Quote:
Originally Posted by HomeProducer  Okay how I understand it:
The DAW has a clock. This clock is synced to the beat and synced to the audio stream. Normally there would be a constant Ratio between the passing beats and the number of recorded samples if the DAW is the master.
Lets suppose the DAW is the master. Then it always can assign the first beat in a bar to some sample in the stream with regular distances between such marked samples.
Now lets suppose the DAW is the slave. Then during recording things are recorded linearly in time without time stretching. Because the clock of the external master is slightly different, and the DAW will track it, it will probably assign different stream samples to the beat (mark them as the "1" ) then it would do if it was the master. That is still "ok".
Now things get complicated when the DAW wants to track the timing of the master when audio files are already recorded. How does it track these streams and align them to the master clock? Imagine, the master has changed and the new master has a different clock with different error. So either the DAW performs some real-time time stretching or the stream will drift away from the new clock. For example: the audio file could be some drum loop and in order to align this drum loop to the external clock, the drum loop must be time stretched. |
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.