Unable to save over jpg or tiff without making a "copy"

Community Expert

We guys did not do anything. We are Photoshop users not Adobe employees.

Dave

Community Expert

Fact- Any application developer has to work with the APIs of the operating system.

Fact - If those APIs change then significantly then the developer has to change their application.

Dave

Community Expert

So Apple made a Change that Apple user don't want you want Adobe to change Photoshop on Windows so Windows user will also not want the Apple change. Apple created a problem. Adobe should have address the Apple Mac problems not proliferate the problem to windows. Did Microsoft change Windows APIs. Adobe change Photoshop operation on both PC and Mac its not about Windows APIs. Dave you know its an Apple problem that Adobe is spreading. The only Adobe applicatiom is Photoshop. Has Adobe spread Apple problem to all of Adobe applications?

JJMack

Inspiring

This is still a huge problem for me!

Community Expert

IMO it is a problem for all users not huge just just an other Adobe Photoshop issue users need to deal with. Still I feel it would be better if Adobe back out this update. Forced version and saturating user storage with version they will never used. Also force addition storage maintenance and file renaming work. Work users have not asked for work they do not want. They want to be able to update/replace their existing image files. Apple and Adobe are now making that processing complex users need to work the versioning forces on them. I'm in better shape then most users. With a little scripting I can update current files versions will not be created mo extra work needed. Most Photoshop users know little to nothing about Photoshop scripting. They have to use Photoshop UI the forces versions.

JJMack

https://petapixel.com/2021/05/18/photoshops-save-as-function-has-changed-on-mac-heres-why/

Community Expert

Adobe cannot back out of the update. Have a read of this. The old APIs have gone.

If Adobe removed some of the functions you use in scripting and refused to put them back in, then your scripts would have to change. That is the same position Adobe were in with Apple, they had to change.

Dave

Inspiring

REALLY? You had to change this? And again, totally messes up my process. Why was this changed on the PC if APPLE was the issue? If it ain't broke, why did you brake it?

TheDigitalDog

Inspiring

@J2kLarsonite wrote:

REALLY? You had to change this? And again, totally messes up my process. Why was this changed on the PC if APPLE was the issue? If it ain't broke, why did you brake it?

You who?

This is a user to user support forum. To provide feedback and suggestions about what you desire from Adobe, you should go here and comment after selecting the appropriate product:
https://feedback.photoshop.com/categories/products/5f5f2090785c1f1e6cc40864

The reason it is on the PC is for platform parity. And it will remain as such.

And no one forces you to update your copy of Photoshop. If you really must work the 'old' way, stick with an old version.

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"

Inspiring

Adobe forces me to update or I run the risk of never getting any of their wonderful new features in the future. Hence the value of a subscription!

And are you really confused "who" I was referencing? Maybe YOU can post my replies in the forum after YOU select the appropriate product.

So your point is that PCs and MACs should equally suck? And what parity are you talking about? Command and Control are in different places on the keyboard and destroy any commonality with Hot Keys. Didn't think that platform parity comment through did you. PCs and MACs also operate differently within their folders when saving. PC has the advantage because I can create and edit folders. MACs can't. Parity my horse's hat!

Adobe dropped the ball and is getting dragged around by Apple's dog leash. I've been using Adobe since before it was available on Apple computers. Now Adobe is Apple's son. What's next? Apple makes a better design suite than Adobe but doesn't offer it to PC users? Yep! See, even I can predict Apple's longterm take over of everything. But Adobe can't see that?

And you're offended I'm in the wrong forum? LOL

Community Expert

It a Mac issue Adobe is trying to force onto Windows users. On Windows you can do it like we did it years ago with an interactive action where you set the location you want to save jpeg file in the interactive Save As step. Before the step the action flatten and after the save as the action steps back an recovers the layers. There is no good reason to Add " copy" to the file name that is a Mac thing....

JJMack

D Fosse

Community Expert

You know better than this, JJ. Should there be Mac-specific and Windows-specific actions? Should every tutorial out there be duplicated, one for Mac and one for Windows? Do you think that would go down well?

Again, the change was forced by Apple removing the API that allowed stripping "-copy" from the file name. I get that most people will blame Adobe for this, but let's not make it any worse.

Inspiring

I'm not sure how many times I'm going to post this... but Adobe's inablity to keep up with Mac's opperating system and changing the Save As feature is pathetic! I'm goint to post this everytime I'm fed up with this change. So stupid! Adobe just lost so much credibility.

Inspiring

THIS SUCKS!!! And for a reason Adobe has not considered! When I save my files, I navigate to the folder I want to save. Since I've been saving files for 20 years the same way until now... I am constantly having to click the "save a copy" in the save as dialog box. This takes me out of the folder I am trying to save my file and into the last folder I saved a file. Since I'm using photoshop at work and I process about a hundred files in a day, this has slowed my workflow incredibly. Why change something that was never broken?!

