Return-Path: Received: from mail-ie0-f176.google.com ([209.85.223.176] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5002352 for AE-List@media-motion.tv; Wed, 13 Mar 2013 18:49:44 +0100 Received: by mail-ie0-f176.google.com with SMTP id k13so1817637iea.7 for ; Wed, 13 Mar 2013 10:56:45 -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=g5hd7tgeLsNyAa/vlJNIho66/mmEZl9bjyDp7yE1nC4=; b=UFTp+5yo5ojB8RaySlL/k7qS4CM+hxe2nw6+3emUKYDrRUEJllWkYEHNYpu7Lcou7g ApBkfeYWOP9Zgoq1ArtZL9Cfrvv7fZwUuZdqt6Dlxd4Ree4EouFZSXrkfb91pY9RZ4Mb wqD7fhfD+1xTNo3nrzldi0A/ka+DhYRVsboJ7Sp795Xxibt4r0gBIDkgZpyMMBQZ0VWt OIlO8qBM/ijPvKlDKll3Ozh3TT8+B4/uznyNQ3urt7WrxBTyEtG5Vn837h7l9wihjcWR R4lvp3h0XEHP/Cdo5VtNYYJcuvvTttrQQ2T8HtsXQs8pxx3AScHGcMlbf0/rlC2XD42t ip/A== X-Received: by 10.50.56.141 with SMTP id a13mr17649018igq.24.1363197405043; Wed, 13 Mar 2013 10:56:45 -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 in10sm5880888igc.1.2013.03.13.10.56.43 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Mar 2013 10:56:44 -0700 (PDT) From: Carey Dissmore Content-Type: multipart/alternative; boundary="Apple-Mail=_DAB7A31B-1A41-4E33-B75E-22933FCC53F5" Message-Id: <13AD5297-A884-4442-9752-25F115BA07A0@imugonline.com> 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:56:41 -0500 References: To: "After Effects Mail List" In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQkZbxJ6TYQ8uiy/IDn5GwiX/iq1yT8JMrjXAMcKYhg0ptdOp1HSthnF9ign/YNqG735WDza --Apple-Mail=_DAB7A31B-1A41-4E33-B75E-22933FCC53F5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Oh BTW my understanding is this regarding CUDA support for exporting: If exporting from Premiere, and your timeline has CUDA-powered effects = on clips, those functions (only) are accelerated during the export. If doing from Media Encoder, they are done on the CPU.=20 Carey On Mar 13, 2013, at 12:53 PM, Carey Dissmore = wrote: > 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. >=20 > Try choosing h264 as the format, and pick a preset like=20 > Apple TV, iPad, iPhone 4 and newer - 720p 29.97 > (for example) >=20 > And see how you go=85 >=20 > 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. >=20 > carye > On Mar 13, 2013, at 11:39 AM, Evan Fotis wrote: >=20 >> 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 >=20 --Apple-Mail=_DAB7A31B-1A41-4E33-B75E-22933FCC53F5 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Oh = BTW my understanding is this regarding CUDA support for = exporting:

If exporting from Premiere, and your = timeline has CUDA-powered effects on clips, those functions (only) are = accelerated during the export.
If doing from Media Encoder, = they are done on the = CPU. 

Carey

On = Mar 13, 2013, at 12:53 PM, Carey Dissmore <carey@imugonline.com> = wrote:

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=_DAB7A31B-1A41-4E33-B75E-22933FCC53F5--