-
native export? Why does it take 100 times longer to export a movie than in FCP?
Hi there I am pretty new to premiere,
I have to say, I love it so far.
there are a few weird little things that I wish were different, but overall its great.however, I have one major problem…
I can’t seem to figure out how to quickly export a master file for viewing.
In FCP7 this procedure takes seconds. Now im looking at 45 min. for a 5 minute movie.
I work in a REALLY time sensitive environment and I usually can export what Im working on and show it right there,
but it seems that premiere will re-render my entire sequence when I export it. So that begs the question-
why would I render my sequence at all? Most of the premiere effects will play right through the unrendered clips.please help!
i have a new retina macbook pro with CS6, everything is up to date.
I shoot with a 5dmkii.
thanks -
7 Replies
-
Premiere Pro does not use render files for output unless you tell it to (via the “Use preview files” checkbox in the output window), and it does not “smart-render” all formats like FCP7 did (copying raw frame data from the source or render container into the output container).
Pr will decompress/recompress on output for many formats (but see below for exceptions). If you choose a high-quality render format or use one of the smart-renderable formats for output, you can minimize or eliminate generational loss.
https://blogs.adobe.com/kevinmonahan/2012/10/11/smart-rendering-in-premiere-pro-cs6-6-0-1-and-later/
That said, 45 minutes strikes me is a pretty lengthy export for a 5-minute edit. What have you got going on in that sequence? The more you can tell us about your workflow (how you import files, what you’re doing to them, how you export them), the more we may be able to help.
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 -
Hey Walter thanks for the quick response!
So I have a bunch of 5dmkii clips that I import from the camera into a folder on my desktop.
I then create a project with the sequence that corresponds to DSLR. I import the clips (no compressing or anything) to work natively with them in h.264, after editing my movie I apply the curves filter and a little noise to all the clips. I also have some light leak overlays here and there. Once I am satisfied I press command M and then set the export to h.264. I have tried sending it to the queue/turning on and off the use previews button.then I wait…..
I guess I was just under the impression that I could quickly save a master copy at the current codec/resolution because I could in FCP. A HUGE reason I switched to premiere was so I could work with my files natively without having to spend time compressing everything before I edit, but if that time is spent after my edit then it isn’t really saving us that much time. I mean I could screen capture my movie and export it quicker than this.
So if I was to compress my footage to XDCAM then do my editing, the render would be nice and quick?
Is there no way to achieve that with native DSLR footage?thanks for your help, seriously. I have watched so many stupid youtube tutorials and googled my brains out trying to figure out this one.
-
[andrew barefoot] “I then create a project with the sequence that corresponds to DSLR. I import the clips (no compressing or anything) to work natively with them in h.264, after editing my movie I apply the curves filter and a little noise to all the clips. I also have some light leak overlays here and there. Once I am satisfied I press command M and then set the export to h.264. I have tried sending it to the queue/turning on and off the use previews button.”
The noise may be the culprit.
I just did a quick test with a 10 second motion graphics clip; rendering it to H.264 with the 2-pass Vimeo 1080p29.97 preset took 22 seconds on my little laptop. Adding 20% noise to the clip and rendering it to H.264 bumped that time up 2.5x to 56 seconds (ouch).
I’d be curious if you can get better times by eliminating the noise (which clobbers your compression efficiency in the output file anyway, lowering quality, increasing file size, or both) or by rendering to a different format.
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 -
[Walter Soyka] “I just did a quick test with a 10 second motion graphics clip; rendering it to H.264 with the 2-pass Vimeo 1080p29.97 preset took 22 seconds on my little laptop. Adding 20% noise to the clip and rendering it to H.264 bumped that time up 2.5x to 56 seconds (ouch).”
I should add for the sake of completeness that rendering the 10 second clip with noise applied to Uncompressed YUV 8b 422 took only 15 seconds.
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 -
Hey Walter,
So I took off the noise and that reduced the export time by a huge margin, I took 1 minute of my movie and did some tests on export times, and got it down to just 2 minutes at full quality quicktime, and 4 minutes at H.264. These were with no noise. With the noise these times were almost doubled. ALSO, my light leaks were slowing it down quite a bit because they weren’t in the same codec as the 5dmkii.
thanks for your help!
Also, times went a little quicker when i did the export straight out of premiere instead of using media encoder. I am going to see if I get faster export times by going to a thunderbolt drive instead of the desktop.
-
[andrew barefoot] “ALSO, my light leaks were slowing it down quite a bit because they weren’t in the same codec as the 5dmkii.”
Having things in different codecs on the same timeline won’t slow Premiere down like it did with FCP, but there are other reasons why you might be seeing reduced performance here.
What codec are the light leaks, and how precisely are you using them?
[andrew barefoot] “thanks for your help!”
You’re welcome!
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 -
[Walter Soyka] “I just did a quick test with a 10 second motion graphics clip; rendering it to H.264 with the 2-pass Vimeo 1080p29.97 preset took 22 seconds on my little laptop. Adding 20% noise to the clip and rendering it to H.264 bumped that time up 2.5x to 56 seconds (ouch).”
I just tried this same export on a monster workstation (a 12-core Z800 provided by HP, with 48 GB RAM, a Quadro 6000, fast RAID and PCIe SSD). The mograph footage plus noise export to H.264 that took 56 seconds on my little MacBook Pro took only 10 seconds on the workstation.
I’ll have to try a longer test sometime to get a more meaningful number.
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
Reply to this Discussion! Login or Sign Up