Cassidy Clawson
Forum Replies Created
-
Thank you very much for the information. It’s fascinating.
I think I am experiencing both Compressor bugs that are discussed in that thread … the drift of ~3 seconds per hour AND an inaccurate start time in the export.
From now on I will do this type of time coding with frames FOR SURE.
Problem is… one of our writers made a very nice story edit in iMovie using our proxy timecoded 5 hour video as her source material. The plan was that I could watch her edit, see the timecodes of the cuts and rebuild the edit in premiere from the corresponding 5 hour sequence (where we have all the good video tracks and audio sync’d).
It takes a lot more work when the time is off and I don’t see an easy way to fix this given our current position. Oh well.
Timecode is something so critical and precise that a bug is inexcusable. I could care less about the dropped frames or deviation from wall clock… it just needs to be the same across applications and exports!
Thanks again. Any additional ideas appreciated.
Cassidy
-
Thanks for the responses.
Vince: Yes, I have both FCP7 and FCP X installed on the machine. And I can’t uninstall FCP 7 at this time (… still in the mix…)
How could FCP be causing this problem?
Cassidy
-
Excellent suggestions and I will try both!
I am also going to clean up the audio tracks and merge them with the video to make cutting easier.
Cheers
Cassidy