Return-Path: Received: from nk11p99mm-asmtpout005.mac.com ([17.158.233.226] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4779164 for AE-List@media-motion.tv; Wed, 18 Jul 2012 16:49:13 +0200 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_R7lHV7uMafSc30DwUAG8jQ)" Received: from [192.168.1.68] ([99.152.153.100]) by nk11p03mm-asmtp995.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0M7D0042Y2O9TF20@nk11p03mm-asmtp995.mac.com> for AE-List@media-motion.tv; Wed, 18 Jul 2012 14:53:00 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.260,0.0.0000 definitions=2012-07-18_05:2012-07-18,2012-07-18,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1207180128 From: Jim Curtis Subject: Re: [AE] Realworld CS6 Date: Wed, 18 Jul 2012 09:52:56 -0500 In-reply-to: To: After Effects Mail List References: Message-id: X-Mailer: Apple Mail (2.1278) --Boundary_(ID_R7lHV7uMafSc30DwUAG8jQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT I'll third my enthusiasm for Ae CS6. But, I'm afraid I can't say the same for Pr. There's a Serious Error thread on the Adobe Pr forum, with hundreds of posts from editors who are reporting that the Serious Errors, followed by an application exit, come every few seconds, making Pr absolutely unsuited for professional editing. With that knowledge, whenever I get one of these - and I've had about three so far - my heart skips a beat. Even without the Serious Errors, it's pretty unreliable for high-pressure work, or for client-in-the-room usage. With external monitoring on my Kona, it's more often out of sync than in. With or without the AJA engaged, the audio disappears, turns to noise, or is choppy. At least 3/4 of the time I hit the spacebar, the audio is MIA or crap. Except for Dynamic Link, and without a CUDA card, there is no advantage to editing in Pr over FCP or MC, IMO. Not until Adobe gets the bugs worked out. To be fair, external monitoring does rely on multiple vendors: AJA, nVidia and Apple. Hard to put the finger on Adobe for sure, but external monitoring is solid on MC6 and FCP7 and X. I was raving about the integration between Ae and Pr a few days ago, and that still goes. When it works, it's wonderful. But, it doesn't work all the time. Luckily, I haven't had a nail-biting session yet. I'm bidding on a project for an on-the-road-live-event-on-site-edit, and I'm concerned that Pr will let me down in a crunch. I'll probably cut on FCP7 instead. I don't think Pr will ever have the responsiveness of FCP or MC, based on my experience with CS 5, 5.5 and 6. You don't even get a smooth display of frames when you scrub the CTI on an un-effected clip in the source player. Avid and Apple have figured this out, but then, they don't use CUDA. Not sure why CUDA and responsive playback don't seem to be able to coexist in Pr. On Jul 16, 2012, at 8:10 AM, mike cardeiro wrote: > I'll second that. Been working in cs6 since my computer died last month and I've never looked back. The stuff I am rendering today without issue would have been plagued with out of memory issues on cs3 (from whence I came). To date I have not had a single memory issue and the new caching system is awesome. I love when I preview a section and then render it and rather than rebuilding each frame it just saves out the render from the cache...brilliant!. > > Mike Cardeiro > Editor/Animator/Compositor > D4 Creative Group - Philadelphia, PA > 215-483-4555 > ------------------------------- > Resume | samples > http://www.michaelcardeiro.com/resume/ > > > From: Chris Bobotis > To: After Effects Mail List > Sent: Friday, July 13, 2012 5:15 PM > Subject: [AE] Realworld CS6 > > To the AE team.... in case I have not said this enough, Bravo! > > The new caching is excellent and AE has been rock solid to date. > > Been pounding away (real hard) on 6 workstations (combo Mac + WIN) running a project at 5000 x 1080 @29.97 in 16bpc > > A slew of AE + third party effects and an incredible amount of assets are being handled just beautifully. Renders have been running 24/7 on these machines and on the render farm. > > Again, Bravo! > > Cheers, > Chris > mettle.com > +---End of message---+ > To unsubscribe send any message to > > --Boundary_(ID_R7lHV7uMafSc30DwUAG8jQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable I'll = third my enthusiasm for Ae CS6.

But, I'm afraid I = can't say the same for Pr.

There's a Serious Error = thread on the Adobe Pr forum, with hundreds of posts from editors who = are reporting that the Serious Errors, followed by an application exit, = come every few seconds, making Pr absolutely unsuited for professional = editing.  With that knowledge, whenever I get one of these - and = I've had about three so far - my heart skips a beat. =  

Even without the Serious Errors, it's = pretty unreliable for high-pressure work, or for client-in-the-room = usage.  With external monitoring on my Kona, it's more often out of = sync than in.  With or without the AJA engaged, the audio = disappears, turns to noise, or is choppy.  At least 3/4 of the time = I hit the spacebar, the audio is MIA or = crap.

Except for Dynamic Link, and without a = CUDA card, there is no advantage to editing in Pr over FCP or MC, IMO. =  Not until Adobe gets the bugs worked out.  To be fair, = external monitoring does rely on multiple vendors: AJA, nVidia and = Apple.  Hard to put the finger on Adobe for sure, but external = monitoring is solid on MC6 and FCP7 and X.

I = was raving about the integration between Ae and Pr a few days ago, and = that still goes.  When it works, it's wonderful.  But, it = doesn't work all the time.

Luckily, I haven't = had a nail-biting session yet.  I'm bidding on a project for an = on-the-road-live-event-on-site-edit, and I'm concerned that Pr will let = me down in a crunch.  I'll probably cut on FCP7 = instead.

I don't think Pr will ever have the = responsiveness of FCP or MC, based on my experience with CS 5, 5.5 and = 6.  You don't even get a smooth display of frames when you scrub = the CTI on an un-effected clip in the source player.  Avid and = Apple have figured this out, but then, they don't use CUDA.  Not = sure why CUDA and responsive playback don't seem to be able to coexist = in = Pr.




O= n Jul 16, 2012, at 8:10 AM, mike cardeiro wrote:

I'll second = that.  Been working in cs6 since my computer died last month and = I've never looked back.  The stuff I am rendering today without = issue would have been plagued with out of memory issues on cs3 (from = whence I came). To date I have not had a single memory issue and the new = caching system is awesome.  I love when I preview a section and = then render it and rather than rebuilding each frame it just saves out = the render from the = cache...brilliant!.

Mik= e = Cardeiro
Editor/Animator/Compositor      =             =
D4 Creative Group - Philadelphia, PA     =
215-483-4555         &nbs= p;       =
-------------------------------
Resume | = samples           &= nbsp;            =
http://www.michaelcardeiro= .com/resume/


=
From: = Chris Bobotis <chris@mettle.com>
To: After Effects Mail List = <AE-List@media-motion.tv> =
Sent: Friday, July 13, 2012 5:15 PM
Subject: [AE] Realworld CS6
=

To the AE team.... in case I have not said this enough, = Bravo!

The new caching is excellent and AE has been rock solid to = date.

Been pounding away (real hard) on 6 workstations (combo Mac = + WIN) running a project at 5000 x 1080 @29.97 in 16bpc

A slew of = AE + third party effects and an incredible amount of assets are being = handled just beautifully. Renders have been running 24/7 on these = machines and on the render farm.

Again, = Bravo!

Cheers,
Chris
mettle.com
+---End of = message---+
To unsubscribe send any message to <ae-list-off@media-motion.tv>


=

= --Boundary_(ID_R7lHV7uMafSc30DwUAG8jQ)--