It also does not show the other container's content in the total arangement as greyed figure.
Either Figure of container A is active, or Figure of container B. Figures for the same instrument do not mix where containers overlap. If you want this, you need to create an additional instrument with the same sound.
When clicking on a note of a figure, it takes around 1.5 seconds until it plays a preview
Sometimes the Engine happens to run out of sync. Pressing Stop fixes this. Last resort is Playback >> Reset Audio/MIDI System. A restart is not necessary.
icons should have a mouse over hint
Tooltips can be enabled from the Help menu. I re-enabled this by default. It's a difficult choice. The tooltips can be extremely annoying and then users complain they don't know where to disable them ;-)
How to create now own Figure library
Library >> New
It warns me of a windows zoom of 125%
There are costemtic issues on Windows dealing with 1/4 pixels. If you are not bothered by graphics glitches, you can ignore this warning.
I opened a SF1 arrangement and agreet to takeover the existing instruments. Since then, SF2 does not load a working engine with FluidR3 anymore.
Sounds like random coincidence. Both have nothing to do with each other, as far as I can tell. There are still issues with the Demo not saving some files and settings where it should. We are currently fixing this.
The drag&drop of midi to DAW does not always work. In a video I saw to go to matrix and drag with mouse from the instrument name to DAW. That worked. But only once. I was not able to do this again.
I am not sure if it should also work on the structure page - the manual indicates, that this could work. But not on my intance.
You need to hold the mouse outside a Synfre window for while for it to switch to export mode. Otherwise drag & drop is internal only.
Sure, thats what I try. Now I restarted SF2 and tried it again, but it does nothing. (click, hold, wait, move to outside - keeping button pressed). It worked only once yesterday (Demo Version).
With Build 16 (and waiting) the drag-and-drop export of MIDI to Bitwig is no longer possible, although this worked fine before. Please check, w/o reliable drag and drop this version is almost useless for my workflow.
Now I bought the full version - SF2 convinced me! It is realy easier to use after the cleanup. So many years I tried to get into but was just totaly confused. With SF2 things are more clear to me. Good Job!
... Regarding export midi per drag/drop:
I think the reason why it seemed to stop working is that I had SF2 second time in a smaller window next to my DAW and now I see it works only when I maximize it to full monitor. Got a resolution of 3440x1440 with 125% Zoom. If I would not have a second monitor, where I can move the DAW to, export per drag/drop would not be possible. I tried also and 150%, but it also does not work. With 100% it works (I must restart SF2 before each try)
But now a funny thing to get it work with 125%:
Set windows to 100% zoom
Start Synfire
Change Windows to 125% zoom
Now it works.
Looks for me you did a kind of zoom analysis during startup, calc some kind of resolution fix but that seems to have a negative impact to the mouse drag/drop functionality.
There are possible issues with HiDPI and drag & drop on Windows if coordinates are not translated correctly.
On macOS however, nothing has changed throughout all 2.0 builds. Just checked and it seems to work as intended. You need to hover over the desktop or DAW for three seconds before the object turns into a MIDI file.
But could it be that you use the windows zoom factor in a fix calculation although it might maybe not needed? I mean, why is it working if I start Synfire with 100% and change the zoom later?
Windows High HiDPI is indeed a pain for many apps have much worse problems, but this artifact is strange, that it only occurs there, also if I click 'always on top' it goes away. I wouldn't worry about it too much, unless somthing springs to mind. Its a very minor issue, and in other respects the program copes well - just thought I would mention it :)
No, it's the structure page with the snippets side view activated. I'm recording with a snippet highlighted.
It does allow me to record but only into the first track being recorded or if the snippet was imported from the arrangement, into those tracks that had already been recorded. Very strange behaviour.
Screenshot? If you want we can have a look together via screenshare. If interested, send me a direct message. But looks like you are a long-term user and may know it even better than me.
Factories: Parameters.Velocity: Metric Velocities: Min and Max don't work most of the time. Strangely, they do work fine when used inside other factories.
Update: I've been able to find out that the bug happens when the range is small, e.g. 62 to 70. In such a case, Synfire just use the entire 0 to 127 range. Expected behavior: however small the range input by the user, KIM should still work with it.
I noted some pitch-related bug of MuiscXML export of absolute symbols. (I tried to export some percussion with only absolute pitch symbols to MusicXML.)
Within Synfires Output parameters, the resulting different pitches are shown (and this is also preserved in the MIDI output). However, the pitches in the MusicXML are all constant, and a different pitch than shown in the Synfire Output (and MIDI export).
Anyway, good to see that the rhythm including triplets and ties was seemingly preserved. Thanks!
Wed, 2022-10-12 - 23:27 Permalink
> That can be enabled somewhere in the settings.
thx, that helped. IMHO should be on for a new installation.
> Have you had a look at factories?
oh. I found it and do not understand so far - a bit overwhelming. Now I gona start watching this video and hope to understand.
Thu, 2022-10-13 - 09:08 Permalink
Either Figure of container A is active, or Figure of container B. Figures for the same instrument do not mix where containers overlap. If you want this, you need to create an additional instrument with the same sound.
Sometimes the Engine happens to run out of sync. Pressing Stop fixes this. Last resort is Playback >> Reset Audio/MIDI System. A restart is not necessary.
Tooltips can be enabled from the Help menu. I re-enabled this by default. It's a difficult choice. The tooltips can be extremely annoying and then users complain they don't know where to disable them ;-)
Library >> New
There are costemtic issues on Windows dealing with 1/4 pixels. If you are not bothered by graphics glitches, you can ignore this warning.
Sounds like random coincidence. Both have nothing to do with each other, as far as I can tell. There are still issues with the Demo not saving some files and settings where it should. We are currently fixing this.
Fri, 2022-10-14 - 02:40 Permalink
Another thing (bug?) found:
Fri, 2022-10-14 - 09:25 Permalink
You need to hold the mouse outside a Synfre window for while for it to switch to export mode. Otherwise drag & drop is internal only.
Fri, 2022-10-14 - 11:20 Permalink
Sure, thats what I try. Now I restarted SF2 and tried it again, but it does nothing. (click, hold, wait, move to outside - keeping button pressed). It worked only once yesterday (Demo Version).
Fri, 2022-10-14 - 17:06 Permalink
I export to Bitwig. Here the trick is to wait for 1sec after dragging to DAW while still holding mouse pressed. Again wait after. This works reliably.
Fri, 2022-10-14 - 19:57 Permalink
Export is disabled in the demo.
Sat, 2022-10-15 - 18:47 Permalink
Build 16 is still buggy when using the Morphing Parameter, often the project is no more ready for use.
Sat, 2022-10-15 - 18:54 Permalink
With Build 16 (and waiting) the drag-and-drop export of MIDI to Bitwig is no longer possible, although this worked fine before. Please check, w/o reliable drag and drop this version is almost useless for my workflow.
Sun, 2022-10-16 - 01:41 Permalink
Now I bought the full version - SF2 convinced me! It is realy easier to use after the cleanup. So many years I tried to get into but was just totaly confused. With SF2 things are more clear to me. Good Job!
... Regarding export midi per drag/drop:
I think the reason why it seemed to stop working is that I had SF2 second time in a smaller window next to my DAW and now I see it works only when I maximize it to full monitor. Got a resolution of 3440x1440 with 125% Zoom. If I would not have a second monitor, where I can move the DAW to, export per drag/drop would not be possible. I tried also and 150%, but it also does not work. With 100% it works (I must restart SF2 before each try)
But now a funny thing to get it work with 125%:
Looks for me you did a kind of zoom analysis during startup, calc some kind of resolution fix but that seems to have a negative impact to the mouse drag/drop functionality.
Sun, 2022-10-16 - 10:33 Permalink
There are possible issues with HiDPI and drag & drop on Windows if coordinates are not translated correctly.
On macOS however, nothing has changed throughout all 2.0 builds. Just checked and it seems to work as intended. You need to hover over the desktop or DAW for three seconds before the object turns into a MIDI file.
Sun, 2022-10-16 - 12:04 Permalink
But could it be that you use the windows zoom factor in a fix calculation although it might maybe not needed? I mean, why is it working if I start Synfire with 100% and change the zoom later?
Sun, 2022-10-16 - 12:11 Permalink
Don't know yet. This code is written by others that I need to consult first.
Sun, 2022-10-16 - 12:24 Permalink
Can I check - why are Snippets greying out the ability to record on tracks that haven't been recorded yet?
Sun, 2022-10-16 - 13:09 Permalink
Factories found. It was also limited by Demo version. Meanwhile I bought it.
Sun, 2022-10-16 - 13:33 Permalink
Small problem, but when palette window not full size, the content of menu item pallete (when clicked) is displayed with wrong scale.
Windows11 3840x2400 250% scale. File Edit Layout etc are all fine, just the Pallete menu item when clicked.
Sun, 2022-10-16 - 14:37 Permalink
Have Single-Phrase Snippets mode enabled?
What's not to love about Windows HiDPI? This is such an awkward artifact, I have not the slightest clue yet why it would even be remotely possible.
Sun, 2022-10-16 - 17:55 Permalink
Windows High HiDPI is indeed a pain for many apps have much worse problems, but this artifact is strange, that it only occurs there, also if I click 'always on top' it goes away. I wouldn't worry about it too much, unless somthing springs to mind. Its a very minor issue, and in other respects the program copes well - just thought I would mention it :)
Mon, 2022-10-17 - 10:45 Permalink
No. It doesn't make a difference if that setting has been enabled or not.
Mon, 2022-10-17 - 10:58 Permalink
Are you talking of the Snippets page? It's not possible to record there. You can record on the Structure page.
Mon, 2022-10-17 - 13:01 Permalink
No, it's the structure page with the snippets side view activated. I'm recording with a snippet highlighted.
It does allow me to record but only into the first track being recorded or if the snippet was imported from the arrangement, into those tracks that had already been recorded. Very strange behaviour.
Mon, 2022-10-17 - 14:51 Permalink
Screenshot? If you want we can have a look together via screenshare. If interested, send me a direct message. But looks like you are a long-term user and may know it even better than me.
Mon, 2022-10-17 - 16:26 Permalink
Thanks AndreasHe
but yes, I think this is one for the big man himself.
appreciate the offer tho'
it also reminds me, maybe time for a Synfire webinar this week if anyone is interested. Reply in a different thread of course.
Mon, 2022-10-17 - 17:19 Permalink
Ah, found it. It's a bug.
Tue, 2022-10-18 - 16:55 Permalink
Synfire 2.0.10 Build #17
Tue, 2022-10-18 - 19:35 Permalink
More crash reports sent.
The software says build #19 is out there but I cannot download it from my site account.
Wed, 2022-10-19 - 17:59 Permalink
Instrument labels just don't work anymore. They're saved, but the new name is not reflected on the instruments on the left panel.
Wed, 2022-10-19 - 19:49 Permalink
Thanks. It's a bug with references to global instruments only though.
Thu, 2022-10-20 - 01:08 Permalink
Factories: Parameters.Velocity: Metric Velocities: Min and Max don't work most of the time. Strangely, they do work fine when used inside other factories.
Update: I've been able to find out that the bug happens when the range is small, e.g. 62 to 70. In such a case, Synfire just use the entire 0 to 127 range. Expected behavior: however small the range input by the user, KIM should still work with it.
Thu, 2022-10-20 - 09:26 Permalink
I noted some pitch-related bug of MuiscXML export of absolute symbols. (I tried to export some percussion with only absolute pitch symbols to MusicXML.)
Within Synfires Output parameters, the resulting different pitches are shown (and this is also preserved in the MIDI output). However, the pitches in the MusicXML are all constant, and a different pitch than shown in the Synfire Output (and MIDI export).
Anyway, good to see that the rhythm including triplets and ties was seemingly preserved. Thanks!