My enthusiasm for Adobe products has taking a big nose dive...

I am using the full production premium CS6 suite on PC 64-bit, no issues for me. Ever.

On MacBookPro I am using FCP for dog and pony show when clients need to be impressed, I've never tried CS6 on it since I don't own it but wish I could help you.
 
Movie_Dude_3 said:
This thread comes as a shock to me. I've been editing on Premiere on a Mac for more than a year now (CS5.5+) and haven't experienced any issues. I also cut on a home PC from time to time and haven't seen anything pop up there, either, aside from a bug that wouldn't let me import a project file. The fix was relatively easy.

Maybe I'm just lucky.
Click to expand...

Awesome. Just don't update to CS6 ;) That's when our problems really started. CS5.5 was solid.
 
Last edited:
M. Gilden said:
Haha- I know, reading this thread makes it sound like the Mac version is riddled with bugs!

No cause for alarm. It isn't.
But like all things tech, put it through enough paces and something is bound to go wrong eventually. The question is, how do you handle it when it does, and is it relatively easy to recover from?

I know the mac version has gone through more hurdles than the PC one, so I'm not as surprised when I hear things like this come up. The point is, Adobe isn't necessarily the one to blame.
Click to expand...


I have been using Photoshop since 2.5... on Macs... and even the pre X days, the Mac often was more stable than the Windows equivalent. I've not upgraded a machine at work with Windows 7, but it's 'as delivered' Vista was garbage... in fact, when working on a contract for a certain large software manufacturer which will be unnamed to protect the guilty... I was given XP rather than Vista...

When running the Adobe apps on my Mac, (past and present) I've not gotten the range of failures that other have reported. The only occasion where I got a kernel exception and 'reboot', equivalent to the industry standard Blue Screen... probably was in fact due to hardware flaking out...

The problem that has caused my current distress is not in the actual Adobe After Effects program, but the ancillary install program which refuses to 'install' and exits with a vacuous 'error message', leading to no correction.

I can agree with a conjecture that because of the current complex environment that Adobe has created for the 'suite' of programs, that such complex interactions could cause more 'install' problems than when an Application was installed individually, and each perhaps had a more watertight compartment for its own 'libraries and support utilities'...

Then again, perhaps part of the Macro Media merger included creating unstable packaging, often boiling down to draconian licensing...

As it is I'm still able to run Premiere CS6 and After Effects CS6 on my aging backup machine running 10.6.8 Mac OS... which of course could strongly suggest that Apple has made some 'library' change that is causing some ripple effect elsewhere... even when I was actively developing products for Apples, the 'willynilly' changes often defied explanation. (like dumping Objective-C in favor of C++ only to have Objective-C come back...)... but I digress...
 
j1clark@ucsd.edu said:
I have been using Photoshop since 2.5... on Macs... and even the pre X days, the Mac often was more stable than the Windows equivalent. I've not upgraded a machine at work with Windows 7, but it's 'as delivered' Vista was garbage... in fact, when working on a contract for a certain large software manufacturer which will be unnamed to protect the guilty... I was given XP rather than Vista...
Click to expand...

Yeah, Vista was a trainwreck. Vista probably created more Apple users than any of Apple's own marketing!

