FWIW Michael, looks like the 2 values you're getting are connected to each other by a 24<>25fps conversion, i.e. 12:29:40:13 at 25fps equals 13:00:54:18 at 24fps.
Not sure why this is, nor what type of project you're in, but it's probably got something to do with the way QT change tags the files and Avid interprets them. Think BWF, where the actual start timecode of the file is number of frames since midnight, but obviously dependant on the counting base.
cheers,
Bogdan Grigoresco
www.finale.tv
--- On Sat, 3/19/11, Michael Brockington <mbrock321@minusblue.ca> wrote:
From: Michael Brockington <mbrock321@minusblue.ca>
Subject: [Avid-L2] 5D/7D timecode import bug with AMA and QTChange combo
To: "Avid-L2" <Avid-L2@yahoogroups.com>
Date: Saturday, March 19, 2011, 9:13 AM
Got bit by an unpleasant bug today.
I used QTChange to add TC to 23.98 5D/7D Quicktime files. I assigned
timecode to match the .THM file, with a reelname from the enclosing
foldername.
After running QTChange the timecode display in Quicktime player shows
the first frame of a sample clip has non-drop timecode 12:29:40:14.
If imported the old-fashioned way into Avid, the start timecode shows as
12:29:40:13. OK -- I'm not sure why there's a 1 frame discrepancy, but
that's pretty close.
Unfortunately, if I bring the quicktimes into Avid via AMA, then the
start TC reads 13:00:54:18. Now I am sad...
I need to pull an EDL from a bunch of 5D clips that I brought in via
AMA. Anyone else run into this problem?
If anyone (Bouke, Avid AMA folks?) wants to look at the problem, I have
a couple seconds of an offending quicktime I can email -- only about 5MB.
Cheers,
--Michael
\----------------------------
System specs:
MC 5.0.3.5 software only, Apple MacPro 4,1 Quad-core Intel Xeon 2.26
GHz, 12 GB RAM, OS 10.6.5, Quicktime 7.6.6 / 10.0 (118)
[Non-text portions of this message have been removed]
If you want to donate to Red Cross quake relief, you can do so through your cell phone. Text redcross to 90999 to make a $10 donation. It will be on your next cell bill.
No comments:
Post a Comment