Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro 8 hour rendierng, not even a third done, are you kidding me?

  • 8 hour rendierng, not even a third done, are you kidding me?

    Posted by Kell Smith on November 13, 2015 at 1:07 pm

    So… CS6, MPB Retina, 2.7 gig I7, 16g 1600 mhz DDr3. @ hour timeline 1920×1080, mts files.

    Put a shadow/highlight filter on it, and an unsharp mask. Set if to render at maximum depth because I plan to downsize it to 720 and run it through a de-noiser.
    Put it on the grill to cook at 12:30 am. Woke up this morning at 7:30, heard it processing , and it is not even a third done. Estimated time remaining: 20 hours.

    Seriously? Is this normal or is something wrong? I don’t usually have to render out like this so I haven’t done this before.

    How can anyone possibly get a project done with times such as this? We’re not even talking about exporting yet. That’s insane.

    (It just occurred to me that I do have a gain boost on the audio tracks, meant for it to render only the video but perhaps that’s slowing it down).

    I’ll have to do some research on ways to reduce render time. But is this normal for the above-mentioned system? I’m afraid to even ask how long a similar effect would take in after effects.

    Going out of town tomorrow and just want to get these clips out. Still need to render the rest of them out, downsize them to 720, run them through a denoise filter, export and burn. But don’t have a straight week to sit and watch them cook. What is the best thing to do?

    David Baud replied 10 years, 8 months ago 8 Members · 27 Replies
  • 27 Replies
  • Tero Ahlfors

    November 13, 2015 at 1:34 pm

    [Kell Smith] “mts files. “

    AVCHD is a shitty piece of crap codec and pretty much the only one I would transcode for something that works better. AVCHD combined with effects is a nightmare even on faster computers.

    [Kell Smith] “maximum depth”

    Do you mean max depth or max quality? Maximum quality should be only used when you’re doing scaling and I wouldn’t use that when rendering the timeline. What is your preview file format? Also is there a reason you’re rendering the timeline?

  • Kell Smith

    November 13, 2015 at 2:05 pm

    The sequence settings are set for max bit depth, max render quality. Then a dialog box came up which recommended optimizing render for “memory” with those settings, so I changed that in the preferences.
    The preview format is whatever Premiere does automatically? I think it’s mpeg.
    As to rendering the timeline, I”m fixing some footage shot in low light conditions with some slight focus issues as well and wanted to add shadow/highlight to boost it a bit, and an unsharp mask while at full scale so as not to lose anything else, then was planning to put it into a 720p timeline and run a neat noise removal filter on it. That’s why I was working at full, for fear of making matters worse.
    Welcome any suggestions.
    The footage is 2 hours of MTS files, lockdown second camera so only a couple of long clips. The audio gain was boosted though in the timeline if that matters.
    This is very frustrating, it’s overdue and for the life of me I can’t seem to get this project out of my system for review. EVERYTHING I do – export, render, even upload to YT for review (which ruined my file even more) takes absolutely forever. The only think I can do is sit here day after day and watch this stupid thing cook. I’m about to do a “quick-render” – i.e. take a hammer to it.

    My fault for the footage problems, but t’s put me four days behind on another project as well. Is there a better way to approach this outputting process? It shouldn’t be this much of an issue to put a filter on it and export. What am I doing wrong?

  • Tero Ahlfors

    November 13, 2015 at 2:18 pm

    Turn off max bit depth and max render quality. Max render quality will take ages and if you’re not scaling you’re just adding useless render time. Also your footage probably doesn’t require the max bit depth toggle. Instead of wasting time rendering the timeline I would render out a full HD master file (prores or DNxHD, XDCAMHD422 might be enough as well), bring that in and denoise that.

  • Kell Smith

    November 13, 2015 at 2:27 pm

    Okay. I’ll try that. SO render it, then export out to dnxhd?
    Would there be an advantage to just outputting the sequence to dnxhd without effects, then bringing it in and applying the effects?
    I need to output this to individual clips rather than the whole timeline so that will be one more step as well. Maybe I’ll just output to clips now – put each clip in a nested timeline, render it, get it outputting to dnxhd in the queue? Thinking out loud..

    Never worked in dnxhd. What’s the best workflow all around for this? Soooo frustrating. Thank you

  • Jeff Pulera

    November 13, 2015 at 2:29 pm

    I had to use Unsharp Mask on some long videos last year to fix footage that was slightly out of focus, and yes it does take a day to render – and I was on a workstation PC, not a laptop! If you understand how Unsharp Mask actually works, then you will realize and appreciate why it takes so long. Google it. An incredible amount of calculations must take place for every single HD frame.

    As Tero asked, why the render preview? When I used Unsharp Mask and realized how slow it would be, what I did was apply ONLY the Unsharp Mask to my raw footage, and exported that raw, sharpened footage to a “lossless” codec. That was my new “original” footage to work the edit with, all sharpened up. Then I was back to normal render times for whatever else I needed to do to the footage, rather than trying to apply Unsharp at the same time as all other effects.

    You mention Denoising, and if you mean for video, that can take just as long as Unsharp Mask. Again, as above, if all my footage is noisy, I will just Denoise first thing, exporting to a lossless codec, then begin editing with that clean footage from the start. If I apply a Denoiser plugin effect in the Premiere timeline, everything grinds to a halt and I just can’t work with that applied. So I just bite the bullet and do the overnight render (export) first, then work with the new cleaned clips that behave normally.

    Back to rendering the timeline – what is the Preview Codec set to? You are adding a generation of quality loss by rendering timeline previews, and these will have to be converted again when you export. Hopefully the preview codec is decent, such as ProRes. And of course you must check “Use Previews” when exporting, or you are rendering it all from scratch again anyway. I don’t export using Previews, for best quality export using raw footage.

    I normally do not use Max Depth, as I understand that is for 10-bit footage, or effects with high bit depth. I don’t use it for my 8-bit sources. And as Tero said, do not use Max Render Quality unless the output is being scaled, like 1080 to 720 or HD to SD, only increases render times. Those checkboxes increase render times.

    You mentioned wanting to add the Denoiser after you convert to 720. That doesn’t make sense to me, because you’ve already added other effects, and rendered them out, and scaled the video, so the noise is just getting worse with each re-compression cycle. Noise doesn’t compress well due to it’s randomness. I would denoise earlier in the game. Like before doing any editing/effects.

    You’re really at a disadvantage if the footage requires both the Unsharp Mask and Denoiser. Not sure which I’d even attack first.

    Good luck with all this, and be prepared for some long waits.

    Thanks

    Jeff Pulera
    Safe Harbor Computers

  • Joe Barta iv

    November 13, 2015 at 2:33 pm

    Turn off the Maximum Bit Depth. The only time you need that is if you are working with high-end animation and/or exporting the timeline with transparency/alpha channels.

    My suggestion; change your Sequence Settings to Preview File Format QuickTime codec ProRes 422, turn off Max Bit Depth, turn off Max Render Quality. Render timeline. Export timeline as QuickTime ProRes 422, select Use Previews. Then use Media Encoder (turning on Use Maximum Render Quality) to do any downscaling and conversion to other formats.

    Joe

    Living the SuiteLife!
    Stuff for editors http://www.cafepress.com/suitelife

    http://www.facebook.com/pages/SuiteLife/1524456414462851?ref=hl

  • Kell Smith

    November 13, 2015 at 3:03 pm

    Previews are set to l-frame only mpeg and are grayed out. –?
    The reason I was downsizing to 720 before applying the denoiser is that I have so many bills this month I have to wait to buy the plugin, so I was going to use the demo which does 720. I am planning to buy the full plugin (it’s amazing) but it will be a few weeks. So it’s a workaround.

    I cannot seem to change the preview format settings anywhere. Looked in preferences, media settings, sequence settings, and tried changing them in a new sequence. Not letting me do it. What setting am I missing?

  • Duke Sweden

    November 13, 2015 at 3:22 pm

    Just to add another angle to this, not that it relates to your situation, but the other day I was rendering a 22 minute video. Some light color grading, a touch of sharpening. That’s it. I’d done a 20 minute video before and it took about 2-3 hours. I started this one at 11 p.m. and thought for sure when I got up the next morning it would be long done, but, no, it had been going for 9 hours and was still only 47% done. I had to wait another 5 hours for it to finish and when it was, I got an error message saying encoding failed!!!

    So I started it again (both times in Media Encoder), this time it said estimated completion time 3 hours 45 minutes, and that was just about how long it took. I didn’t make any changes, I just tried to encode it again. Sometimes, these computers, you know what I’m sayin’?

  • David Baud

    November 13, 2015 at 3:29 pm

    I would also refine your workflow: you should choose a lossless intermediate codec for all your high processing work on your footage. It is much less power intensive to work on a frame basis (intra-frame codec) than to work with Long GOP footage (inter-frame codec) Working directly with MPEG footage will impact how fast your cpu is capable of processing your frames.

    To find your best workflow, run a small test on 30″ or 1 min. timeline, from start to finish, and keep track of the time it takes for your computer to do it.

    If you are on a mac, I would choose Apple ProRes codec as your intermediary codec.

    Your workflow might look that way:

    Original footage -> apply FX -> render to ProRes -> ProRes to your master format
    or
    Original footage -> transcode to ProRes -> apply FX -> render to ProRes -> ProRes to your master format

    Other than your workflow, they are many other parameters that might slow down your rendering. You will need to give us a more detail description of your system setup to figure it out. For example is your footage on the same drive than your output? if it is the case you may want to consider having your footage on a fast internal hard drive and output to a RAID array drives…

    HTH,

    David Baud
    Post & VFX
    KOSMOS PRODUCTIONS
    Denver – Paris
    http://www.kosmos-productions.com

  • Joe Barta iv

    November 13, 2015 at 3:32 pm

    “Previews are set to l-frame only mpeg and are grayed out. –?”

    Create a New Sequence with the Preview setting you want and Copy/Paste your old timeline into the new.

    Joe

    Living the SuiteLife!
    Stuff for editors http://www.cafepress.com/suitelife

    http://www.facebook.com/pages/SuiteLife/1524456414462851?ref=hl

Page 1 of 3

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