-
XML Export Timecode Problem
It seems to me that I’m having a very similar problem to the post: https://forums.creativecow.net/thread/3/920522#920522
I’m exporting an XML from premiere to be used in Davinci Resolve. But when imported into Davinci, it finds all of the source media, but cannot connect, because the timecode ins and outs are all off by about a full minute. (so sometimes the TC in is after the out of the media) The footage is RED Scarlet footage.
I thought it might be a Davinci problem, so I imported the XML into FCP and though obviously it couldn’t like to the R3D files, the timecode showed up the same, incorrect. While in the source window of Premiere it shows the correct ins and outs.
I’m not sure if this is user error or a bug, but I need to figure this workflow out as we have several projects that need to go to finishing.
Cheers,
-Alan -
4 Replies
-
did you ever figure this out? I’m having the same exact problem and don’t know what to do to fix it.
-
Nope never figured it out. Not even cs 6 fixes the issue.
Ended up having to export a flattened MOV and use scene cut detection. Worked but not ideal. And it’s real weird because another project xml worked beautifully…
-
I found out that you can get the video out into fcp by exporting a legacy aaf file out and the audio out with a omf export in premiere and then use automatic duck to import into final cut. It will bring the video and audio in sync into fcp but you then have to recreate any titles or graphics. Not ideal but worked for me
-
The problem was I was using Red footage in the timeline so going to fcp was impossible. Also I had scaling and positioning information that I didn’t want to have to redo and aaf from premier does not have ptzr information that davinci understands. I just set all the r3ds to redlogfilm and exported as prores 4444 it became basically like grading alexa footage.
Reply to this Discussion! Login or Sign Up