this assumes the drift occurs at a constant rate, anyway if you run into issues in FCP, you can always put it through ffmpeg, like so: ffmpeg -i input.m4a -af atempo=1.001 output.wav
-
or, well, technically the precision is something like 1 in a quadrillion but the point is that it's way more than 2 decimal places
I actually think the audio hijack may have worked! Gonna do another test now, as my mic levels were a bit too low to accurately test. Will let you know!
-
-
guess that confirms the problem was quicktime, then; good to know
-
Tried again and it seems to be working! The audio file still drifts, but the difference is down from 5-6 frames an hour to 1.5 an hour.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.