Since many of the plugs we use are not 64-bit (and it's possible some may never be) please give us a better way to invoke the 32-bit version when needed. Currently, the only way I know how to do that is to use Get Info, and set the finder switch to 32-bit. This is problematic. Try this: before setting the switch put an alias on dock, then set the 32-bit switch and create another alias for the dock. Now there is two icons to invoke the flavor needed, only when I click on the 32-bit one, I get a message "The Application has been moved....Update...Yes or No?" If you say yes, the alias reverts to 64-bit, and if you say yes, PS opens in 32 bit. That means I have to go through that dialogue each time for 32-bit! Arg...come on guys, you can do better, as you put us into this situation (ie. not allowing plug vendors the needed upteen months to retrofit old code). Thanks!
That is the only way to switch. That is the mechanism provided by Apple.
The only other option would have been to install 2 separate copies of Photoshop: one 32 bit and one 64 bit.
(ie. not allowing plug vendors the needed upteen months to retrofit old code).
And that is untrue. The major plugin vendors (and more than a few smaller ones) have been part of the Photoshop CS5 beta program for many months.
well, i don't want to fight with an adobe employee, as you already have enough of a battle with Apple going on, but I gotta say, this fix rots. u guys should figure out a way to make plugs compatible. I can't believe the amount of cash spent on plug-in upgrades since CS first came on the scene. And here, just a bit over a year later, the plug vendors are charging for another upgrade for CS4 to CS5 plugs, and making us wait for them too. But I guess users are just collateral damage...and money bags.
It sounds to me like you are person who is professional and if you think about it you might have come up with this situation yourself.
I can speak from my own expereince.
I f you have your own clients or work with a firm that has numerous clients you find that some are more prepared to move on than others.
There was time when digital photography was not really ready for prime time but all the clients were excited about this technology and wanted digital no matter what the cost.
Then they found that it was not quite as easy as they thought. Then they found they had to acquire knowledge and skills themselves.
Then it was difficult to explain that we had to use tiffs and not jpegs as the agencies demanded tiff files then it became apparent to some agencies that if they went modern it meant ftp for file transfer and that meant it was not practical to send 20 or 30 or more 100MB tiff files, actually the agencies limited it to 80 MB files. So jpeg became their only option so over night it went to nevr send jpeg to you must send jpeg only we will not accept any other format.
To them it turned out to be a blessing if the client is not savvy then they will degrade the jpeg file and have to pay for another download.
Ok so now we are set with the agencies jpeg it is now what do you tell your clients we can only send you jpegs when they have just learnt that jpegs is a lousy compression scheme, now they think you don't care you are just making this easier for yourself, even if you explain that there is a work around to resave the file as a tiff and or .psd.
You see what is happening here the user in this case you an me want certain capabilities and we can't wait, the support developers are not as capable as the main the developer, the resources of the developer is limited by what the stock holder expects and what is possible no matter how much resources you put into it.
If you are a professional you should understand in this case we are the public and the public can be difficult and extremely unfair even at the cost of creating more problems for themselves.
I wanted Illustrator to be 64 bit but not one of their plug in developers are 64 bit or is even prepared to be 64 bit. en if the plug in developer was working side by side with the Photoshop team they could not have a plug in that they could safely market until the final version is ready for the stores because of the possibility of conflicts so their software has to be tested. It would do little good to take the chance of marketing a plug in too soon as if it became a major problem rathr than solid time tested solution that could be the end of the developer.
Hopefully you can add one plug in at a time and make certain they are sill working for you when they become available and be thankful your plugins are developed by people who care about what they do and are not just going to through junk at you.
I for one am thankful Nik software is taking their time to do a good job.
Don't you think a little of this at least sounds correct or am I all wrong?
You need to have a better understanding of the issues here. Apple decided to change course which required a major rewrite to update to Cocoa for Photoshop. When Adobe did that, it changed the way the plug-ins interfaced with Photoshop which then required the plug-in developers to change their code. Now, no developer is really going to know if their plug-in code will completely work until Photoshop ships (until then, interfacing is potentially a moving target). So that explains why, even with betas of Photoshop, plug-ins aren't ready to go.
As far as pricing, OnOne has said that if you own the current version, the updates to work with CS5 will be free:
Nik says the same basic thing:
Now if you chose not to update to the current version in the past, what do you expect the plug-in developers to do? They certainly can't be expected to update code from previous versions to work with CS5 and 64bit. That makes no business sense.
Where Photoshop CS5 for Mac was headed was made public last year so users would know that it would be 64bit and not run on PowerPC computers. That gives the user a heads up that things are going to change in hardware and software going forward. I had to finally invest in an Intel Mac or stay at CS4. My choice was to keep moving forward so I bit the bullet even though my G5 was working fine.
I won't argue that being on a perpetual upgrade merry-go-round is frustrating and expensive at times. Unfortunately, like it or not, that's just the way it is and will be for the foreseeable future.
For users to get attitudes with Chris though, is something that I will argue is extremely counter productive. He his here to help us figure out our problems and when we can give him the required info, fix problems in Photoshop that will make it better for all of us.
Jim, I agree that Chris is helpful and it's nice to have a developer's ear. But as a photoshop user since day 1, and a suite user since day 2, I am just tired of updating plug-ins ad nauseum. I am tired of the entire plug-in strategy and just a tad frustrated to have to go thru this every 12-18 months. Instead of something like puppet warp I would rather see persistent plug-in support. I just don't understand why a plug archeticture can't be developed that supports developed plugs for at least 3 years or more. But I guess complaining about this is like peeing in the wind, so I will stop. I've said my bit. Cheers, and happy creating!
We can't make plugins compatible. Apple's OS does not allow a 64 bit application to load or use 32 bit binaries.
This isn't about money, this is just the limitations of the OSes we run on.
BTW - Windows had the same issue.
I am just tired of updating plug-ins ad nauseum.
Except for technology changes that we can't avoid (68K -> PPC -> OS X -> x86), you shouldn't be forced to upgrade plugins.
Photoshop goes to great lengths to make sure that our plugin APIs remain stable and older plugins will keep working (again, except for unavoidable platform changes). Technically, a plugin written against the Photoshop 1.0 API should run with Photoshop CS5 (but would have to change compilers, target processor, and OS libraries).
Because we put in a lot of work on this, most plugins DO work across versions without changes.
A few plugin vendors do require updates for each version of Photoshop, usually because they do things we explicitly tell them not to do (like trying to hook into Photoshop's UI). And some vendors include copy protection code that breaks with new OS versions. But we can't control those problems.
Europe, Middle East and Africa