This content has been marked as final. Show 8 replies
>Has anyone observed this extended encoding time?
Well I sure have.
One sure way to cut the encoding time is to render the timeline and then check the "Use Preview Files" in the "Export Settings" window.
In both cases below I did NOT export from Premiere. I closed Premiere and opened Adobe Media Encoder and under "File" I selected "Add Premiere Pro Sequence". This avoids using your C: drive as the source since I have a much faster RAID array for the project files
Without using the preview files on this extremely complex (editing-wise) one hour 18 minute video it took 6 hours 14 minutes to encode to MPEG2 DVD without using the preview files and it took only 42 minutes using the preview files!
This is an 8-core E5420 Xeon 2.67 GHz system
Thanks I appreciate your comments. I'm not familiar with the preview file usage and rendering on the time line but will read up on it and try it.
Much thanks for this valuable tip!!!
>One sure way to cut the encoding time is to render the timeline and then check the "Use Preview Files" in the "Export Settings" window.
That's a little deceptive, isn't it, because you must then add the render time to the export time. Is that total really any faster?
Media Encoder runs MUCH faster if you turn the Preview OFF. I have an E5420 quad-Xeon processor in an HP workstation. It renders SD video to MP2-DVD in about 1/4 real-time. It takes about 3x as long with Preview enabled. Premiere CS4 seems to do a decent job balancing the multi-processor loading.
Yes thank you for reminding us. It was so long ago that I turned off the "Preview" in AME (not to be confused with "Use Preview Files") that I forgot to mention that.
Edward, I do not know your system but with my two E5420's Adobe has done a pretty good job of balancing the multiprocessor loading with all 8 cores. Just to keep it a complete honest comparison as Jim suggested I am now timing the rendering of the timeline my post #2 above. since I rendered incrementally I did not realize how long the total timeline render actually took. More later when it finishes.
So far, with 8 cores, I haven't noticed any significant slowdowns when using Preview versus not using Preview in the AME. However, I haven't done any timed tests; my results are based solely on my own, relatively impatient observations.
Thanks for that tip. Simple actually but I just never thought about it. I will try that for sure.
Certainly, there is no substitute for the monster machines used by some of the participants in this thread. It's like comparing a four cyclinder Covair to an 8 bander (cyclinder. It would indeed be all smoke from the tires that is. I's sure I am getting all I can expect from my little 2 cyclinder (dual core) rocket which just isn't in the same class of the ture multi-cores. I would love to own one...
but I would be afraid to take one for a test drive as I am sure I wouldn't want to return the keys! Oh how I would love to...