Views
2061
Replies
63
Status
Closed
MacBook Pro 16” Mockups 🔥
– in 4 materials (clay versions included)
– 12 scenes
– 48 MacBook Pro 16″ mockups
– 6000 x 4500 px
Excellent Summary Concerning Optimizing Photoshop CS2 Performance
This IMHO should have been available within 7-days of commercial release of CS2.
Maybe it was?
Maybe it was?
should have been available within 7-days of commercial release of CS2.
It was in the Adobe Knowledge base at least as early as June 13 – maybe earlier.
shel
It was in the Adobe Knowledge base at least as early as June 13 – maybe earlier.
shel
So that tells me the smokscreen for CS2 ("it’s your computer, not Photoshop") was well known before CS2 was even released.
Shame on Adobe 🙁
Shame on Adobe 🙁
was well known before CS2 was even released
Last edited 10/25/05 – it’s obviously a work in progress, so what was known or not known at which time might be a little fuzzy to say for certain.
Last edited 10/25/05 – it’s obviously a work in progress, so what was known or not known at which time might be a little fuzzy to say for certain.
Joe Joe – huh? What smokescreen? What are you talking about?
I’m referring to the constant complaints and problems with the performance of CS2, and the standard reply of, "Photoshop is absolutely great and wonderful, if you are having problems with CS2 there is something wrong with your computer".
I don’t personally know a single graphic artist that uses CS2 in their work any more. The only one I did know finally gave up on CS2 just this week, and reverted back to CS. Her computer, while not the latest, does work just fine, too.
I don’t personally know a single graphic artist that uses CS2 in their work any more. The only one I did know finally gave up on CS2 just this week, and reverted back to CS. Her computer, while not the latest, does work just fine, too.
<shaking head> Sigh. And here I was, thinking I was a graphic artist.
Joe Joe, we know you have (had*) serious problems with CS2 and you have my deepest sympathy.
But it’s about time you realised that, since you are in a minority, your sweeping statements do look a bit ridiculous.
You will also notice that Adobe has acknowledged the problems and stated that they are working on them. They are also asking repeatedly for those with the problems to give them information that will help identify the cause and find a solution.
Be positive!
*Was it you that got a refund?
But it’s about time you realised that, since you are in a minority, your sweeping statements do look a bit ridiculous.
You will also notice that Adobe has acknowledged the problems and stated that they are working on them. They are also asking repeatedly for those with the problems to give them information that will help identify the cause and find a solution.
Be positive!
*Was it you that got a refund?
C’mon JJ lighten up.
Joe Joe by the sound of it has experienced grief and no amount of defensive action can undo that grief. It takes time to build shattered confidence but it can and should be done.
Joe Joe by the sound of it has experienced grief and no amount of defensive action can undo that grief. It takes time to build shattered confidence but it can and should be done.
Yep 🙂
You’re 100% right, deebs. I will take your advice to heart 🙂
Ah. I didn’t realize that JJ had some acknowledged problems.
Sorry for being a bit snotty, but I think John captured the sentiments pretty well. That said, if you’ve had significant issues, I know how it feels.
In my case, there is an error in batch processing. The solution is for me to wait for the upgrade (which I have to pay for) to get it fixed. So I know how frustrating it is.
Peace,
Tony
Sorry for being a bit snotty, but I think John captured the sentiments pretty well. That said, if you’ve had significant issues, I know how it feels.
In my case, there is an error in batch processing. The solution is for me to wait for the upgrade (which I have to pay for) to get it fixed. So I know how frustrating it is.
Peace,
Tony
I wonder if that is a new policy>
Rather than designing in obselesence, design in dysfunctionality that can only be resolved by purchasing the new (and expensive) upgrade?
Shoot me down somebody…
Rather than designing in obselesence, design in dysfunctionality that can only be resolved by purchasing the new (and expensive) upgrade?
Shoot me down somebody…
I’m in complete agreement with Joe Joe. Adobe knew, or should have known that there were serious problems with CS2’s performance and adjusted their system requirements accordingly. YrbkMgr’s statement "The solution is for me to wait for the upgrade (which I have to pay for) to get it fixed." is the heart of my animosity toward Adobe. I resent in the extreme that I have to wait for the next version and pay for bug fixes for the version that I have. Adobe should be very, very ashamed of the way they treat not just their customers, but also for the lack of support for their flagship product.
Isn’t anyone going to pick this up and address the serious issues raised?
Can we, as consumers, purchasers and customers expect a repeat with CS3?
If so, what are the proposed resolutions?
Can we, as consumers, purchasers and customers expect a repeat with CS3?
If so, what are the proposed resolutions?
I don’t really think there’s anything we consumers can do to force Adobe to fix their products…after all, if that’s what they want to promote and sell, it’s really only their business.
And for those willing to put up with it and pay for fixes, well, that’s their business, too. Except these folks should realize they are being taken for a ride. But maybe they don’t really care?
The only reasonable alternative is to ask for a refund if you’re not satisfied. And Adobe has enough integrity to give refunds to seriously dissatisfied customers, as I can attest.
And for those willing to put up with it and pay for fixes, well, that’s their business, too. Except these folks should realize they are being taken for a ride. But maybe they don’t really care?
The only reasonable alternative is to ask for a refund if you’re not satisfied. And Adobe has enough integrity to give refunds to seriously dissatisfied customers, as I can attest.
tmalcolm – no, Adobe didn’t know of any problems or Photoshop wouldn’t have shipped.
And Adobe still doesn’t know why some users are seeing problems when most aren’t, because most of those users seem more interested in whining than helping figure out the problem on their system.
And Adobe still doesn’t know why some users are seeing problems when most aren’t, because most of those users seem more interested in whining than helping figure out the problem on their system.
And Adobe still doesn’t know why some users are seeing problems when most aren’t, because most of those users seem more interested in whining than helping figure out the problem on their system.
I find that very hard to believe. The reports of performance problems are so widespread (Google "CS2 performance" if you don’t believe me) that I can only conclude that either Adobe did indeed know of the performance problems and chose to ignore them or that Adobe’s QA department is so incompetent that they didn’t see anything wrong. And you’ll have to define "most". If 10% of 1,000,000 customers have a problem, that’s 100,000 users. Obviously an insignificant number in your world.
Those of us who do whine about it do so because it’s a problem. We’re not imagining it and we don’t do it for the sheer joy of whining. We do it to get it through the thick skulls at Adobe that CS2 needs to be fixed. Maybe if Adobe spent less time blaming everything but their sacred CS2 code and started looking at ways to fix, it would get fixed. And customers wouldn’t be forced to wait for 18 months for the next version and then pay for what should have been patched within weeks of release.
I find that very hard to believe. The reports of performance problems are so widespread (Google "CS2 performance" if you don’t believe me) that I can only conclude that either Adobe did indeed know of the performance problems and chose to ignore them or that Adobe’s QA department is so incompetent that they didn’t see anything wrong. And you’ll have to define "most". If 10% of 1,000,000 customers have a problem, that’s 100,000 users. Obviously an insignificant number in your world.
Those of us who do whine about it do so because it’s a problem. We’re not imagining it and we don’t do it for the sheer joy of whining. We do it to get it through the thick skulls at Adobe that CS2 needs to be fixed. Maybe if Adobe spent less time blaming everything but their sacred CS2 code and started looking at ways to fix, it would get fixed. And customers wouldn’t be forced to wait for 18 months for the next version and then pay for what should have been patched within weeks of release.
No, they’re not really that widespread.
Yes, a few people are being quite vocal – but they’re also the ones being least helpful in finding the causes.
How about you stop whining and help us figure out why your system shows problems when most users are not seeing those problems? (face it: most of the problems people report are actually configuration or preference issues on their system, not a bug in the software).
Yes, a few people are being quite vocal – but they’re also the ones being least helpful in finding the causes.
How about you stop whining and help us figure out why your system shows problems when most users are not seeing those problems? (face it: most of the problems people report are actually configuration or preference issues on their system, not a bug in the software).
Chris, for example, you know about mouse lag (and 100% CPU usage) when Info palette open. It makes us to reduce hardware acceleration in Display properties. I think that needs to be corrected. Doesn’t?
And all others throughout the list of issues mentioned in these forums… 🙂
And all others throughout the list of issues mentioned in these forums… 🙂
Chris, that’s not at all what I see in my little world.
Every graphics artist I know – and I know a few 😉 – has now dumped PS CS2 and gone back to PS CS.
Adobe and the PS CS2 problems are still pretty common subjects around the water cooler, although that seems to be settling down as people give up on it.
Believe it or not. PS CS2 is a real dog.
Every graphics artist I know – and I know a few 😉 – has now dumped PS CS2 and gone back to PS CS.
Adobe and the PS CS2 problems are still pretty common subjects around the water cooler, although that seems to be settling down as people give up on it.
Believe it or not. PS CS2 is a real dog.
Pipkin – I’ve said that we know about it. But I can’t comment beyond that.
Joe Joe – well, I’m sorry your little world doesn’t resemble the rest of the world.
But you either need to put up (and help find the cause of the slowdown on YOUR system) or shut up.
But you either need to put up (and help find the cause of the slowdown on YOUR system) or shut up.
Thank you, Chris. I still remember that you know it. As for me, I am working with CS2 with pleasure and it’s minor faults don’t put me into depression 🙂
Chris
Your arrogant attitude is astounding.
If you remember back when PS CS2 came out, I was one of the first guiena pigs to actually buy and install it. I sent you numerous files and all the data you requested regarding the issues we had.
And you did absolutely NOTHING to get any of the problems resolved.
Eventually, after six months of trying, Adobe issued a refund.
"Put up or shut up"?
It’s about time YOU put up, little man.
Your arrogant attitude is astounding.
If you remember back when PS CS2 came out, I was one of the first guiena pigs to actually buy and install it. I sent you numerous files and all the data you requested regarding the issues we had.
And you did absolutely NOTHING to get any of the problems resolved.
Eventually, after six months of trying, Adobe issued a refund.
"Put up or shut up"?
It’s about time YOU put up, little man.
Calm down folks. I’m not in the habit of putting words in Chris’ mouth cuz "that ain’t sanitary", but consider this for just a second…
Adobe <cough> Chris wants users to have a pleasant experience. His name is on the product. But he’s fielding non-scientific data collection and flailing accusations of a conspiracy and cover up.
Now, there may indeed be a conspiracy and cover up, but those of us who have had the pleasure of Chris’ expert help understand that he wouldn’t be one of the ones at the bottom of it.
I don’t want to be snotty, and Chris can take care of himself, but I challenge anyone to say that Chris is just lazy and doesn’t care. Compare the support from a guy like Chris in a company the size of Adobe to any other company. If there’s a problem with his baby, he wants to find it. But he needs help.
Now in Joe Joe’s case, if documents were exchanged, selectors were mingling with selectees, so to speak, then maybe he’s got a point in as much as being disappointed. But I don’t think the notion that the PS teams ass reputation is on the line with every release should be forgotten.
If we get along nicely, the problems will get resolved.
In my case, yes, I have to essentially pay for a fix. But you know what? They admitted it. They didn’t run from it and say I was nutz. I don’t like it and don’t think it’s fair, but it’s the best that can be done, and I understand it.
Sorry, we will now resume our regularly scheduled program…
Adobe <cough> Chris wants users to have a pleasant experience. His name is on the product. But he’s fielding non-scientific data collection and flailing accusations of a conspiracy and cover up.
Now, there may indeed be a conspiracy and cover up, but those of us who have had the pleasure of Chris’ expert help understand that he wouldn’t be one of the ones at the bottom of it.
I don’t want to be snotty, and Chris can take care of himself, but I challenge anyone to say that Chris is just lazy and doesn’t care. Compare the support from a guy like Chris in a company the size of Adobe to any other company. If there’s a problem with his baby, he wants to find it. But he needs help.
Now in Joe Joe’s case, if documents were exchanged, selectors were mingling with selectees, so to speak, then maybe he’s got a point in as much as being disappointed. But I don’t think the notion that the PS teams ass reputation is on the line with every release should be forgotten.
If we get along nicely, the problems will get resolved.
In my case, yes, I have to essentially pay for a fix. But you know what? They admitted it. They didn’t run from it and say I was nutz. I don’t like it and don’t think it’s fair, but it’s the best that can be done, and I understand it.
Sorry, we will now resume our regularly scheduled program…
Can I add my tuppen’orth?
A good and non-emotional analysis of past events is nought on its own. It somehow has to feedback into policies, procedures and practices with a view to avoiding similar circumstances ever again.
That is an ideal situation.
Part of me wonders if the program "Photoshop" is indeed ok but the consumer package …. well, I wonder if a few bots have been added for security and the like?
I do wonder if, for example, program holdups are caused by bot checks?
If there are security bots in the consumer package we’re hardly ever likely to find out as consumers because it is a security feature?
A good and non-emotional analysis of past events is nought on its own. It somehow has to feedback into policies, procedures and practices with a view to avoiding similar circumstances ever again.
That is an ideal situation.
Part of me wonders if the program "Photoshop" is indeed ok but the consumer package …. well, I wonder if a few bots have been added for security and the like?
I do wonder if, for example, program holdups are caused by bot checks?
If there are security bots in the consumer package we’re hardly ever likely to find out as consumers because it is a security feature?
As a ps:
In one post a 44 KB JPEG takes 25 seconds to load when the machine is linked to a network.
Instantaneous to load if not.
If my understanding is correct these timings hold whichever way round the network options are: connected => standalone, or standalone => connected
My conclusions: it ain’t Photoshop it’s a package bot-check possibly with program holdups while the bot is running and waiting for a confirmation flag
In one post a 44 KB JPEG takes 25 seconds to load when the machine is linked to a network.
Instantaneous to load if not.
If my understanding is correct these timings hold whichever way round the network options are: connected => standalone, or standalone => connected
My conclusions: it ain’t Photoshop it’s a package bot-check possibly with program holdups while the bot is running and waiting for a confirmation flag
My conclusions: it ain’t Photoshop it’s a package bot-check possibly with program holdups while the bot is running and waiting for a confirmation flag
Could I borrow your tinfoil hat? We might be on to something here.
Could I borrow your tinfoil hat? We might be on to something here.
Of course! It’s in the post 🙂
ps – if it is I think Chris may be due a whole bundle of thanks for taking flak for something that may be out of his direct influence?
ps – if it is I think Chris may be due a whole bundle of thanks for taking flak for something that may be out of his direct influence?
(face it: most of the problems people report are actually configuration or preference issues on their system, not a bug in the software).
Well, if the problems show up as a result of front panel selections or a combination of front panel selections, then the problem lies squarely in Adobe’s lap, IMO. So long as the machine meets the minimum requirements this should be the mantra at Adobe. Maybe the fix is to up those requirements or to flag components that can introduce these problems with the stated configurations. I notice that with Aperture, two specs are issued for the product, the mins and the optimum. They name names for their recommended components which the user can access. So far, what I have seen flagged here and with earlier products is the video card, suggesting the mins here. Some userer shared their experiences good and bad with various video cards. This is not acceptable. The vast majority of users here are not engineers. Going this route with PS problems is no different than getting Internet advice on health issues off chat rooms.
When I worked at Tektronix, a major issue was front panel configurations. Could a user get into trouble with certain knob, switch and signal combinations? If so we fixed it, and if it was a retrofit we did it with mod kits, information updates and/or manual revisions (absolutely the best instruction manuals I ever saw). I can recall but one instance that a fix had to be incorporated into basic design, and came out in subsequent instruments (beam finder). And these instruments were used mostly by people who knew what was going on inside the box.
I think Adobe needs to do the same. It’s much more complex, of course, as the combination of hardware, software and preferences are so vast. Reports comming back from we, the users, can alert Adobe to these issues, allowing for Adobe to replicate these conditions as best as possible. So long as we can configure from the front panel, so to speak (no one going in and tweaking code) Adobe needs to take a hard look.
Adobe does not have to try all the possible combinations, just those which become persistent, if only minor, so far as user count is concerned.
One line statements as to possible cause is not going to help, only alienate certain users who complain loud and clear.
The squeaky wheel gets the grease, and on a train whose length is over a mile, that’s lots of wheels to inspect!
Well, if the problems show up as a result of front panel selections or a combination of front panel selections, then the problem lies squarely in Adobe’s lap, IMO. So long as the machine meets the minimum requirements this should be the mantra at Adobe. Maybe the fix is to up those requirements or to flag components that can introduce these problems with the stated configurations. I notice that with Aperture, two specs are issued for the product, the mins and the optimum. They name names for their recommended components which the user can access. So far, what I have seen flagged here and with earlier products is the video card, suggesting the mins here. Some userer shared their experiences good and bad with various video cards. This is not acceptable. The vast majority of users here are not engineers. Going this route with PS problems is no different than getting Internet advice on health issues off chat rooms.
When I worked at Tektronix, a major issue was front panel configurations. Could a user get into trouble with certain knob, switch and signal combinations? If so we fixed it, and if it was a retrofit we did it with mod kits, information updates and/or manual revisions (absolutely the best instruction manuals I ever saw). I can recall but one instance that a fix had to be incorporated into basic design, and came out in subsequent instruments (beam finder). And these instruments were used mostly by people who knew what was going on inside the box.
I think Adobe needs to do the same. It’s much more complex, of course, as the combination of hardware, software and preferences are so vast. Reports comming back from we, the users, can alert Adobe to these issues, allowing for Adobe to replicate these conditions as best as possible. So long as we can configure from the front panel, so to speak (no one going in and tweaking code) Adobe needs to take a hard look.
Adobe does not have to try all the possible combinations, just those which become persistent, if only minor, so far as user count is concerned.
One line statements as to possible cause is not going to help, only alienate certain users who complain loud and clear.
The squeaky wheel gets the grease, and on a train whose length is over a mile, that’s lots of wheels to inspect!
Hmmm, I just re-read my post and realize that today’s business model has no room for such a perspective on product responsibility. Tek’s attitude is now rather quaint, even naive.
And what’s wrong with yesterdays values?
I think yesterday’s values would just set standards which, in today’s bean counting environment, are unattainable.
Especially with an organisation like Adobe Inc. where, even within one application, the compartmentalised work division makes communication difficult and effective overall engineering management a distant target.
I think yesterday’s values would just set standards which, in today’s bean counting environment, are unattainable.
Especially with an organisation like Adobe Inc. where, even within one application, the compartmentalised work division makes communication difficult and effective overall engineering management a distant target.
the compartmentalised work division makes communication difficult and effective overall engineering management a distant target.
You said it. The woes of success. It’s irony.
You said it. The woes of success. It’s irony.
" the compartmentalised work division makes communication difficult and effective overall engineering management a distant target."
That’s not a woe of success.
That’s meltdown & ultimate failure if not corrected.
That’s not a woe of success.
That’s meltdown & ultimate failure if not corrected.
It also suggests that there is no named individual to take corporate responsibility for a product nor to oversee product development
That’s not a woe of success.
Sure it is. Are you telling me that Adobe started that way? As the organization gets bigger, the dynamics change – logrithmically.
It also suggests that there is no named individual to take corporate responsibility for a product nor to oversee product development
No it doesn’t suggest that in the slightest. It simply states (not suggests) that communication is difficult and overall engineering management is a tough target to hit. It does not speak to responsibility, only difficulty.
Sure it is. Are you telling me that Adobe started that way? As the organization gets bigger, the dynamics change – logrithmically.
It also suggests that there is no named individual to take corporate responsibility for a product nor to oversee product development
No it doesn’t suggest that in the slightest. It simply states (not suggests) that communication is difficult and overall engineering management is a tough target to hit. It does not speak to responsibility, only difficulty.
the compartmentalised work division makes communication
difficult and effective overall engineering management a distant target.
You said it. The woes of success. It’s irony.
Space shuttle.
Ah well, let’s hope the merger brings a new lease of life.
It does give an impression that internal politiking is more or becoming more important than it should be?
It does give an impression that internal politiking is more or becoming more important than it should be?
Look, anyone here ever had a manager? Did you do everything that manager wanted to his or her satsifaction? Was your manager always right? Did you ever work on a team that had different priorities than another, complementary team?
It’s awful nice to have these ideas about how to run a multi-billion dollar organization, but I have a sneaking suspicion that if it were that easy, everyone would do it.
It’s awful nice to have these ideas about how to run a multi-billion dollar organization, but I have a sneaking suspicion that if it were that easy, everyone would do it.
Space shuttle.
Right on point.
Right on point.
Look, anyone here ever had a manager?
Had one; was one end result: left the company (and the entire industry) which, apart from the end product, bore an uncanny resemblance to the Adobe of today.
Remember this?
< http://www.storyphoto.com/multimedia/multimedia_photoshop.ht ml>
….thats how it was once.
🙁
Had one; was one end result: left the company (and the entire industry) which, apart from the end product, bore an uncanny resemblance to the Adobe of today.
Remember this?
< http://www.storyphoto.com/multimedia/multimedia_photoshop.ht ml>
….thats how it was once.
🙁
Tektronix had much the similar beginnings, with Howard Vollum bringing home his pet scope schematics from WWII radar work. He ran an appliance repair shop on the ground floor and built oscilloscopes on the second. The local big banks laughed at his applications for loans. One didn’t and the rest is history, for both Tek and the bank.
An interesting sidebar: An elderly woman took liking for Howard because he was so thorough in his appliance repairs. After Tek got going and moved to larger quarters, she came looking for him because she needed a repair job done. He promptly left his office and went to fix the appliance.
You ask who is in charge. As the Product Evaluation person on a specific project, we had complete control, and could stop a project for cause anywhere after what was called "A" Phase (the designers were king then). I damn near got fired because at the last minute, I got cold feet and didn’t get into the head of engineering’s face about some disturbing results in a pilot run. Please my boss? Stand up for what you know, and he got right behind you. Wimp out and you are out.
The best guy I ever worked for(with).
BTW, my comment on business plans was meant to be sarcastic.;-)
An interesting sidebar: An elderly woman took liking for Howard because he was so thorough in his appliance repairs. After Tek got going and moved to larger quarters, she came looking for him because she needed a repair job done. He promptly left his office and went to fix the appliance.
You ask who is in charge. As the Product Evaluation person on a specific project, we had complete control, and could stop a project for cause anywhere after what was called "A" Phase (the designers were king then). I damn near got fired because at the last minute, I got cold feet and didn’t get into the head of engineering’s face about some disturbing results in a pilot run. Please my boss? Stand up for what you know, and he got right behind you. Wimp out and you are out.
The best guy I ever worked for(with).
BTW, my comment on business plans was meant to be sarcastic.;-)
I guess the bottom line will probably be: while the USD keep rolling in don’t panic. keep a low profile and let it blow over
while the USD keep rolling in don’t panic. keep a low profile and let it blow over
You can’t be serious. That may be true for our friends in Redmond, but I’ve never seen that with the photoshop team (although I HAVE seen it with the Acrobat team).
Point is though, I think being overly critical and slinging mud with the amount of input we have, and the amount of intelligent answers we get from Chris is the wrong thing to do.
Most people say "hey, it isn’t my job to help Adobe troubleshoot. Damn it, they should just make an excellent product that does everything everyone wants all the time, has new features all the time and operates the same way regardless of platform. I don’t care that Windows is poorly documented, or doesn’t operate like it’s supposed to. I don’t care that Redmond keeps giving Adobe crap to fix or workaround either due to poor documentation, ignorance or stupidity, or all three. It should just work, and always work, in all situations."
Maybe you’d be right. But I’ve rarely seen a company that can meet that mark that are the size of Adobe – in fact, never.
It’s not a magic box you know. It’s run by people. Chris is telling us to help them find YOUR problems so that they can document it, anticipate it, or at least support it. If they can’t reproduce it, whose problem is it – anyway?
You can’t be serious. That may be true for our friends in Redmond, but I’ve never seen that with the photoshop team (although I HAVE seen it with the Acrobat team).
Point is though, I think being overly critical and slinging mud with the amount of input we have, and the amount of intelligent answers we get from Chris is the wrong thing to do.
Most people say "hey, it isn’t my job to help Adobe troubleshoot. Damn it, they should just make an excellent product that does everything everyone wants all the time, has new features all the time and operates the same way regardless of platform. I don’t care that Windows is poorly documented, or doesn’t operate like it’s supposed to. I don’t care that Redmond keeps giving Adobe crap to fix or workaround either due to poor documentation, ignorance or stupidity, or all three. It should just work, and always work, in all situations."
Maybe you’d be right. But I’ve rarely seen a company that can meet that mark that are the size of Adobe – in fact, never.
It’s not a magic box you know. It’s run by people. Chris is telling us to help them find YOUR problems so that they can document it, anticipate it, or at least support it. If they can’t reproduce it, whose problem is it – anyway?
Well, I speak from experience on these matters.
Yes, I corresponded with Adobe on every problem I encountered.
I sent files – lots of files – and detailed descriptipions, screen shots, and discussion on these problems.
Was there a problem with my computer? No one could find any. Drivers, OS, etc., were analyzed and nothing was found that could possibly affect the operation of PS CS2.
PS CS2 is the single, only, application that does not run on many late model and high performance computers. Including mine.
"Chris is telling us to help them find YOUR problems so that they can document it, anticipate it, or at least support it. If they can’t reproduce it, whose problem is it – anyway?"
There you go. "Photoshop is wonderful and grand; if you have any problem with it it’s because of your computer."
No, it’s not because of my computer. I am not stupid.
It’s because of crap software.
Put up, Adobe.
Yes, I corresponded with Adobe on every problem I encountered.
I sent files – lots of files – and detailed descriptipions, screen shots, and discussion on these problems.
Was there a problem with my computer? No one could find any. Drivers, OS, etc., were analyzed and nothing was found that could possibly affect the operation of PS CS2.
PS CS2 is the single, only, application that does not run on many late model and high performance computers. Including mine.
"Chris is telling us to help them find YOUR problems so that they can document it, anticipate it, or at least support it. If they can’t reproduce it, whose problem is it – anyway?"
There you go. "Photoshop is wonderful and grand; if you have any problem with it it’s because of your computer."
No, it’s not because of my computer. I am not stupid.
It’s because of crap software.
Put up, Adobe.
You guys are just great.
You are certainly wonderful too, johnkissane3.
Thank you for your insightful and thoughtful addition to the thread.
Thank you for your insightful and thoughtful addition to the thread.
Documenting your problems but finding the trouble are two vastly different things Tony. We need not find the trouble. Documenting problems and defining your system is all a novice and many times, experienced people can do. Troubleshooting is for the experts. I sense that many here are not satisfied with the process by a long shot.
Joe Joe,
No, it’s not because of my computer. I am not stupid.
I know, I know. I also know that it must absolutely rot to continually have troubles.
It was just a long-winded way to say that it isn’t easy to solve these kinds of problems and I am convinced that it’s not intentional. I would also add, that if they do know what may be causing problems for users they probably wouldn’t say unless they had a fix waiting, upgrade or patch.
But I don’t think that any of my particular diatribe should be construed to mean that users shouldn’t continually hold their feet to the fire and demand excellence.
Peace,
Tony
No, it’s not because of my computer. I am not stupid.
I know, I know. I also know that it must absolutely rot to continually have troubles.
It was just a long-winded way to say that it isn’t easy to solve these kinds of problems and I am convinced that it’s not intentional. I would also add, that if they do know what may be causing problems for users they probably wouldn’t say unless they had a fix waiting, upgrade or patch.
But I don’t think that any of my particular diatribe should be construed to mean that users shouldn’t continually hold their feet to the fire and demand excellence.
Peace,
Tony
I have a RAM test sent to me by MS which, when written to a floppy and inserted on bootup, will run a comprehensive test of your memory system. It caught a problem I had with a particular stick. I can e-mail a copy if you would like to try it.
Adobe didn’t know of any problems or Photoshop wouldn’t have shipped.
Total nonsense. Upgrade schedules for Creative Suite are driven by revenue stream requirements, not by whether an upgrade is ready for shipment.
Or are you REALLY trying to claim that the pathetic state of Bridge 1.0.0 was unknown to Adobe before it shipped?
Total nonsense. Upgrade schedules for Creative Suite are driven by revenue stream requirements, not by whether an upgrade is ready for shipment.
Or are you REALLY trying to claim that the pathetic state of Bridge 1.0.0 was unknown to Adobe before it shipped?
can’t be much worse than the Browser in CS. I just re-opened a rather large folder to purge it of unnecessary versions of the same image, and the damn program wants to "Generate Previews" again, locking me out of selecting files and deleting them until the program is damn well ready to let me.
Can you imagine having to go back to get a mug shot out of thousands and having the computer tell you to wait until it does it’s predetermined chores?
This sucks and because of the complaints about Bridge(first among others,) I steadfastly refuse to pay for CS2.
Can you imagine having to go back to get a mug shot out of thousands and having the computer tell you to wait until it does it’s predetermined chores?
This sucks and because of the complaints about Bridge(first among others,) I steadfastly refuse to pay for CS2.
Does Cris Cox really think people will believe him when he says if people let Adobe know the particulars of the problem theyll fix it? Is the Adobe team practicing a new policy?
I dont own CS2 because I felt more than ignored by Adobe with the CS re-activation issue. I reported the problem several times to Adobe. Im sure I wasnt the only one to have an issue with it, even though the Adobe folk wanted me to think that was the case. They also wanted folk to think it was there machine, not their Adobes program.
What was worse is that Adobe had folk take their time to report the problem in detail thinking it would be fixed, and Adobe all the while had intention of doing so. Kind of like now?
Did Adobe fix CS re-activation issues? Of course not. Why should they? They could depend on the majority of CS users who didnt have a problem with it to purchase the newer version to keep the $$$ coming in. Who cared if they lost a certain percentage of customers as long as they kept the majority of them?
Now there have been numerous reports of Bridge problems and performance problems with CS2. Seems like Adobe is employing their new policy again. First, suggest its the customers machine. Next, ask for help from the customer to fix the problem with no intention of really doing so. Finally accept the fact that Adobe only needs the majority of the customers to remain loyal to stay in business.
If the product has issues, it should be corrected by the manufacturer, FOC, rather than blame the user, his equipment, his other programs, ignoring the problem, and finally pretending to fix the problem.
If you continue to purchase Adobe products, fine. Its your choice. You know how Adobe has treated its customer lately. And if you feel that purchasing upgrades to fix performance/program related problems is ok, especially knowing you are in reality trade the old problems for new, then fine. I for one dont think its ok at all.
But then again, to Adobe, Im one of the minority, so I dont matter to them. I have to wonder though. If Adobe alienates just 2% of customer base with each new version, wont that mean that eventually the majority is still a small number of people?
I dont own CS2 because I felt more than ignored by Adobe with the CS re-activation issue. I reported the problem several times to Adobe. Im sure I wasnt the only one to have an issue with it, even though the Adobe folk wanted me to think that was the case. They also wanted folk to think it was there machine, not their Adobes program.
What was worse is that Adobe had folk take their time to report the problem in detail thinking it would be fixed, and Adobe all the while had intention of doing so. Kind of like now?
Did Adobe fix CS re-activation issues? Of course not. Why should they? They could depend on the majority of CS users who didnt have a problem with it to purchase the newer version to keep the $$$ coming in. Who cared if they lost a certain percentage of customers as long as they kept the majority of them?
Now there have been numerous reports of Bridge problems and performance problems with CS2. Seems like Adobe is employing their new policy again. First, suggest its the customers machine. Next, ask for help from the customer to fix the problem with no intention of really doing so. Finally accept the fact that Adobe only needs the majority of the customers to remain loyal to stay in business.
If the product has issues, it should be corrected by the manufacturer, FOC, rather than blame the user, his equipment, his other programs, ignoring the problem, and finally pretending to fix the problem.
If you continue to purchase Adobe products, fine. Its your choice. You know how Adobe has treated its customer lately. And if you feel that purchasing upgrades to fix performance/program related problems is ok, especially knowing you are in reality trade the old problems for new, then fine. I for one dont think its ok at all.
But then again, to Adobe, Im one of the minority, so I dont matter to them. I have to wonder though. If Adobe alienates just 2% of customer base with each new version, wont that mean that eventually the majority is still a small number of people?
Unfortunately, no real competition, Thomas. Especially for Windows machines. Doesn’t look like Aperture will be either.
Chris is essentially right. It’s their software on your machine. Validating a package on all possible configurations of hardware and OS combinations is daunting, especially when you consider that a tiny hiccup anywhere in the system can cause havoc in one program but not another. Yet, with the memory test from Microsoft, I found that one of my 512 sticks failed the checkerboard test, but I cannot see any performance degradation because of it. Running on one 512 stick gave identical performance other than time to invoke scratch on a large file. So, go figure!
Anyway, a systematic approach with validation techniques can be accomplished but it takes time and money. Maybe they just don’t want to do it, and I do not want to chance losing efficiency any more than I already do.
Chris is essentially right. It’s their software on your machine. Validating a package on all possible configurations of hardware and OS combinations is daunting, especially when you consider that a tiny hiccup anywhere in the system can cause havoc in one program but not another. Yet, with the memory test from Microsoft, I found that one of my 512 sticks failed the checkerboard test, but I cannot see any performance degradation because of it. Running on one 512 stick gave identical performance other than time to invoke scratch on a large file. So, go figure!
Anyway, a systematic approach with validation techniques can be accomplished but it takes time and money. Maybe they just don’t want to do it, and I do not want to chance losing efficiency any more than I already do.
Don’t get me wrong. Overall, I’m satisfied with CS2. But the claim that Adobe doesn’t ship software until it’s ready is laughable.
Hey Chris!!! I upgraded to CS2 and just like CS it’s purring along!!!
(Just thought you might like to hear that ;o)
(Just thought you might like to hear that ;o)
I am new to the Adobe users forum – I was prompted to come check it out because of my decreased performance with CS2. we (my company) bought it recently hoping to take advantage of the increased memory allocation and 64 bit OS compatibility for a large project we are undertaking.
I am a cartographer that uses photoshop for map production. we work with layered TIF files that, at 1200 DPI and grayscale color mode, are 400-800 MB using RLE compression. I have thoroughly checked my preferences between CS1 and CS2, the only difference being that CS2 has more RAM available from the 8GB on my Mac 2 x 2.5. I have also taken advice from this website as far as optimizing performance (export clipboard OFF, font preview OFF, save image preview OFF, thumbnails in layers pallette OFF, etc).
using a 486 MB file (and a stopwatch) produced the following:
open file:
CS1 – 2:34
CS2 – 3:05
downsample file from 1200 to 600 DPI:
CS1 – 1:23
CS2 – 2:50
convert color mode from grayscale to RGB:
CS1 – 1:23
CS2 – 2:45
I worked with it a little last week to see if the more minor funtions are slower and they definetly are – rendering type, merging down, erasing hole when moving, etc.
we were all set to buy four more seats for my colleagues, but based on my testing we are going to stick with CS1.
just my .02, not trying to p*ss anyone off.
regards and thanks for the valuable info, I thought I was going crazy!
I am a cartographer that uses photoshop for map production. we work with layered TIF files that, at 1200 DPI and grayscale color mode, are 400-800 MB using RLE compression. I have thoroughly checked my preferences between CS1 and CS2, the only difference being that CS2 has more RAM available from the 8GB on my Mac 2 x 2.5. I have also taken advice from this website as far as optimizing performance (export clipboard OFF, font preview OFF, save image preview OFF, thumbnails in layers pallette OFF, etc).
using a 486 MB file (and a stopwatch) produced the following:
open file:
CS1 – 2:34
CS2 – 3:05
downsample file from 1200 to 600 DPI:
CS1 – 1:23
CS2 – 2:50
convert color mode from grayscale to RGB:
CS1 – 1:23
CS2 – 2:45
I worked with it a little last week to see if the more minor funtions are slower and they definetly are – rendering type, merging down, erasing hole when moving, etc.
we were all set to buy four more seats for my colleagues, but based on my testing we are going to stick with CS1.
just my .02, not trying to p*ss anyone off.
regards and thanks for the valuable info, I thought I was going crazy!
I really don’t think you are p*ssing anyone off
My guess is that major things have happened and will continue to happen.
My observation is based on the impression that Photoshop is not merely a product to many people, it is also a passion.
Somehow it would not surprise me if CS3 will undergo a different marketing strategy altogether (I hope I am not proved wrong)
My guess is that major things have happened and will continue to happen.
My observation is based on the impression that Photoshop is not merely a product to many people, it is also a passion.
Somehow it would not surprise me if CS3 will undergo a different marketing strategy altogether (I hope I am not proved wrong)
Kevin,
CS2 in not cleared for XP64. However, I do share you’re observations about it’s performance and you’re decision not to purchase any other seats.
CS2 in not cleared for XP64. However, I do share you’re observations about it’s performance and you’re decision not to purchase any other seats.
the CS2 I tested was for Mac, it was tested on a 2 x 2.5 GB G5, 8GB of RAM with OS 10.3.9
In that case, you might want to jump over to the Photoshop Mac Forum
oops, thought that is where I was. sounds like PCs have some of the same issues as the Macs.
thanks, I’m off to Mac Land <boooo!>
thanks, I’m off to Mac Land <boooo!>
How to Improve Photoshop Performance
Learn how to optimize Photoshop for maximum speed, troubleshoot common issues, and keep your projects organized so that you can work faster than ever before!
Related Discussion Topics
Nice and short text about related topics in discussion sections
-
How do I optimize PS preferences/performance?
By jakesnake66 on Nov 30, 2004Views436Replies7 -
Maintaining top performance for Windows XP Pro
By knielsen on Aug 8, 2003Views413Replies10 -
Can you perform multiple actions in a droplet?
By Paul_Zahradka on Aug 25, 2004Views988Replies3 -
"Please read the existing threads on Win2K performance problems"
By Brian on Nov 19, 2003Views437Replies6 -
ImageReady optimized seems to revert to previous image
By John Wiens on Mar 30, 2007Views699Replies0 -
Photoshop CS performance
By Paul_Marrison on Feb 24, 2004Views240Replies8 -
CS3 Save for Web & Devices (Save Optimized as)
By Derrick_Conway on Nov 1, 2007Views251Replies2 -
Improving performance in PS 7 ?
By The One on Aug 4, 2005Views176Replies4 -
Photoshop performance on Dual Core Processors
By KSSumra on Apr 24, 2005Views371Replies5 -
optimizing: PS adding "copy" to file name…
By maya on Mar 15, 2009Views629Replies8 -
Vista – Wacom tablet, Line Tool, Pen Tool has terrible performance
By James_Cho on Jul 30, 2007Views224Replies7 -
How do I save .gif’s optimized pics with color?
By Lynn Johnton on Jul 17, 2003Views275Replies2 -
Maximizing CS Performance
By Leonard_Leffand on Oct 27, 2005Views323Replies6 -
Optimize QuickSilver G4 for large files in PS 7
By Chuck_Hemard on Feb 17, 2004Views193Replies4 -
Not enough memory to perform…Error
By Tan_H on Jun 30, 2008Views157Replies1