I suffered through it for a bit because I wanted to use 64 bit apps, and XP 64 was very poorly supported (and Mac OS didn't have support for Adobe 64 at all yet). Windows 7 has been a delight and rock solid.

As it is I'm still able to run Premiere CS6 and After Effects CS6 on my aging backup machine running 10.6.8 Mac OS... which of course could strongly suggest that Apple has made some 'library' change that is causing some ripple effect elsewhere... even when I was actively developing products for Apples, the 'willynilly' changes often defied explanation. (like dumping Objective-C in favor of C++ only to have Objective-C come back...)... but I digress...
Click to expand...

Yep, that about sums it up. So don't necessarily blame Adobe. It's not entirely their fault.
 
Exact said:
Awesome. Just don't update to CS6 ;) That's when our problems really started. CS5.5 was solid.
Click to expand...

But I did upgrade to CS6 last August. I got the cloud subscription, so I have the whole suite available. Never had any issues with it except for one when I had to reinstall Premiere. Worked fine afterwards.
 
Just saw this same thing happen today on a site license, many many computers out all saying Adobe Applications Manager damaged or missing. Happened after a flash update.
 
J Davis said:
Just saw this same thing happen today on a site license, many many computers out all saying Adobe Applications Manager damaged or missing. Happened after a flash update.
Click to expand...

It looks like Adobe is juggling both an Acrobat and Flash crisis. Not sure if that would tie into the problems these users are having, especially since some go back before this week.
 
Imagine if every single day you sat down to edit you started by getting an error upon opening your project and had to hit "continue" up to 400 times before the project opens. And then, you knew that you will almost certainly freeze and crash at some point in your day. That is our experience on Premiere Pro CS6. Every single day. Without fail. On both Mac and PC computers.

After several months on CS6 on a Mac editing for 8-12 hours a day 6-7 days a week, I'm convinced its actually Premiere that's the problem, not Mac. I am one of a few editors in a team of editors that uses PPro CS6 and one of the editors is on a PC and has the same issues we do on mac. Premiere has many great features and is very quick which is what drew us to the program last summer. Now you may be able to get it running faster on a windows machine (so I've heard) but I am certain that without a doubt Premiere Pro CS6 is a VERY BUGGY program on both PC and Mac. Otherwise I would have switched over to PC. But again, our PC editor gets the same freezes, the same error messages, and has the same issues we do with certain bugs. I cannot go one full day without it freezing up, and we get errors upon starting up and exporting every single time. All of us do. Now, I'd say that 80% of the issue is the insanely buggy "Warp Stabilizer" effect that we unfortunately HAVE to use frequently (there are 3 major and repeatable bugs that will cause your system to freeze or generate errors every time without fail). The effect works great, better than "smoothcam" on the old FCP7, but unfortunately its just a buggy mess.

But aside from that it's also been very disappointing to experience Adobe's lack of updates to this program. I'd rather they updated frequently with 5 or 6 bug fixes, rather than make us wait 6 months and do a big list of them because if you don't make that list you know you're screwed for another 6 months. Plus there's always the empty feeling that they may no longer even care about CS6 since they're most likely working on CS7 now anyway. Tech support is a joke because even if they generate the same errors you do, there's nothing they can do about it. Their little "wish" form that you fill out with bugs is almost laughable. "I wish it worked like it's supposed to and didn't freeze every day".

We all really like many of the features of CS6 and 90% of the time it's a joy to work with...but then when 10% of time it's a freezing, crashing, error generating fail of a program...well, that gets annoying real fast. And mac or pc, it doesn't make one bit of difference at all.

That's our experience anyway.
 
Last edited:
I can't leave CS6 running overnight, or the machine will be unresponsive in the morning.

I can't export directly from a project reliably, because it will crash - I have to queue it to AME instead.

I can't play any media in full quality any more... I have no idea why, it'll just bog down.

I have to make "save" a twitch response after every minorly significant change, because there's a good chance it may crash for no apparent reason


This exact same machine can soldier through days of FCP7 editing without a stutter or dropped frame. Yeah, CS6 has not felt like a worthwhile upgrade in any sense... but I can sling together AVCHD material quickly, which is the only thing that's earned its keep.
 
Wait, is CS6 really so much worse than CS 5.5?
I bought an upgrade for 6, but I haven't installed it yet. Should I just sell it and stick with 5.5??

Also, is it just premiere, or are the other CS6 packages as bad (after effects, audition, etc)? Because to be honest, I spend more time in those than actually in premiere. For simple edits I actually prefer Sony Vegas, and only use Premiere for collaborating with other post houses.

Is the whole CS6 package this bad? I'm on PC by the way, and never had a problem before. You guys are scaring me.
 
I have a had none of these issues on CS5.5 through CS6. I just finished this project in it, all AVCHD on a Core 2 Quad Windows 7 x64 workstation, with no crashes, and it only bogged down with Colorista II applied to the clips (just render for preview and no issues). I did run into the "Out of memory" export bug due to some of the photos being really large, but you just disable GPU and it renders fine (and I'll have 4GB in my next GeForce upgrade to take care of that).

 
When CS6 came out, I was on a 2008 MacBook Pro. I made the upgrade from CS5 and CS6 ran better than CS5 did. After the MBP crashed, I bought a $400 Windows 7 laptop and installed CS6 on there. Again, no issues. I just finished a 7 minute doc for a client that had over 5 hours of T2i and EX1 footage. For fun, I threw all the footage onto the timeline, mixed together and didn't have a single issue. It's been so stable and the dynamic link is so awesome that I have switched completely from Vegas to Premiere.
 
nothing said:
You can install them both on the same system, no need to leave anything behind. Install cs6 and leave cs5.5 there as your security blanket to switch back to if you hate the upgrade.
Click to expand...

Well, my CS6 is actually a new license, bought for me as part of a barter project. I could either sell my 5.5 or 6 license. I think it would be silly to keep both independantly registered copies, wouldn't it?
 
dishan said:
Well, my CS6 is actually a new license, bought for me as part of a barter project. I could either sell my 5.5 or 6 license. I think it would be silly to keep both independantly registered copies, wouldn't it?
Click to expand...

Yes, as long as your CS6 license is a full version and not an upgrade.
 
You must log in or register to reply here.
Back
Top