After your rant, you may care to read this recent post from Conrad Chavez, author of "Adobe Photoshop Classroom in a Book (2022 release)":
Except it WAS broken
Correct. In addition to legitimately fixing old broken code, many of the other recent changes have had to do with bringing Photoshop up to date. For Save As, it could be argued that the old way was wrong, because many applications do not offer non-native formats in Save As; they put all those formats (JPEG, etc.) in an Export or Save a Copy command…which is exactly how Photoshop works now.
Another “legacy” issue is proportional scaling without the Shift key. Again, using Shift for proportional scaling is no longer the standard in newer applications, especially for consistency with mobile versions where there is no Shift key. The new Photoshop default is consistent with other current applications. (The main mistake Adobe made there was to not also make the change in other applications like InDesign and Illustrator.)
It’s true that old habits are burned into our muscle memory, so it’s a pain when they are changed. But just because something was done a certain way 25 years ago often doesn't mean it’s still the best way today. Things change fast in tech, so it helps to be adaptable.
For whatever reason, Adobe is struggling to communicate the what and why of all the changes to its userbase. This isn't a new thing in business.
@Derek Cross wrote on 04 November 2021:
... you may care to read this recent post from Conrad Chavez, author of "Adobe Photoshop Classroom in a Book (2022 release)":
Do you have a preview copy Derek? The 2022 edition will be released on 27 December.
The best change was to add later legacy option to let everyone work like they prefer 😉
This explains why someone THOUGHT they should change it, so that things could be placed in boxes in a way that the coders preferred. But is also sums up why users are angry. Software should not be written to satisfy the coders desires. It should be written to make the end users daily lives as effortless as possible. If you compare the total number of times the code needs to be rewritten in the entire history of the software, compared to the total number of times that end users save jpg files, then the needs and desires of the users should completely override the wants of the coders. If the coders actually had to use the software every day, they would have NEVER set up the default settings the way they did.
If you wanted to apply the "correct" logic to the organization of what goes where, then the most-frequently-used file formats should go into the Save category and everything else should go into a second category, simply to keep the first list as easy to use as possible. And giving us an option to revert to legacy Save settings only proves that the coders could have chosen to leave things as they were in the first place.
Adobe needs to stop creating software that requires users to go in and change dozens of preferences every time there is a new version. Stop screwing over the end users. Make our lives easier, not harder.
Unfortunately, this was a necessary evil to counter what the operating system makers did to their latest releases. It was this way or no way. And this way (although not perfect) is still better than no way. 😉
Nancy is right.
The reason it is the way it is now, is that with the OS changes, there's a real risk of unintentionally overwiting data. That's why it's now a preference and not the default.
No one at Adobe is “screwing” the user and it helps to stay on topic and accept change when you update your software which NO ONE forces upon you.
Some Adobe customers hates two things: Change and the way things are.
Time out, carol. I think if you look at this calmly, you'll see that there's no conspiracy here. There's nothing to gain for Adobe by needlessly alienating paying customers. Of course they don't want that, it's bad for business.
The fact is that Adobe had to do something, because MacOS no longer allowed the old saving protocol. So first they did it one way, which caused so much uproar that they had to work overtime to come up with another workaround. So they did, and that's what we have now.
Note: This change didn't initiate with Adobe. It came from Apple, as a security policy, and chances are Microsoft will go the same way (if they haven't already).
Re carolp44698866's posts, there seems to be a touch of the bonkers here!
Derek Cross, referring to people's comments as being "rants" or "bonkers" is a form of trolling that is not helpful. I also can't help but wonder how much of it is just sexism.
Thank you for your further comments on this matter.
Perhaps someone could do us all a favor and lock this thread? It seems unlikely anything more useful will come out of it.
Actual arguments and facts are just ignored anyway.
Actually, in the old days, before the subscripton model, Adobe was pretty great about fixing problems and testing software before releasing it into the world. They had to because we wouldn't pay for the upgrades until we heard that the product was stable. Things have gotten much worse since the subscription model came out. These day, we have no choice but to install upgrades almost immediately either because the previous version was so buggy we're desperate for fixes, or the software simply starts to crash and act up because we have not installed the update yet. And I don't have a choice. Even if there were an alternate software, my industry would force me to use the same software that everyone else is using.
But you are all still missing the point. What I am saying is the coders should have known that changing saving jpgs the way they did was going to cause major problems for end users and the preference work around that they eventually came up with should have been the initial solution.
Yes, I know, many times you can just use scripts to automate processes as was recommended to the initial poster. That is nothing new. But I've also found myself in the same situation as the initial poster, where individual photos needed custom solutions in order to keep file sizes low while maximizing image quality. Not all processes can be automated and my heart goes out to everyone whose work life was made into a living nightmare by JPGgate.
This is messing with my workflow, and I don't know if there's a way to switch settings to fix my problem. I'll lay out what I'm doing, because I don't know how else to explain it.
1. I open a jpg.
2. I edit the file in some way.
3. I press save.
4. I am taken to the dialog box that saves a PSD file. However, I just want to save the file with my edits, not create a PSD document.
5. Instead of using "Save" I choose "Save A Copy", because this is the ONLY way I have found to save a jpg.
6. I still have to erase the word "copy" after the filename, which doesn't help when doing batches.
The reason this messes with my work flow is because when you create an action that saves as a copy, it doesn't erase the word "copy" from the filename. It just creates a new copy with the word -copy at the end.
This all changed in the May update. I am frustrated by this update and really wish you would not have changed the save's normal functions.
ANYWAY, how do I fix this in photoshop so that I can do my batches quickly. This new method just doesn't work for what I need to do.
If you flatten the document File Save will write over your jpeg file. If you enable legacy save as when File Save switches to Save AS to give you the opportunities to save layered file format you can choose jpeg instead if Legacy Save As is enabled and save a flat version of your layered document over your existing jpeg file after you confirm that is what you want to do,
Thanks for the tip! I am going to try this out.
Thank you - several people who listed the solution to go into preferences, file handling and check the box enable legacy save as....
As for those of you stating you want to roll back... I have several version of PS on my main computer as I have plug ins that do not work as well with the newer versions... when I want to use them, I just open that PS version, open the PSD I am working on and then use my plug ins. It's all good.
yeah that a [inappropriate language removed] update from adobe. save a copy so every time if you wanna save in jpg "ctrl + alt + s" on windows. and they though good to add "copy " in the file name that you will have to manually remove (such annoying feature and so usless + such lot of time lose)
Hello, I think there is a bug with the "legacy" implementation. I have the latest Photoshop and the lastest Windows OS. I have "Enable Legacy Save As", "Do not append "Copy" to file name" and the "Save As to Original Folder" options selected.
Issue is that the Save As does NOT save to the original folder, I have to manually specify it when I use the Lightroom, Edit in, Edit in Photoshop 2022 option. I think it may be saving to a previous folder, not the one where the original file (usually the .NEF in my case) when I access Photoshop from Lightroom. I am pretty sure this used to work, that I did not have to manually specify the original folder (the one in Lightroom, containing the raw files). Right now, this is impacting my workflow, as I have to take the time to specify the intended file location in Photoshop.
File formats that don't support all the current properties of the file have now been moved to Save A Copy (because that's what it is). The original full file will still be open for editing after Save A Copy.
You can revert to the old Save As behavior in Preferences > File Handling.
I'm currently having the same issue. Except "Save a Copy" does not have an option for PNG either
You are not able to save your file as a PNG in Photoshop because your document is in CMYK color mode or is set to 32-bit channel. You can confirm this by going to Image>Mode… PNG files can only be saved in RGB and only support 8-bit and 16-bit channels.
To save it as a png, go to File>Export>Export As… In the export dialog box, choose PNG under “format” then click Export All. Photoshop will automatically convert the image to RGB and save it as a PNG without affecting the file on your canvas.