Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premiere CS6 to FCP 7 with DSLR files

  • Premiere CS6 to FCP 7 with DSLR files

    Posted by Mitch Malecho on June 24, 2013 at 5:32 pm

    Quick question here,

    I decided to edit a project in Premiere CS6 for the purposes of speed, but now may need to hand it off to someone else who’s still on FCP7. Problem is, I took the lazy route offered by CS6 and opted to not transcode anything. Now, as I import XML to FCP7, it crashes because all my files are untranscoded h264 files from DSLRs. If I unclick “relink media” when importing the XML, the project will open, but if I have it checked it crashes.

    My question, is there anyway to transcode all the media, then relink it in FCP7 after I open XML in any efficient manner? If that’s not possible, is there anyway to do it efficiently in CS6 before exporting XML for FCP7 (ie, efficiently replacing all h264 files with prores files in my cs6 project, then exporting xml and opening in FCP7).

    Any help here is much appreciated.

    Thanks!

    Stephen Hill replied 12 years, 11 months ago 2 Members · 1 Reply
  • 1 Reply
  • Stephen Hill

    June 24, 2013 at 7:47 pm

    I have done this successfully many times in both directions. You just need to transcode your files to Pro Res and preserve your folder structure from your original project. its not critical but it will make relinking everything alot easier. You need to ensure your project settings all match up nicely but that is straight forward enough. Open your XML in FCP and point it at the new pro res files where appropriate. You may need to tweak performance settings to ensure good playback, i.e if you have loads of audio tracks FCP may be set to only play x amount of audio tracks before rendering. Also, any MP3s you may have used should probably be transcoded to something more FCP friendly like WAV or Aiff.

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