Posted
Im using Bitwig 5.
The sync works really well. The only issue Im having is that whenever I loop a container and start from a container in the middle of the song, my DAW's timing is off. It sort of sounds like its Halftimed but the tempo is the same as Synfire's.
When I start the song in Synfire from the beginning, I have no problems and it works beautifully but when I loop a container and play from the container, my DAW is somehow Halftimed. Like I said, the temp is exactly the same and they are still synced.
Mo., 09.10.2023 - 18:25 Permalink
Loops have not been tested yet, so thanks for your feedback.
It is not quite clear how a loop in Synfire is supposed to map to the DAW. For Synfire there is no way to supply a DAW with loop locations. It is also impossible for any sync method to reposition an unprepared DAW to the start of a loop without disruptive hickups and delays.
So the only way this could work is to keep the DAW moving on (not looping) while Synfire is running its loops. Not sure if that makes any sense.
Mo., 09.10.2023 - 19:03 Permalink
Thanks.
I understand what you mean and just tried it. No luck. To make it worse, I just started it from a container, no looping enabled on Synfire's side and got the same result. As of now, I must play all the way through from the beginning of the song. Hope at least that is fixable soon.
Mo., 09.10.2023 - 19:23 Permalink
Congratulations. You have just found a bug with BitWig.
Running BitWig and Ableton Live side by side, both receiving the same clock from Synfire, Live is correct and stays 100% in sync while BitWig veers off.
You should report that as a bug. Something along the lines of "MIDI Clock sync detects tempo correctly but doesn't follow/increment absolute time correctly."
Mo., 09.10.2023 - 19:25 Permalink
I followed the tutorial. Ill keep messing with it...Ill figure out whats wrong. Thanks
Ah Ok. Will do thanks. Think Im gonna use Studio One anyways. Bitwig has done similar things in the past with other softwares.
