Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro PPro CS6 and rendering

  • PPro CS6 and rendering

    Posted by Brian Cooney on January 5, 2013 at 8:35 pm

    being a long time FCP editor, It’s great being able to work with multiple native clips within a PPro timeline. I’ve just switched over and I’m noticign rendering times being quite a bit longer than FCP even with a single codec. Could anyone tell me if pre-conversions to ProRes might speed this up? working strictly with prores.. or maybe not worth it. thanks. Feels like the days of the G4 and FCP 2.0 sometimes..

    MotionFoundry, Inc. Video Post
    Clients: GM, AOL, Kohl’s, 3 Doors Down, IKEA, Kelloggs, Toyota, Thomas Nelson, NASCAR Affiliates

    Alex Udell replied 13 years, 4 months ago 3 Members · 3 Replies
  • 3 Replies
  • Bernhard G.

    January 6, 2013 at 12:01 pm

    Hello,

    currently, PremierePro does Smart Rendering
    as FCP7/X or MediaComposer does, only for a handful of formats
    which means, only those portions of the sequence are rendered
    that need to be in case, the sequence-codec/format and the clip codec/format are the very same.
    See here:
    https://blogs.adobe.com/kevinmonahan/2012/10/11/smart-rendering-in-premiere-pro-cs6-6-0-1-and-later/

    When exporting via AME this means, every time You output the sequence in PremierePro, 100% of the images are processed during export again.
    If You export a sequence into 3 different
    delivery formats, the whole sequence is rendered 3 times.

    Therefor, to render a sequence doesn’t make much sense.

    You COULD set the preview codec to e.g. ProResHQ
    and check ‘use preview files’ in AME.
    BUT: this would mean, if the render-files are ProResHQ and You export the sequence into a ProResHQ master, the ProResHQ render files are decoded and re-encoded into the very same format again…
    So: DON’T DO THAT!

    When You need to export into several formats:
    PremierePro’s rendering workflow delivers a better quality
    but it also takes longer.

    (But as long as PP’s image processing pipeline is not 100% 32bit-float,
    combined with CPU-CUDA differences in quality, this advantage is very theoretical…)

    One thing I don’t understand:
    Why does Adobe offer so many different sequence presets?

    Since PremierePro’s sequences are codec-independent,
    there seems to be no technical reason for that!
    It appears to be a help for those who don’t know in which
    video standard they are working…

    Best regards,
    Bernhard

  • Brian Cooney

    January 6, 2013 at 1:31 pm

    Great info thanks. Are you more of a Media Composer advocate?

    MotionFoundry, Inc. Video Post
    Clients: GM, AOL, Kohl’s, 3 Doors Down, IKEA, Kelloggs, Toyota, Thomas Nelson, NASCAR Affiliates

  • Alex Udell

    January 6, 2013 at 2:33 pm

    I think the reason for the presets is not that they are tied to a codec.

    Most ppl however, are used to the convention of thinking about video based on particular codec / resolution….

    So it’s easier to say…this is DVCPro HD

    then to say… this preset is: HD 1280 x 1080 at 1.5 PAR

    Alex Udell
    Editing, Motion Graphics, and Visual FX

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