Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Exporting to the same format as source without quality loss

  • Exporting to the same format as source without quality loss

    Posted by Run Rodriguez on October 29, 2012 at 3:39 am

    Simple question, just to be sure:

    If I have a project with multiple movie files edited together and I want to export this project to one movie file using the same codec, will there be any quality loss?

    I’m using footage that is:

    Frame Size = 1920 x 1080
    Compressor = Apple ProRes 422
    Quality = Most (5.00)
    Average Data Rate: 16.8 MB / second

    I’m exporting using the same codec, filetype and size, so is it safe to assume that there would be no loss in quality?

    Do the bitrate settings need to be played with?

    Walter Soyka replied 13 years, 6 months ago 3 Members · 3 Replies
  • 3 Replies
  • Kris Merkel

    October 29, 2012 at 3:30 pm

    I never export to ProRes from PrP or AME as the quality is never as good as the original. Anytime I need a ProRes file I use FCP7.

    As far as the bitrate goes, that depends on what your deliverable size requirements are, length of program, do you need VBR or CBR ect. best thing to do is start with the presets and play with the settings from there to get the optimal encode.

    Really the thing is, If you are already using particular codec there would be no need to re encode it to that codec. You will see a quality loss and that is why when you need to export a prores file you would want to use FCP7 and export the native file.

    “Think of everything in terms of building capacity.”

    Kris Merkel
    twitter: @kris_merkel
    Product Manager, Flanders Scientific Inc.
    http://www.shopfsi.com
    Co-Founder, Atlanta Cutters Post Production User Group
    http://www.atlantacutters.com

    2.2Ghz MBP core i7
    16Gb RAM
    CS 5.5
    FCP7 and Studio
    Blackmagic Design UltraStudio 3D
    AJA IO XT
    FSI LM-2340W



  • Run Rodriguez

    October 29, 2012 at 5:00 pm

    Thanks.

    The reason I want to export back to prores is because I am to deliver to a client one high quality quicktime file of a project that is currently broken up into multiple files and arranged in premiere. My workflow has been to import raw BDMV to premiere, export prores mov’s to after effects, then effects are added and new prores mov’s exported back to premiere. I do have final cut and I could easily set up the files in a final cut project. If I then exported a same as footage quicktime within final cut, would this solve my problem and give me one prores quicktime mov without quality loss when compared to the prores mov’s in the timeline?

  • Walter Soyka

    October 29, 2012 at 6:04 pm

    [Run Rodriguez] “My workflow has been to import raw BDMV to premiere, export prores mov’s to after effects, then effects are added and new prores mov’s exported back to premiere. I do have final cut and I could easily set up the files in a final cut project. If I then exported a same as footage quicktime within final cut, would this solve my problem and give me one prores quicktime mov without quality loss when compared to the prores mov’s in the timeline?”

    FCP will not recompress the media, as you noted above.

    Pr would recompress the ProRes media. Practically speaking, I wouldn’t worry about the quality loss. ProRes handles multiple generations of compression without visible degradation pretty gracefully. Two generations of ProRes should be fine.

    That said, you can avoid the multiple compressions and stay in an all-Adobe workflow by using Dynamic Link between Ae and Pr, or by using lossless intermediates instead of ProRes.

    Walter Soyka
    Principal & Designer at Keen Live
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    RenderBreak Blog – What I’m thinking when my workstation’s thinking
    Creative Cow Forum Host: Live & Stage Events

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