...and if anyone thinks that a simple change of hot keys is going to solve this problem, well, you haven't been doing this as long as I have!!!

D Fosse

Community Expert

This was changed because the Save As jpeg function had already been broken for over a year on the Mac side, since Catalina. Saving over a jpeg resulted in a separate file with "-copy" appended. Apple did not want to change this, and there was no way for Adobe to work around it. The Save As jpeg function was terminally broken and finished, and had to be totally rewritten.

To be clear, saving a layered/16 bit file as jpeg saved out a copy the whole time. That is important to understand! The jpeg format does not allow 16 bit or layers. That fact was just hidden by Photoshop, but with Catalina it was no longer possible to hide.

Everybody should keep in mind that the direct save to jpeg, from 16 bit/layered files, was introduced in Photoshop CS5 in 2010. Prior to that, it was not possible at all to save directly to jpeg. First you had to remove every property in the file that wasn't supported in the jpeg specification. Only then could you save it. So this is nothing new - but this time you can use Save A Copy.

Platform parity has always been a sacred principle in Photoshop, so it had to be changed in the Windows version as well, even though it never was a problem on Windows.

Inspiring

Sounds like Adobe got their hat handed to them. How does a company that works cross platforms for nearly 30 years mess this up? did they not see it coming? Do they not have the tech people to adjust? What's next?

Anyone who has used Adobe for their career knows what a joke this FORCED change is.

and lastly... WHY CHANGE THIS ON PC's IF THIS IS A MAC ISSUE??????????

[20 lines of extraneous punctuation removed by moderator]

W

walts5189928

Participating Frequently

After doing the latest update on Photoshop CC, I am now having similar, if not the same issue as lizuare regarding the simple task of creating a jpeg file from a single raw file in photoshop. Instead, of getting the standard JPEG option I am getting only Photoshop (PSD), Large Document Format, Cineon, IFF Format, JPEG 2000, PNG, Portable Bit Map and TIFF file options. For me to save the rendered image to a JPEG, I must refer to the "Save a Copy", which leaves the file name with -copy.jpeg attached to the end of it. I have been using Mac's since 2006, and Adobe photoshop even longer than that, so what davescm says is total BS!

Abobe, FIX THE PROBLEM!!!!!

Community Expert

@walts5189928 Thank you for you complementary remark - please keep this forum civil.

You are missing the jpeg option because the document you have opened from Raw cannot be saved directly in jpeg. Chances are you have opened it from Raw in 16 bits/channel which is supported in the formats you listed above but not in jpeg.

Are you ready to apologise? 🙂

Dave

Community Expert

O.K. Let me lay this out. I have for the past two years been working from a 27-inch

3.6 GHz Intel Core i9 iMac with 128 GB 2667 MHz DDR4 memory for rendering raw files form my Nikon D850 which are 89 MB (6880 x 4584) in size into 6880 x 4584 8-bit size jpegs. Before the latest update (5/17/21) I was able save the image being rendered into a JPEG file by selecting that option in the drop down. Yes, I am aware that JPEG file rendered is downsized from 16 bit to a 8 bit in the process (automatically). Seeing that option removed and replaced with Save a Copy to get the same results but with -copy.jpg attached to the file name is doing nothing by creating an unwanted addition step, which to me is stupid.

(

"I have for the past two years been working from a 27-inch 3.6 GHz Intel Core i9 iMac"

Then you will also be familiar with the copy problems since Catalina.

If you don't want "copy" added you could Export the file as a jpeg

Dave

Community Expert

That has been change in 22.4 Saves As will no longer save a flat jpeg from a layered document. You must be on a Mac and an older version of Photoshop. Windows has no problem over written the was some issue on mac wrote a new File with copy appended to the file name. Now Adobe is forcing copy to all....

You could Programs a script that basically works like Photoshop 'Savs As" worked in the past. The script would have a different UI than good old "Save AS"a Photoshop which used a system dialog. The script would have a ScripUI interface quite like Adobe Script "Export Layers to Files. Save the Document in the image file format you want to save. In fact I use code from Adobe 'Export Layer to Files' creating the script for my personal use.

Change the title in the dialog to Save As and process the document. It will be a Plug-in Script.

Still on a Mac I do not know for sure the Scripted Save As will over write files on a Mac. Mac has a unix type file system.

JJMack

L

lizuareAuthor

Known Participant

Just updated! Working! Although I will say the new "Save a copy" is a bizare additonal step... seeing Daves note above nice to have a real explanation! Thank you