Return-Path: Received: from mail-bk0-f45.google.com ([209.85.214.45] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5002254 for AE-List@media-motion.tv; Wed, 13 Mar 2013 17:30:55 +0100 Received: by mail-bk0-f45.google.com with SMTP id i18so559592bkv.4 for ; Wed, 13 Mar 2013 09:37:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:disposition-notification-to:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-tagtoolbar-keys:content-type; bh=SRNNBAW84EpUEA+aiBkJhcwxx/Skh9jGdMlib9/7VUI=; b=PpYJTBCh1ai+BUQ+xcdFdwxzrtXWrbkjIM2Z7qvj2x/70NkzBBBMEW20wOBMF3mzzf T1qAVEYkdmOZoTpyyHX3X/Nib1nKduF0y/+2Ppj9EHO6XCO96BaD10KJmejIO5rXE9xz VzvV5lk48xZ2TnIhLzeCH4b9pfLBKBs0yy/qugJM4cVNdQdmoDjFJADQXE3iDNpn2+j3 h7WH/RG/yrHp0ESytYtGkzjNfiW16fHYJqlw2DifoHIaw/8DFdlvU6SSHTD59nno/e9a QxBmc2R0iW7zGaHVWHjFnOVVd8PShkN4FD9yfNdYTEsbQgQvZexNFL200/W0i+K+MoWO CLDQ== X-Received: by 10.205.138.148 with SMTP id is20mr8096484bkc.45.1363192677172; Wed, 13 Mar 2013 09:37:57 -0700 (PDT) Return-Path: Received: from [192.168.1.5] (cust-233-240.on4.ontelecoms.gr. [92.118.233.240]) by mx.google.com with ESMTPS id z6sm6235492bkv.11.2013.03.13.09.37.55 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Mar 2013 09:37:56 -0700 (PDT) Message-ID: <5140ABD8.2080902@gmail.com> Disposition-Notification-To: Evan Fotis Date: Wed, 13 Mar 2013 18:39:52 +0200 From: Evan Fotis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080914 Lightning/0.9 Thunderbird/2.0.0.17 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: After Effects Mail List Subject: Re: [AE] transcoding in AE or Premiere References: In-Reply-To: X-TagToolbar-Keys: D20130313183952627 Content-Type: multipart/alternative; boundary="------------060200030000060207090004" This is a multi-part message in MIME format. --------------060200030000060207090004 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 /> >/* 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 />> >/* 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! >>> >> > --------------060200030000060207090004 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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?

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!



--------------060200030000060207090004--