Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Better Export Workflow Needed for Client Review Presentations with TC burn in

  • Better Export Workflow Needed for Client Review Presentations with TC burn in

    Posted by Manny Kivowitz on May 8, 2013 at 9:35 pm

    Hello,

    We’re just making the switch from FCP to PremierePro CS6 and are running into some bumps, many of which we’ve found helpful advice for here.

    Our big issue at the moment is finding the fastest workflow for creating client review videos which we post to the web at 960×540 mp4 files.

    First off, specs for our machine: 12 core 2.66ghz intel neon machine with 32gb of ramw/ nvidia gforce gt120 512mb graphics card

    Our old workflow in FCP was :

    1) export the timeline as a QT movie (not conversion) using the sequences settings (which were typically 1920 x 1080 prores) which very quickly created a hi-res output file in less than a minute for a 5 minute clip. (most of our projects are multicam projects – might be relevant to the Premiere slow down)

    2) Use Episode encoding software with a preset to create an acceptable quality 960×540 mp4 file with a TC burn-in in the lower right corner. (Episode creates the TC burn in) Roughly 5 – 8 minutes

    3) post to web for review. Total time, less than 10 minutes.

    Today we realized that Adobe encoder does not have the ability to add a TC burn window and so we had to add the burn in using Premiere (which un-rendered our entire timeline of course). This export took a whopping 56 minutes to achieve what used to take us less than 10 minutes with the FCP / Episode process outlined above.

    So our questions are:

    1) What would be the fastest path / settings for Premiere to quickly export a high quality file that we could run through Episode to achieve the desired results. Is it possible to achieve those super fast exports we were getting in FCP?
    —–FYI – We did try exporting a fully rendered 5 minute timeline as well using “match sequence settings” and it took 17 minutes (vs less than a minute in FCP) – ugh

    OR

    2) Is there a faster path available to us while staying within the CS6 suite?

    If we have to spend 56 minutes to export every client review clip we do, we’re in trouble!

    Your help is much appreciated!

    Manny Kivowitz
    KSK:STUDIOS

    Bouke Vahl replied 13 years ago 4 Members · 7 Replies
  • 7 Replies
  • Steve Brame

    May 8, 2013 at 10:28 pm

    Does the Mac version of CS6 include Adobe Media Encoder? I confess that I don’t even know.

    If it does, then add your timecode burn to an Adjustment Layer above everything in your timeline, then export directly to whatever format and size you need. No need for intermediate encodes. If you have a good CUDA card, and encode to H.264, your encode will be swift.

    Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia Quadro 4000 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID5 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * CS6.x Creative Cloud
    ——————————————-
    “98% of all computer issues can be solved by simply pressing ‘F1’.”
    Steve Brame
    creative illusions Productions

  • Walter Biscardi

    May 8, 2013 at 10:45 pm

    [Manny Kivowitz] “2) Is there a faster path available to us while staying within the CS6 suite?

    If we have to spend 56 minutes to export every client review clip we do, we’re in trouble!”

    First off, with CS6 you need an nVidia CUDA card for the FASTEST renders, and fast processors help.

    We struggled with this exact task when we switched from FCP 7 too. Here’s what you do.

    In the timeline, add an Adjustment layer at the very top, usually you need to add a video layer. Make it the length of your entire timeline.

    Add Video Effects > Video > Timecode (I think that’s where it is) to the Adjustment layer.

    Resize and position as you see fit.

    Now Export from your timeline and it’ll burn in the TC.

    You can choose from a myriad of settings from your Export settings.

    Walter Biscardi, Jr.
    Editor, Colorist, Director, Writer, Consultant, Author, Chef.
    HD Post and Production
    Biscardi Creative Media

    Foul Water Fiery Serpent, an original documentary featuring Sigourney Weaver. US & European distribution by American Public Television
    MTWD Entertainment – Developing original content for all media.
    “This American Land” – our new PBS Series.
    “Science Nation” – Three years and counting of Science for the People.

    Blog Twitter Facebook

  • Manny Kivowitz

    May 9, 2013 at 2:19 pm

    Thanks for the insight Walter – we’re jumping out to pickup a Quadro 4000 to replace the ATI Radeon 5770 thats installed alongside a Nvidia Geforce GT 120 – this should do wonders for Davinci Resolve as well! Not sure how we ended up with two GUI level cards in our main machine…. but it should definitely make a difference having the CUDA enabled (and only one slot!) Quadro 4000.

    Will post again later when we’ve installed the card and tested it out.

    Manny Kivowitz
    KSK:STUDIOS

  • Manny Kivowitz

    May 9, 2013 at 2:20 pm

    Thanks Steve! We’re switching out one of our graphics cards out today – will post results once we’ve got it up and running.

    cheers!

    Manny Kivowitz
    KSK:STUDIOS

  • Manny Kivowitz

    May 9, 2013 at 4:10 pm

    After installing the Nvdia Quadro 4000 our render time for the exporting the same sequence with the window burn added in the Premiere Pro timeline dropped from 56 minutes with our non-CUDA card to 4 minutes with the Quadro 4000 CUDA enabled card installed. What a relief.

    Problem Solved! – Thanks guys!!

    I’m sure we could have gone with a less expensive card and gotten decent results but time is definitely money in this business and we’re now back to a workflow that will meet client demands.

    cheers!

    Manny Kivowitz
    KSK:STUDIOS

  • Steve Brame

    May 9, 2013 at 4:13 pm

    [Manny Kivowitz] “dropped from 56 minutes with our non-CUDA card to 4 minutes”

    So much for coffee breaks.

    Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia Quadro 4000 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID5 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * CS6.x Creative Cloud
    ——————————————-
    “98% of all computer issues can be solved by simply pressing ‘F1’.”
    Steve Brame
    creative illusions Productions

  • Bouke Vahl

    May 10, 2013 at 6:22 pm

    Perhaps a long shot, but nevertheless:

    If you can make QT (perhaps as inbetweens, could be QT ref files), QTchange can insert TC in the blink of an eye.
    This is because the TC is a text track (see it as a caption file)
    Now, if you’re client uses a QT compatible viewer, he’s able to see them.
    Some encoders (qt player itself of course for sure) will burn the track inside the video.
    Worth a try.

    Otherwise, there are more options to have the TC travel as a caption track, thus taking up no rendering time at all.

    hth,

    Bouke

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

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