Posted
As Andre wanted to clear the Synfire 2 thread for announcements, here is a separate item. Iam using Synfire 2 with Bitwig 4.3.4.
I can load midi drones into Bitwig, they turn up in Synfire and with the wonderful wizard I can happy assign then to tracks (much easier than previous version).
However, naming both files the same and saving them, Iam unable to get them back once I try to reload. Synfire always reports that the Drones are not available, Bitwig shows them as online.
No amount of restarting/rebooting/open Synfire first or Bitwig first ever brings them back.
Drones have always been hit and miss for me (even using Ableton). If your working on a piece and you cant bring it back togther then I would say its a disaster.
Any similar experience with Bitwig (or Ableton) and ideas to get a more reliable behavior?
Di., 13.09.2022 - 22:10 Permalink
Just an update
I setup Synfire Bitwig combination from scratch with 3 midi Drones again. All works as expected and the drones connect. Then I saved Synfire and then Bitwig. On loading them backup Synfire still cant connect to/find the drones. Iam using Synfire 2.08 build 3 and vst3 (is there a vst2 version of the drone I couldnt find it anywhere?)
Do., 15.09.2022 - 23:21 Permalink
Another update:
I worked out that I can make the Drones turn up again by deleting and re-inserting the last midi drone in Bitwig. Then Synfire sees them all again and maps accordingly. Of course I need to do this everytime I start Synfire and Bitwig from scratch.
So., 18.09.2022 - 21:36 Permalink
Drones must be fully loaded in a DAW to connect with Synfire. Some DAW suspend or delay loading plug-ins in order to speed up the loading process. This makes an associated arrangement come up broken when you open it.
Check the project settings of your DAW and make sure all plug-ins are always loaded, whether or not the DAW thinks they are currently needed.
This fixed the issue here with Logic. BitWig, Live and others may have similar options that you should check.
A related fix will make sure that rack modules at least don't come up as NULL when this happens, so they are able to re-connect to the Drones once the DAW is actually loading them.