Quote:
Originally Posted by Altitude909  mtc clock and sample clock are not synchronized and not related. Sample clock runs into the kHz range while the midi rate is 30 frames per second, getting those two in sync = no fun. The DAW can be running at a completely different sample clock and it would not have any bearing on the MTC sync. All MTC does is send information on where it is in the host sequence based on 30 frames per second. It was made for syncing midi to a SMTPE track, thats all. |
sorry I don't get it.
Of course sample clock is 44.1 kHz (or 96 kHz or whatever).
And midi frame rate is much lower. But still: midi clock or absolute counted sample position both
relate to a timing position within the audio stream.
If a audio tape recorder is the slave and measures that some current playback
position is slightly ahead or behind the received midi clock, it must slightly slow down
or accelerate the tape speed in order to correct timing. This is a control loop.
Same thing for the DAW, but here the acceleration can only be realized with
time stretching during playback, for my understanding.
This would also explain why Ableton can do it, because it has real-time time-stretching.