|
|
I usually start from presets and add only minor tweaks. Even CBR and QT P-JPEG are dog slow. At first I thought it was MB Denoiser II or a Windows firewall issue, but nope.
Rich
--- On Wed, 3/13/13, Jim Curtis <jpcurtis@me.com> wrote:
8-12 hours sounds wrong. I get fast exports from Pr to H.264. What settings are you using?
One thing I noticed will really slow exports to H.264 is to mess with the Advanced settings, so I never touch those.
And I don't use Format: Quicktime>H.264. Use H.264 under Format.
Exporting from Pr or AME is exponentially faster than exporting
to uncompressed or ProRes and transcoding in Squeeze. Squeeze only uses one or two cores, very inefficiently, whereas Pr and AME max out my 8 cores during exports.
Last week, I tried dragging an Ae comp into Pr (Dynamic Link), and then used the export settings in Pr, which are more extensive than the Output Modules in Ae. Worked very well for me.
On Mar 13, 2013, at 10:26 AM, Rich Young wrote: I don't think Adobe is doing GPU encoding yet, or it would appear in the marketing bullet points (maybe CS Next some time). Sorenson Squeeze does, and it seems to have a Premiere export plug-in.
I'm now experiencing serious export slowness in Premiere. I have Yellow lines in the Sequence and
perfect playback, but exporting takes 8-12 hours to h.264 or QT. Last year for similar material on a similar computer, it was 1 hour to render h.264 (~ 2-hr event videos). I'm not sure even magic words by Todd Kopriva will fix this.
Rich
--- On Wed, 3/13/13, Dean Forss <deanforss@gmail.com> wrote:
Hey folks,
Does anyone know if/how
the GPU is utilized in transcoding files on output in Premiere or AE with cuda support? In other words are the GPUs being utilized other than when editing?
|
|
|
|
