Return-Path: Received: from mail-ie0-f181.google.com ([209.85.223.181] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5002339 for AE-List@media-motion.tv; Wed, 13 Mar 2013 18:46:09 +0100 Received: by mail-ie0-f181.google.com with SMTP id 17so1854819iea.12 for ; Wed, 13 Mar 2013 10:53:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:content-type:message-id:mime-version:subject:date :references:to:in-reply-to:x-mailer:x-gm-message-state; bh=kYw8iA53hoAhFGSgBzVVcAy+z59ZJWFEJvynAnR7d6c=; b=H68sMZc4qqa2l8+ANM5BQFDkYXkti6XUU80rZwz+NOg6yU/CJatEUQtzbk3swej2br kOvo8NCEhW3CvHSS1U+AXX19Mq3hh3PyUGaK1McIHaPLAPb0vtHgxwBgIuyvoOQUNi3z 0k1bEufDu9X+a5762+D4HfF/Zuyp48RjE6cR8ZLP7CF26IPt3p64Hr9buDU9RUWNhNf6 OffXGeln3JebRj2HCB+7w+eg3D47Pn3RMDcDpZkDQXAThlM8NcWKsm0pA4Ysi3gYgVob s2f2VZ7e2waX7rIBeAeAigTBC0nyvUJsM2IOwt7vILPfS7SDhEZ0cDDTUnq+Z95v4ahu Rvqw== X-Received: by 10.42.68.66 with SMTP id w2mr14417741ici.6.1363197189236; Wed, 13 Mar 2013 10:53:09 -0700 (PDT) Return-Path: Received: from ?IPv6:2002:473f:ba1d:e472:ecdc:2df4:d59d:229e? ([2002:473f:ba1d:e472:ecdc:2df4:d59d:229e]) by mx.google.com with ESMTPS id ur12sm4244914igb.8.2013.03.13.10.53.07 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Mar 2013 10:53:08 -0700 (PDT) From: Carey Dissmore Content-Type: multipart/alternative; boundary="Apple-Mail=_D118FF8E-A1C1-488B-9558-3D82C04C8B84" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: [AE] transcoding in AE or Premiere Date: Wed, 13 Mar 2013 12:53:05 -0500 References: To: "After Effects Mail List" In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQlkHhi0eaKuSlFII1loBlA2XDYltoo1xkyvMF7oRHCqqM3xCUKiv/44o4KJa9OtaPr2I+kL --Apple-Mail=_D118FF8E-A1C1-488B-9558-3D82C04C8B84 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 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=20 Apple TV, iPad, iPhone 4 and newer - 720p 29.97 (for example) And see how you go=85 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 On Mar 13, 2013, at 11:39 AM, Evan Fotis wrote: > aso checking, render @ maximum depth and quality boxes gives a big hit = to render times >=20 > 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. >>=20 >> 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. >>=20 >>=20 >> On Mar 13, 2013, at 11:10 AM, Rich Young wrote: >>=20 >>>=20 >>> 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. >>>=20 >>> Rich >>>=20 >>>=20 >>> --- On Wed, 3/13/13, Jim Curtis wrote: >>> 8-12 hours sounds wrong. I get fast exports from Pr to H.264. What = settings are you using? >>>=20 >>> One thing I noticed will really slow exports to H.264 is to mess = with the Advanced settings, so I never touch those. =20 >>>=20 >>> And I don't use Format: Quicktime>H.264. Use H.264 under Format. >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>>=20 >>>=20 >>> On Mar 13, 2013, at 10:26 AM, Rich Young wrote: >>>=20 >>>>=20 >>>> 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. >>>>=20 >>>> 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. >>>>=20 >>>> Rich >>>>=20 >>>>=20 >>>> --- On Wed, 3/13/13, Dean Forss wrote: >>>>=20 >>>> Hey folks, >>>>=20 >>>> 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? >>>>=20 >>>> TIA, >>>>=20 >>>> --=20 >>>> Dean Forss >>>> Technology Consultant, 3D Artist, Interactive Designer >>>> Direct 904.557.4189 >>>>=20 >>>> Life is a wondrous adventure; embrace it, leave yesterday behind, = take risks - not to escape today's life, but to prevent it from escaping = you! >>>>=20 >>>=20 >>=20 >=20 --Apple-Mail=_D118FF8E-A1C1-488B-9558-3D82C04C8B84 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 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=85

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
On = Mar 13, 2013, at 11:39 AM, Evan Fotis <evan.fotis@gmail.com> = wrote:

=20 =20
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.co= m> 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?

TIA,

--
Dean = Forss
Technology Consultant, 3D Artist, Interactive = Designer
Direct = 904.557.4189

=
Life is a wondrous adventure; embrace it, leave yesterday behind, take risks - not to escape today's life, but to prevent it from escaping = you!

=




= --Apple-Mail=_D118FF8E-A1C1-488B-9558-3D82C04C8B84--