Return-Path: Received: from mail-vb0-f41.google.com ([209.85.212.41] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4779294 for AE-List@media-motion.tv; Wed, 18 Jul 2012 18:55:55 +0200 Received: by vbkv13 with SMTP id v13so1315999vbk.28 for ; Wed, 18 Jul 2012 09:59:42 -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=VkIJ/bcoHNHQFeLVI+A7Sn/kEM46N2cHGS6GY1waOn4=; b=ynJdqTyHzpAmh8vXR5Y52hPbaqEMAxI08ksLuXeFteK3F8cLmx2rr9wP8MpvhcvLVa 38QLYkNfJOyvVjbrTtm/wDH2GKX+CoRJJubdkEtM1xPX23ODzI3LkYcqLemuj8kk0ReA wf3sRNRJ/+xKJaHrCVHfB7e4KTSCEWsNLN0fy/b1GxStvjbqcMdFyzjzIm/mSI6ySG5e 5TU5ArzB0ekHxU4741x6sN8tNRn7Vz0znpE0nRCChLDKOqRDY019TZ7JEM82W5cwVera v0fL9OdVxV1o29fQfxOO6XB4r/HGpN5OO0krzg7bEet8JB6MtjlhuScNQ8N+qG+8+SSz RYxg== MIME-Version: 1.0 Received: by 10.220.141.203 with SMTP id n11mr1181784vcu.74.1342630782223; Wed, 18 Jul 2012 09:59:42 -0700 (PDT) Received: by 10.220.18.201 with HTTP; Wed, 18 Jul 2012 09:59:42 -0700 (PDT) In-Reply-To: References: Date: Wed, 18 Jul 2012 17:59:42 +0100 Message-ID: Subject: Re: [AE] Realworld CS6 From: rendernyc To: After Effects Mail List Content-Type: multipart/alternative; boundary=f46d042f93c6d6c46804c51d96d5 --f46d042f93c6d6c46804c51d96d5 Content-Type: text/plain; charset=ISO-8859-1 I dont have a ton of media but my edits have been between 1 min and 1 hour in length with the majority around 45 mins Wed, Jul 18, 2012 at 5:45 PM, James Culbertson wrote: > Well, this is generally true of forum complaints except in this case there > are a lot more than one or two, it just takes awhile for the onslaught of > "me too's" to kick in. > > I've been experimenting with Premiere CS6 as I have since CS4 or so. It > does appear now be caught up with FCP7 in terms of basic editing and > trimming. And it isn't crashing too much anymore -- only a couple of times > per session (with 10 clips or so in the project/timeline). But I have no > idea how things would be if I loaded it up with a feature length doc. > > I would say I trust Premiere CS6 about as much as FCPX 10.0.5, which is > just barely. I wouldn't use either for long form yet. > > James > > > On Jul 18, 2012, at 8:41 AM, Steve Oakley wrote: > > you know the problem with forums ? one or two people have a problem, yell > a lot, and make like EVERYONE is having problems when in fact, its mostly > just them. > > I've been running CS6 longer than anyone. I've been running it with > clients in the room just fine. all my editing work goes thru it and its > just fine for "professional" work. in fact it takes projects that simply > crushed FCP7. > > I'm going to suggest as a first step, disable using the Kona for output > and see if most if not all problems go away. if they do, then the problem > is the AJA drivers. matrox and BMD drivers have been ok. > > also in terms of sync, if you feed a monitor via HDMI, there is often 1-2 > frames of processing / delay in the monitor. this will put audio from the > card's outputs out of sync. use the monitor's speakers / audio outs to feed > real ones. > > as for those other guys, there are so many things that could be going on - > starting with as one user suggested, bad RAM. A new OS install, a drive > check may be in order. one user was using a "1TB mirrored volume (7200RPM > drives) for media" which is probably resulting in a lot of extra internal > I/O and slower media access / bottlenecking. you also don't know what other > apps they may be running at the same time, or if they have other stuff > installed on their system that can cause problems like perian codecs. > > another source of magic problems is bad power. especially in summer when > you have AC units kicking on they will put heavy loads and spikes into the > power. I recall a client's system that was randomly crashing all the time > and they were going crazy. I say in front of it and saw it crash at the > same time their window AC unit kicked in. APS solved the problem. > > I'm not denying they have problems, its just that they have not done very > good trouble shooting to figure out what is really going on, nor have they > eliminated potential problems external to PP / AE > > S > > > On Jul 18, 2012, at 9:52 AM, Jim Curtis wrote: > > 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. > > > > -- danny princz exposedideas.com --f46d042f93c6d6c46804c51d96d5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I dont have a ton of media but my edits have been between 1 min and 1 hour = in length with the majority around 45 mins

Wed, Jul 18, 2012 at 5:45= PM, James Culbertson <albion@speakeasy.net> wrote:
Well, this is generally true of forum complaints ex= cept in this case there are a lot more than one or two, it just takes awhil= e for the onslaught of "me too's" to kick in.

I've been experimenting with Premiere CS6 as I have= since CS4 or so. It does appear now be caught up with FCP7 in terms of bas= ic editing and trimming. And it isn't crashing too much anymore -- =A0o= nly a couple of times per session (with 10 clips or so in the project/timel= ine). But I have no idea how things would be if I loaded it up with a featu= re length doc.

I would say I trust Premiere CS6 about as much as FCPX = 10.0.5, which is just barely. I wouldn't use either for long form yet.<= /div>

Jam= es


On Jul 18, 201= 2, at 8:41 AM, Steve Oakley wrote:

you know the problem with forums ? one or tw= o people have a problem, yell a lot, and make like EVERYONE is having probl= ems when in fact, its mostly just them.

I've been running CS6 longer than anyone. I've been = running it with clients in the room just fine. all my editing work goes thr= u it and its just fine for "professional" work. in fact it takes = projects that simply crushed FCP7.

I'm going to suggest as a first step, disable using= the Kona for output and see if most if not all problems go away. if they d= o, then the problem is the AJA drivers. matrox and BMD drivers have been ok= .

also in terms of sync, if you feed a monitor via HDMI, = there is often 1-2 frames of processing / delay in the monitor. this will p= ut audio from the card's outputs out of sync. use the monitor's spe= akers / audio outs to feed real ones.

as for those other guys, there are so many things that = could be going on - starting with as one user suggested, bad RAM. A new OS = install, a drive check may be in order. one user was using a "1TB mirrored volume (7200RPM drives) for media" which is probably res= ulting in a lot of extra internal I/O and slower media access / bottlenecki= ng. you also don't know what other apps they may be running at the same= time, or if they have other stuff installed on their system that can cause= problems like perian codecs.

=A0another source of magic pro= blems is bad power. especially in summer when you have AC units kicking on = they will put heavy loads and spikes into the power. I recall a client'= s system that was randomly crashing all the time and they were going crazy.= I say in front of it and saw it crash at the same time their window AC uni= t kicked in. APS solved the problem.

I'm not denying they have = problems, its just that they have not done very good trouble shooting to fi= gure out what is really going on, nor have they eliminated potential proble= ms external to PP / AE

S


On Jul 18, 2012, at 9:52 AM, Jim Curtis w= rote:

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, wi= th hundreds of posts from editors who are reporting that the Serious Errors= , followed by an application exit, come every few seconds, making Pr absolu= tely unsuited for professional editing. =A0With that knowledge, whenever I = get one of these - and I've had about three so far - my heart skips a b= eat. =A0

Even without the Serious Errors, it's pretty unreli= able for high-pressure work, or for client-in-the-room usage. =A0With exter= nal monitoring on my Kona, it's more often out of sync than in. =A0With= or without the AJA engaged, the audio disappears, turns to noise, or is ch= oppy. =A0At least 3/4 of the time I hit the spacebar, the audio is MIA or c= rap.

Except for Dynamic Link, and without a CUDA card, there= is no advantage to editing in Pr over FCP or MC, IMO. =A0Not until Adobe g= ets the bugs worked out. =A0To be fair, external monitoring does rely on mu= ltiple vendors: AJA, nVidia and Apple. =A0Hard to put the finger on Adobe f= or 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. =A0When it works, it's wonderful. = =A0But, it doesn't work all the time.

Luckily,= I haven't had a nail-biting session yet. =A0I'm bidding on a proje= ct for an on-the-road-live-event-on-site-edit, and I'm concerned that P= r will let me down in a crunch. =A0I'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. =A0You don't= even get a smooth display of frames when you scrub the CTI on an un-effect= ed clip in the source player. =A0Avid and Apple have figured this out, but = then, they don't use CUDA. =A0Not sure why CUDA and responsive playback= don't seem to be able to coexist in Pr.





--
danny princz
=
exposedideas.com
--f46d042f93c6d6c46804c51d96d5--