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.