| This doesn't sound right. While different target formats (and different source material in the timeline) will impact encode times, it shouldn't be that long.
Try choosing h264 as the format, and pick a preset like Apple TV, iPad, iPhone 4 and newer - 720p 29.97 (for example)
And see how you go…
BTW as an aside I have found that when I have any codecs based on MPEG-2 in my timeline that I get significantly slower exports due to codec handling. But that was true way back in FCP7 days too.
carye
aso checking, render @ maximum depth and quality boxes gives a big
hit to render times
FWIW neat video renders relatively fast using GPU even though it is
not listed as an accelerated FX in PR
On 13-Mar-13 18:19, Jim Curtis wrote:
You
sure it's not MB Denoiser? IIRC, that's pretty render intensive.
You could test by turning off the effects, and exporting a
section.
Other things that can produce excessive render estimates are
bad fonts, corrupt footage, and plugs that got degraded. I've
had to remove plugs and reapply them before. This may not be
what you're seeing, but I'd watch export progress go along at a
even rate, then slow to a crawl and the time remaining estimate
would go way up while it appeared that it was still rendering.
On Mar 13, 2013, at 11:10 AM, Rich Young wrote:
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?
|
|
|
