Complains about sluggish performance on many machines have been piling up for over a month now. Some Adobe techies confirmed issues and promised to look into it. Is there any news-worthy progress in development of a remedy or a vage forecast of when to expect a first patch?
Give your photos a professional finish with sharpening in Photoshop. Learn to enhance details, create contrast, and prepare your images for print, web, and social media.
Wasn´t expecting one tomorrow and didn´t say so. Just curious of how long a wait this could turn into. I know, you´re the one without the problem. You have a working version. I don´t. (cue sound of impatient feet tapping)
It’s bad when you get a few windows up. It always will be bad. CPUs won’t get faster any time soon. More cores won’t help. GL was an attempt to add some speed to the equation, but the problem is it all comes out like Intel’s infamous floating point error. Few ever realized there was a problem with the Intel FP (few used FP), just like some here. Some did and didn’t care (99.99679 is close enough for some), just like some here. Some were affected to the extreme, like many here. Intel recalled the CPUs and promised to never allow this to happen again. Adobe is only doing what Intel did all those years ago, only it hasn’t gotten to the stage where it admits to the fault. Knowing Adobe, it never will. Did you ever try to get a refund from Adobe? Don’t. Charge back immmediately upon discovering your error because that’s what you’ll have to do to get your money back to bring it to an end, anyway. I am, after all, and expert here.
Stonehenge (11…something) The one Adam Jerugim/Adobe has given to those, willing to volunteer for a test ride. See "disaster thread"… somewhere in the middle of the four billion posts.
@dave We´re not quite there yet, but I guess we can stop for a pee break.
I had very little difficulty in getting a refund on CS4, and the longer I keep checking back, I’m glad I did. I think "Adobe Corp" pays more attention to money than complaints.
70% of what? Minor sinus headache? 30% of migraines remaining?
Good one 🙂 Fortunately, it´s the other way round with the patch at it´s present stage. Remaining irritations are: ch..ch..choppy zoom(by mousewheel only), and moving and rotating image (hand symbol).
It´s tolerable, if you´re a forgiving nature and sort of interlace the bad framerate with the peaceful flow of your mind.
No, I didn’t try it. I may rethink the notion once the patches are released and the dust settles. My strategy has always been to skip every other version, and CS3 was my skipping point. However, I got such a good price on the CS3 upgrade that I decided to go ahead and take the plunge, setting my sights on CS5.
But, like I said, I plan to keep an eye on developments with CS4.
I agree. We were planning on CS4 upgrade. After reading this thread we do not need to degrade our work flow productivity with software bug issues. Will watch for the patch then reevaluate our need for PSCS4
Just try the evaluation copy for a month – you should see if any bugs plagues your system. you should never go by reports in an internet forum, particularly a place like this where people are likely to complain – you dont see threads recommending stable software here.
Well, Mat, I did evaluate CS4, under reasonably controlled conditions in one setup, and I don’t find CS4 to be worth it at all, as there are several deal breakers for me, particularly with respect to brushes, the palettes arrangement, the stupid, stupid "Show All" at the bottom of menus like Layers (everything I use in Layers on a regular basis is hidden, so it takes additional steps to obtain them). The default to non-floating frames is particularly odious. And I’m not the only one hating the non-floating frames. I have one floating, I open another (usually a variation on the first image) and want to click back and forth. Every time I open a new image it reverts to non- float.
The first installation to my working computer had 11 errors, but CS4 ran anyway. I suspected that CS4 loaded those from CS3. I am now certain, because, after uninstalling CS4, those parts of CS3 now behave differently, having reverted to a default position rather than my own setup.
It’s too bad that Adobe cannot supply some sort of debug logging capability, like Structured Exceptions Handling, which MS has used for at least XP on. I know damn well that, even having the same platform/chipset running simultaneously at a number of stations, not all will report bugs, and when one does, measures to replicate those have to be undertaken. You might be surprised in the number of times such investigations uncover an additional bug or three!
Regardless of the other problems you have had, I have to point out that you can customise the menus to have anything you want showing and save it out with a Workspace.
Did you ever check out the nine preloaded Workspaces? One of them might cover all you need!
Regardless of the other problems you have had, I have to point out that you can customise the menus to have anything you want showing and save it out with a Workspace.
Thanks for pointing it out, but again, it’s a step backwards in usability. I expected I could customize the menu problems but I saw no path to setting float to default, whilst allowing for the non-float to invoked,unless it’s the same as CS3, ie the F key.
So, let’s see what I do like. I like AutoTone. I like the faster Bridge, but again, a bunch of stuff needing to be deciphered and somehow accommodated added on.
I’m picky and I’ll admit it. Many third party add-ons don’t meet my criteria either. Some do, like Nik software. Intuitive from the get- go, then, when that is comfortable, you can do additional explorations.
This reminds me of the sad case of Peugeot in America. The 1971 504 was a great little car. That was before EPA standards took off in a significant way. Peugeot, instead of re-engineering the engine to accommodate these requirements, added on and added on, until the car was FAPP, a +cripple. Finally, they woke up, but too late.
But now, I have even a worse problem. CS3 no longer behaves as it was installed. Now, when I click a file in Bridge the only options I have for .tiff is either Firefox(!) or Paint 5.1. That is also true for .nef, unless I go to Open and pick RAW.
WTF!!!
Reset prefs doesn’t work, and when I do, and go to my working space, it’s some default setup instead of what I set.
I went into Windows Explorer and re-associated the extensions with the proper programs, so far as jpeg, tiff and nef are concerned. Resetting defaults in Bridge file associations did no good, nor could I find Photoshop as an option. Just Paint, FF or Browse.
Windows knows more about what extensions need to open than CS3 does.
Browse opened My Documents. I could go to C Programs etc but I don’t know what to associate it with. PS executable?
So I went to the tried and true Windows Explorer to find it.
So what else is crippled because of the cavalier abandonment attitude uninstalling CS4?
I left a copy in some thread or another of the actual files CS4 Installer couldn’t find to delete(!) so I better go find it and see if I can glean anything from that list. Most of it is obscure as to it’s function and location, and certainly, may not even be the right name for the CS3 equivalent which CS4 glommed onto. (Glommed. A tech term. Obscure analog term)
Larry, what you’re experiencing makes a persuasive argument for creating a HD image before installing trial-ware. I know I don’t need to tell you that, I’m just kind of surprised you didn’t do it.
That’s rather vague in that Adobe seems to want you to navigate to some place or another.
Dropping it into PS .exe is like finding a stray dog the belongs to someone in New York, so you drop it off at the city limits. It might work, as dogs are good at finding directions.
Windows Expolorer is more like the pound where the license is registered.
Dumb faith, I guess, Ho. I had no idea that Adobe would ever be an unknown in that department. It took a small hiccup when CS3 beta became a problem during uninstall that Adobe had a fix. They probably don’t know( or don’t care) that CS4 uninstall is a problem.
I lost more than that, dave. This was the last straw. I knew I could do a re-association but in view of the rest of the problems, I posted this as I wasn’t sure of my self any more. It kept going downhill, because before I reset prefs, .nef automatically opened in RAW with a double click on the thumb, but afterwards, no can do.
Another association lost: the Card Reader. Before, when I plugged in the card reader for the D80, a small app opened up and gave some choices. One of them was to Open in Bridge. Now, that’s gone. I have to Open Bridge Get Photos from Camera and then the reader is found. Probably that is also associated with CS4 then dropped when it was uninstalled.
This is perfectly normal. When you installed CS4, all the file types were associated to that suite. When uninstalling CS4, those associated file types does not know to revert back to CS3. I’d re-install Bridge CS3 at least.
It is true that the associations are all changed when you install CS4 and don’t change back. It would be in the realms of possibility to have the old associations restored but hey we’re talking about the "Installer Folks" as Nack <http://blogs.adobe.com/jnack/2008/11/installer_rant.html> calls them. I think they are a small tribe of elves that live near the Updater Goblins and share laughs together at the discomfiture of confused users.
However with persistence and know-how it is possible to restore the Status Quo without getting into Dire Straits.
