I tried chasing the same timecode signal with Reaper, and it can follow much more smoothly, so I suspect that the problem originates is in Waveform.
Based on the symptoms I'm seeing, I suspect that Waveform is trying to autodetect the framerate, but not really succeeding. Is it possible to explicitly set the frame rate to expect?
Here are some more details.
- I am on Mac OS 10.13.6
- I am sending MTC from BitWig Studio via IAC
- Reaper does a good job of chasing the timecode signal
- I can "trick" waveform into chasing the timecode like this: [1] Start sending timecode at 30fps. This causes Waveform to begin playing, but it is about 250ms behind BitWig. [2] while transport is still playing, change the fps in Bitwig to 24. This causes Waveform to synch quite accurately. Now if I stop and restart the Bitwig transport waveform chases playback, but it is 250ms behind again.
