Return-Path: Received: from nk11p03mm-asmtp002.mac.com ([17.158.232.237] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5002223 for AE-List@media-motion.tv; Wed, 13 Mar 2013 17:12:15 +0100 Received: from [192.168.1.68] ([99.152.153.100]) by nk11p03mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-26.01(7.0.4.26.0) 64bit (built Jul 13 2012)) with ESMTPSA id <0MJL00BLQXBP3KC0@nk11p03mm-asmtp002.mac.com> for AE-List@media-motion.tv; Wed, 13 Mar 2013 16:19:03 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626,1.0.431,0.0.0000 definitions=2013-03-13_07:2013-03-13,2013-03-13,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1302030000 definitions=main-1303130096 From: Jim Curtis MIME-version: 1.0 (Apple Message framework v1283) Content-type: multipart/alternative; boundary="Apple-Mail=_BE01B008-6745-4F3B-B6CB-EEF42E26467D" Subject: Re: [AE] transcoding in AE or Premiere Date: Wed, 13 Mar 2013 11:19:01 -0500 In-reply-to: To: After Effects Mail List References: Message-id: X-Mailer: Apple Mail (2.1283) --Apple-Mail=_BE01B008-6745-4F3B-B6CB-EEF42E26467D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 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. >=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 >> 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 --Apple-Mail=_BE01B008-6745-4F3B-B6CB-EEF42E26467D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 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=_BE01B008-6745-4F3B-B6CB-EEF42E26467D--