Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Workable Premiere Pro –> Davinci Resolve Workflow with DSLR?

  • Workable Premiere Pro –> Davinci Resolve Workflow with DSLR?

    Posted by Ryan Patch on June 28, 2012 at 3:56 pm

    Hello all –

    I have edited a huge documentary on Premiere Pro, and am very happy with the whole process. This doc is going to be a really cool, well-distributed doc.

    I am, however, having a very hard time trying to get my work out of Premiere into Davinci Resolve.

    When I try to go via XML, I am having trouble with clips relinking to the wrong clips, because I am dealing with Canon DSLR footage which creates duplicate filenames. I understand that this could be solved by making unique reel data for each clip.

    However, I can’t find a place to edit reel data in Premiere. Or, if I use a batch reel# editor (like qtChange), that doesn’t import into Premiere for the XML import.

    Does anyone have a tried and true method for going from Premiere to Resolve, while taking into account the problems of duplicate filenames?

    This seems very very very backwards for getting data into a color application to be so difficult.

    Ryan

    C-deeq Rapheal replied 13 years, 8 months ago 6 Members · 9 Replies
  • 9 Replies
  • Chris Borjis

    June 28, 2012 at 4:20 pm

    It’s the nature of the beast with dslr footage, but hopefully they’ll
    fix for a workaround soon.

    Have you tried exporting the entire timeline and using scene detection
    in resolve?

    I heard that at least works for about 90% of the cuts. sometimes all of them.

  • Jacob Lanum

    June 28, 2012 at 4:21 pm

    Try aaf adobes xml is unreliable

  • Tero Ahlfors

    June 29, 2012 at 4:28 am

    This really doesn’t help now, but the photographer should force file naming on the camera. It makes dealing with the files easier if the A camera starts it’s numbering at 1000 and B camera at 2000 etc.

  • Ryan Patch

    June 29, 2012 at 6:20 am

    Problem with just exporting a rendered movie is crossfades.

    Yes, cameras were staggered. It was a multi-week, multi-camera shoot with a total of over 10,000 clips… so resetting camera numbering doesn’t help.

  • Bouke Vahl

    July 2, 2012 at 2:03 pm

    Not sure if it helps you, but i’ve found Premiere to have a ‘memory’ for files. If you alter a file that Premiere already knows, it assumes the data of the first moment it saw the file.
    Changing the file name can reset this, but probably that causes more problems then it solves.

    If the Reelname change from QTchange prior to importing to Premiere does not work, there is really something funny going on.
    If that’s the case, contact me directly.

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pros

  • Ryan Patch

    July 2, 2012 at 2:59 pm

    Yes, exactly, Premiere’s “memory” for the reelname (I’ve since figured out refers to “Tape Name” in PrPro) is the problem – it will import the reelname on initial import, but there is seemingly no way to force premiere to look again for the reel names.

    Bouke, I would definitely be in the market for a tool that could parse through premiere pro .prproj files or .xml files and convert Tape Names to the file names.

    My colorist and I developed a workflow that I think will work – haven’t tested it yet, but just for others resources:

    – Media manage Premiere project into different projects and folders for each reel. This will mitigate problem of duplicate media.
    – Export .XML of sequence that’s been stripped of any premiere-specific effects (warp stabilizer, etc).
    – Open this sequence in FCP and use FCP to force reel names as file names, export as XML.
    – use qtChange to change reel names on files.
    – Open XML in DaVinci.

    WIll keep you all posted.

  • Bouke Vahl

    July 2, 2012 at 3:06 pm

    Well, the project file is a bit risky to toy around, but XML is human readable.
    I’m very much willing to take some money from you, but since XML is editable with a normal text editor, a search / replace operation will do the trick just fine!

    hth,

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pros

  • Ryan Patch

    July 2, 2012 at 4:03 pm

    Hahahaha. Nice. I would love to give you some money, but it would likely only support you for a day!

    I do know that XMLs are human readable, and have tinkered with them (as well as .prproj files, actually) successfully many times in the past. It’s the sheet number of clips, though, and I’d need a script that could automatically grab the filename and force it into the tape name… find a replace wouldn’t work for that!

  • C-deeq Rapheal

    August 14, 2012 at 5:11 am

    WOW,

    This is the error message
    “the project contained a sequence that could not be opened. No sequence preview preset file or codec could be associated with this sequence type ”

    I used to color correct in After Effects. I have since got my hands on the Red Epic, the Scarlet, and I plan on buying two Black Magic cameras. Therefore, I decided to change the way that I color correct. I first sterted using speed grade. Speed grade has the capabilities of being a great software. However it has some Major flaws that need to be resolved ASAP …..Which brings me to my point. Adobe Premiere can import and export FCP XML v4 However, davinci can import FCP XML v4 and FCP XML v5 but only export FCP XML v5. What that means is, if you want to import any new XML’s that use FCP XML v5, you can’t. I don’t know what needs to happen but we need Adobe to make an update so that they can support 5.0.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy