Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums DaVinci Resolve Solution for DNxHD.mxf in Premiere Pro on Windows.

  • Solution for DNxHD.mxf in Premiere Pro on Windows.

    Posted by Dmitry Kitsov on February 21, 2012 at 5:56 am

    Your reason to use might be a fast rendering speed of DNxHD in resolve.

    You must download and install Avid DNxHD codec from the Avid website for this to work.

    Download ffmbc source (search google), put it into folder, compile. If cannot compile (I do not know how) then download one of the precompiled Windows distributions version higher 0.7 (search google) and put ffmbc.exe file in the same folder as earlier. Then create a text file and paste the following (not including Start/stop copy markers) into it:

    Start copy after here
    DO (
    md mov
    )

    for %%f IN (*.mxf) DO (
    “C:LocationofffmbcfolderFFmbc-0.6.1ffmbc.exe” -i %%f -vcodec copy %%~nf.mov
    )

    DO (
    move *.mov “mov”
    )
    Stop copy before here

    You will need to replace the “C:LocationofffmbcfolderFFmbc-0.6.1 with the path relevant to your system.

    After doing so save the file anywhere you will find it (I suggest ffmbc root folder) and change it’s extension to .bat. Name the file anything you want: for example “mxf_to_mov.bat”
    After that create a new folder into which you will output your mxf files from DaVinci Resolve. When rendering mxf files and your original files having too long of the names, use renaming features in Resolve Render panel (refer to Resolve manual), so you have short file names like {0001projextmxf.mxf} The reason is that ffmbc does not like file names with spaces in it or the long ones.
    In resolve go to conform panel and under Timeline management section do Export. Export an xml.
    Once you have your rendered files copy and paste the .bat file we created earlier into your render folder with the .mxf files. Double click the .bat file and let it run. It will create a folder named “mov” and put the .mov versions of your mxf renders there.
    Put an .xml file from before into a new mov folder alongside with your newly trans-coded .mov files. Right click on .xml file and choose edit. Edit it in text editor of choice. You will want to use replace feature of your text editor (normally in Edit menu) and ave it replace all of .mxf with .mov strings. This way your xml will now refer to mov files.
    After doing that start Premiere Pro or any other app that understand FCP XML format and create a new project. Then do Import and navigate to a folder with the xml file from before. If Premiere pro will ask for location of .mov files point it to the mov folder making sure that display only matching names media is checked.
    You are done.

    Rohit Gupta replied 13 years, 9 months ago 3 Members · 3 Replies
  • 3 Replies
  • Reynold Dodson

    February 29, 2012 at 8:57 pm

    Thank you for this procedure. I am able to get this to work pretty well. Converting Resolve’s MXF DNxHD file into QT DNxHD files takes 0 seconds. The files are a reasonable size, look great, and work well in Premiere.

    I thought I would add a bit more information here that might be helpful other users.

    The official ffmbc site is here:

    https://code.google.com/p/ffmbc/

    Compiled ffmbc for Windows can be downloaded from here:

    https://www.videohelp.com/tools/ffmbc

    Avid’s QT codecs (including DNxHD) can be downloaded from here:

    https://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=372311

    Now the only thing we need is a way to get Premiere to output a DNxHD codec file that Resolve will open. Using the above Codec, Premiere will render output DNxHD QT files, but Resolve does not “see” these files.

    Has anybody had success with this part of this work flow?

  • Dmitry Kitsov

    July 29, 2012 at 7:42 pm

    Sure no probles, thanks for posting the links.

  • Rohit Gupta

    July 30, 2012 at 3:41 am

    Version 9 has support for DNxHD in a Quicktime wrapper, and hopefully that will help this workflow.

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