Return-Path: Received: from mail-vc0-f169.google.com ([209.85.220.169] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4779279 for AE-List@media-motion.tv; Wed, 18 Jul 2012 18:32:17 +0200 Received: by vcbfl10 with SMTP id fl10so1315041vcb.28 for ; Wed, 18 Jul 2012 09:36:04 -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=P5GrRYgb77BoldMqd628q9Ml9kxyB5gcM5BK3lTu5VM=; b=Tch2zxzs555cXLlc6WsC4VgCC3tpFuGpShV+IFmsZ4MAgrg3Q6bkYQUfXTb1cjNyIm O/AMhjqZkKBBYneHbJB0PYvcUGRuLxuNJza5qcWPDgFpr82fS4/LVDwXjU+Y0QFzqXOl y9g10v0RBdpHOYC+hNG+IsonHfdWEjDtNtZFFEtB9AwcbKcVzDxNg2NXGA3KyVnLLvsL /sDF+gPjXsdY5pLPZH9E6CLDTDwhAeeiZtUdiEd08U1p9TKHsgB3rdxonwWT9BiEA9Dq ZdVgI4eFBtJmT9/792VerNNKYUgLoFxYsW2tKBQa9BdmWliOJLAM+mU38O5itgPMoorj 1Lpw== MIME-Version: 1.0 Received: by 10.52.23.71 with SMTP id k7mr1079185vdf.3.1342629364434; Wed, 18 Jul 2012 09:36:04 -0700 (PDT) Received: by 10.220.18.201 with HTTP; Wed, 18 Jul 2012 09:36:04 -0700 (PDT) In-Reply-To: References: Date: Wed, 18 Jul 2012 17:36:04 +0100 Message-ID: Subject: Re: [AE] Realworld CS6 From: rendernyc To: After Effects Mail List Content-Type: multipart/alternative; boundary=20cf3071c8d255092004c51d429f --20cf3071c8d255092004c51d429f Content-Type: text/plain; charset=ISO-8859-1 i have been using PP CS6 to edit my classes for FXPHD over the last 4 months and there have been MANY times where there is no audio on clips that have audio. sometimes only some clips wont play with audio. the first time this happened it completely freaked me out because even though i checked and do test recordings and knew there should be sound it seemed that none recorded. thankfully a restart of PP has usually fixed this Besides that it has been working at least as well as FCP, if not better On Wed, Jul 18, 2012 at 5:27 PM, Jim Curtis wrote: > Yes, I know most people only visit forums when they have problems, but if > you want to take half a day to read the link I provided, you'll see it's > not "one or two people." And some of the people having this issue are > gurus like you, Steve, who are expert at troubleshooting, yet flummoxed by > this severe complication. > > It is good to hear that some users are having a trouble-free experience. > > I generally do disable my Kona for the editing stage, and I have APCs for > power conditioning. But, the audio problems I mentioned persist. My Mac is > handling all the audio - no special drivers for a third party interface, > yet I have a one in four chance my audio will even sound when I hit the > spacebar. That's my main issue with Pr CS6 at this point. > > I know from previous posts that your set-up and mine are very similar. If > audio is rock solid reliable 24/7 for you, that gives me some hope I'll be > able to fix it over here. > > Sorry to repeat, but I'm not beset with the Serious Errors as some on that > thread are. I got several in rapid succession on one occasion. And having > read about how that was a job killer, I did a Full Monty: Disk Warrior, > Repair Permissions, zap PRAM, delete caches and previews, and reinstalled > Pr with fresh Preferences. That vanquished the Serious Errors for several > days. The next time I got one, I just deleted the caches and previews, and > I was back in business. > > Nobody wants Pr to shine more than I do. > > > On Jul 18, 2012, at 10: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 --20cf3071c8d255092004c51d429f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable i have been using PP CS6 to edit my classes for FXPHD over the last 4 month= s and there have been MANY times where there is no audio on clips that have= audio. sometimes only some clips wont play with audio. the first time this= happened it completely freaked me out because even though i checked and do= test recordings and knew there should be sound it seemed that none recorde= d. thankfully a restart of PP has usually fixed this

Besides that it has been working at least as well as FCP, if not better=

On Wed, Jul 18, 2012 at 5:27 PM, Jim Cur= tis <jpcurtis@me.com> wrote:
Yes, I k= now most people only visit forums when they have problems, but if you want = to take half a day to read the link I provided, you'll see it's not= "one or two people." =A0And some of the people having this issue= are gurus like you, Steve, who are expert at troubleshooting, yet flummoxe= d by this severe complication.

It is good to hear that some users are having a trouble-free= experience.

I generally do disable my Kona for th= e editing stage, and I have APCs for power conditioning. But, the audio pro= blems I mentioned persist. =A0My Mac is handling all the audio - no special= drivers for a third party interface, yet I have a one in four chance my au= dio will even sound when I hit the spacebar. =A0That's my main issue wi= th Pr CS6 at this point. =A0

I know from previous posts that your set-up and mine ar= e very similar. =A0If audio is rock solid reliable 24/7 for you, that gives= me some hope I'll be able to fix it over here.

Sorry to repeat, but I'm not beset with the Serious Errors as some on t= hat thread are. =A0I got several in rapid succession on one occasion. =A0An= d having read about how that was a job killer, I did a Full Monty: Disk War= rior, Repair Permissions, zap PRAM, delete caches and previews, and reinsta= lled Pr with fresh Preferences. =A0That vanquished the Serious Errors for s= everal days. =A0The next time I got one, I just deleted the caches and prev= iews, and I was back in business.

Nobody wants Pr to shine more than I do. =A0
=

On Jul 18, 2012, at 10: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 f= act, its mostly just them.

I've been running CS6 lon= ger than anyone. I've been running it with clients in the room just fin= e. all my editing work goes thru it and its just fine for "professiona= l" 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 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 o= f 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. =A0With that knowledge, whenever I get one of th= ese - and I've had about three so far - my heart skips a beat. =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.




--
dann= y princz

exposedideas.com --20cf3071c8d255092004c51d429f--