-
Timecode funkiness
Let’s start with the tech specs
12-core, 10.6.8, 24 gigs ram, quadro 4000
premiere 5.5.2 and FCP 7.0.3
XDCAM 35 vbr origin footageWhat I’m trying to do is send an XML from Premiere to FCP. The sequence is cuts only. From premiere I go to export final cut xml. Then in FCP I import the xml. When I open the sequence in FCP the cut isn’t even close to to what it is in Premiere.
Then I went back to premiere to figure it out. I couldn’t. This is where things got really strange. I’ll try to explain with screen captures, as I don’t even know the words to explain it.
In this picture you can see that the media start time for highlighted clip is 9;30;06;11, but the video in point is 9;29;32;05. If my media doesn’t start until 9;30;06;11 how can I have an in point prior?
Things get more weird. When I click on the clip used in the timeline, this is what I get in the viewer
Clearly you can see that the start timecode is 9;30;06;11, but when I click on the clip in bin this is what I get.
Here you can clearly see the timecode starts at 9;29;32;05. What the heck is going on?
I brought the XDCAM clip into the computer using Sony’s XDCAM transfer and a U1 deck.
Anyone else getting this funkiness? It really kills my rough in Premiere, finish in FCP workflow.
-
7 Replies
-
I’m no help here, but we experience the same thing at our shop. It happens for us with DSLR footage all the time (transcoded or not). As best we can tell it corresponds to the time code in the file, how PP reads it, and how PP interprets it upon XML export.
Our common problem lies in going from PP to DaVinci Resolve. The cuts come into Resolve nowhere even close to what the PP timeline actually shows. My only guess is that PP is having problems dealing with the timecode/metadata of the file. I never had this issue with FCP7.
Glad to know we’re not alone over here….sorry I’m not more help.
Ryan
-
It looks to me that, in that second picture, the timecode is showing as NDF, where in the first image the timecode is clearly DF.
The odd thing is that you screen-cap of the bin also looks strange with just that particular clip; the bulk of the time codes indicate DF, but the Video In and Video Out points seem to be showing NDF timecode (though it’s hard to tell since the dotted lines might be obscuring the semi-colons).
One disadvantage of Premiere’s willingness to play anything (normally a good thing) is that if there’s an issue here (and it may be with just that single clip) it doesn’t show up until you need Premiere to play nice with another app.
If you remove that clip from the equation and test with other clips that are consistently DF on a DF timeline, can you roundtrip with FCP and get the cuts you expect?
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Make sure you have the latest version of Premiere Pro. Go to Help>Updates
Kevin Monahan
Sr. Content and Community Lead
Adobe After Effects
Adobe Premiere Pro
Adobe Systems, Inc.
Follow Me on Twitter! -
You are correct about the DF vs. NDF. If I load any clip from the bin it miraculously shows up as NDF. I can actually make any of the clips in my bin do that, it just happens that I have this one selected for the screen grab. It’s not just this one clip.
All the stuff was shot NDF so I don’t know why it is showing up as DF in Premiere.
-
It says I’m all up to date.
-
Jeremy,
What about Petros’ suggestion: “If you remove that clip from the equation and test with other clips that are consistently DF on a DF timeline, can you roundtrip with FCP and get the cuts you expect?”Ryan
-
I never did get it to work. It is definitely a drop frame, non-drop frame issue. All the clips were shot non-drop frame. When I highlight them in the bin, under the in and out the footage displays the correct time code, but under the media attributes tab it will not display as non-frop frame.
After trying for couple hours, I just recut the piece in FCP. Probably should have done that straight off as that only took an hour.
Reply to this Discussion! Login or Sign Up