2 ms·
It's not hard; it's just kept behind a very thin veil of 'pro' Timecode server and recorders that sink timecode are literally all you need. Everything has been
by gorkish 2y ago
It's not hard; it's just kept behind a very thin veil of 'pro'
Timecode server and recorders that sink timecode are literally all you need. Everything has been standardized for multiple decades.
Truthfully, anymore even this is starting to become unnecessary; most NLE's can just figure it out from the regular metadata and autocorrelation to sync the clocks. Just dump it in the timeline and everything lines up.
- geerlingguy 2y agoThe clocks often drift if you have more than 5-10 minutes of continuous footage though, so TC is essential. Unfortunately you have to bump up to prosumer/pro tier cameras and recorders if you want TC inputs.
- gorkish 2y agoGenlock is absolutely not needed to overcome clock skew; sync to nearest frame at cuts and resample the audio to the frame timings. Plus most modern equipment has really great clocks and I would not be surprised if it drifts less than hypothesized. Let's imagine we are shooting 24fps on a couple of iPhones; what is the clock error required to drift out by 1 frame over 10 minutes? The answer works out to about 70ppm. The iphone uses a MEMS oscillator with about a 5ppm error, so ... eh? Just doesn't seem likely to be a big issue for regular stuff. If you are shooting scientific data or something maybe this matters more, but you'll have to account for it in that context no matter what.