From: "Greg Balint" Received: from mail-qg0-f46.google.com ([209.85.192.46] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5514452 for AE-List@media-motion.tv; Sat, 28 Jun 2014 18:01:54 +0200 Received: by mail-qg0-f46.google.com with SMTP id q107so557136qgd.5 for ; Sat, 28 Jun 2014 09:01:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=gtNRVZrMZtr8GxDjYJuFmYaAdzAbXrnBmJsHmW7kYy0=; b=tKmMkaZlzfHQAu9MQgXIbmVdwiBv34NjroMaZ/43D9afTe3MrB7msmHYQFZKwpNknu 5z3x1UiBnR1hRIDHaFplqIkHgTrjkSGBgaOQ4mFsVdTi0g4Kny23G1Q8VRnJQJLsA4Ch lBMleHK7cWaACT+a2dZJKkTrLqFCpirLyS5NfHd62X5Z3GzrHjRegeMK61R0zgLxk3Xb AMHbXECPQaXt8xUJQ6k/R13wS2zmQhJEqiiT+o5xqDEJzvqxNYycYeUguHqWK7FcyeFJ w4cNHo/5QVr04iczJ7RPiErWwzTQOCULjkuSKO7RIO163FHGby35FZxt+iHISK0Nc1Rf Cl2g== MIME-Version: 1.0 X-Received: by 10.140.93.163 with SMTP id d32mr42836149qge.1.1403971313159; Sat, 28 Jun 2014 09:01:53 -0700 (PDT) Received: by 10.229.38.3 with HTTP; Sat, 28 Jun 2014 09:01:53 -0700 (PDT) Received: by 10.229.38.3 with HTTP; Sat, 28 Jun 2014 09:01:53 -0700 (PDT) In-Reply-To: References: Date: Sat, 28 Jun 2014 12:01:53 -0400 Message-ID: Subject: Re: [AE] Depreciated output formats gone completely in AE 2014 To: After Effects Mail List Content-Type: multipart/alternative; boundary=001a113956986555fc04fce78b80 --001a113956986555fc04fce78b80 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yep. That's probably my problem. I've got a 6core i7 980 with 24 gihs of ram right now. It should, however, be able to render at the same speeds with AE closed, right? I'll test. ///Greg Balint //Art Director / Motion Graphics Designer /321.514.4839 delRAZOR.com/ On Jun 28, 2014 9:22 AM, "Carey Dissmore" wrote: > I believe any slowdown to be related to insufficient RAM and/or slow > storage=E2=80=A6or both. > > I work on a 64GB ram 6/12 core i7 machine with very fast SSD cache and > RAID-0 storage and never experience a slowdown, but recently freelanced o= n > a machine that was set up with only 24GB (or was it 32GB?) of RAM, and al= so > had a gigabit-SAN storage setup, which had =E2=80=9Cadequate" throughput = but > introduced I/O latency (as they ALL do=E2=80=A6). Boy was it painful runn= ing > AE/PPro/Media Encoder simultaneously. I think the primary culprit was it > was starved for RAM. > > carey > > On Jun 26, 2014, at 11:36 AM, David Torno wrote= : > > Greg, more to your note, I actually haven't noticed a big hit with AME an= d > AE working side-by-side, but I haven't really pushed it either. I know we > stopped using H264 out of AE years ago as it still has a gamma issue. > Always have to correct it in QT on every export. X264, when it works fixe= d > that, but has been unreliable for us for years too. Always crashes and > fails within weeks of install. We've stuck to the PR4444 outputs that get > cut down to H264 in QT. Got a decent clean clip and a compressed preview. > > > --001a113956986555fc04fce78b80 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yep. That's probably my problem. I've got a 6core i7= 980 with 24 gihs of ram right now.

It should, however, be able to render at the same speeds wit= h AE closed, right?=C2=A0 I'll test.

///Greg Balint
//Art Director / Motion Graphics Designer
/321.514.4839
delRAZOR.com/
=C2=A0=C2=A0=C2=A0

On Jun 28, 2014 9:22 AM, "Carey Dissmore&qu= ot; <AE-List@media-motion.tv<= /a>> wrote:
I believe any slowdown to be related to= insufficient RAM and/or slow storage=E2=80=A6or both.

I= work on a 64GB ram 6/12 core i7 machine with very fast SSD cache and RAID-= 0 storage and never experience a slowdown, but recently freelanced on a mac= hine that was set up with only 24GB (or was it 32GB?) of RAM, and also had = a gigabit-SAN storage setup, which had =E2=80=9Cadequate" throughput b= ut introduced I/O latency (as they ALL do=E2=80=A6). Boy was it painful run= ning AE/PPro/Media Encoder simultaneously. I think the primary culprit was = it was starved for RAM.

carey


Greg, more to your note, I actually haven't noticed a big hit with AME = and AE working side-by-side, but I haven't really pushed it either. I k= now we stopped using H264 out of AE years ago as it still has a gamma issue= . Always have to correct it in QT on every export. X264, when it works fixe= d that, but has been unreliable for us for years too. Always crashes and fa= ils within weeks of install. We've stuck to the PR4444 outputs that get= cut down to H264 in QT. Got a decent clean clip and a compressed preview.<= /div>

--001a113956986555fc04fce78b80--