PS Error Saving JPEG

  • 1
  • Problem
  • Updated 1 year ago
  • (Edited)
This is becoming a serious issue for me and I'm wondering if anyone else has seen this. I am processing a full sized PSD file, no layers, then doing a "Save As..." I save it to another outside folder as a JPEG, IQ 12. The original file is always over 4000 px on the long side and I'm not resizing it in the output. I follow that procedure in every instance. When I look in the folder where the files are being saved, some are fine but a significant number show a size of 160 x 106 px or 106 x 160 px if a vertical format. All the sizes in the damaged files are the same - 160 on the long side. In one folder of 17 images, fully 4 of them came out with this sizing. Again, I am not varying my process whatsoever with these images - they are all saved using the same routine (I'm not using Actions for this). When I double-click on the image in Bridge to see if it's a problem with the preview, Photoshop opens with the following message:



I'm trying to meet a deadline here and it looks like I'm going to have quite a few images to reprocess. Anyone have any ideas on this please? System Info:

iMac 27 5K Retina, 32GB RAM, over 2 TB free HD space
Mac Mojave OS, latest update
Photoshop CC 2019 V20.0.4 (this has been happening for at least a year now though)
Files are PSD converted from NEF's using either LR or Camera Raw

Thanks for any help.

Glenn
Photo of Glenn Davy

Glenn Davy

  • 93 Posts
  • 22 Reply Likes

Posted 1 year ago

  • 1
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1315 Posts
  • 277 Reply Likes
Photo of Glenn Davy

Glenn Davy

  • 93 Posts
  • 22 Reply Likes
Umm, what is "WhatsApp?

Glenn

Edit:  I just looked WhatsApp up on the web. Not sure how this applies in any way to my situation. Could you please clarify?
(Edited)
Photo of eartho

eartho, Champion

  • 1486 Posts
  • 500 Reply Likes
I've saved a few 10,000 jpgs over the past year and not once encountered this issue... and this isn't a fix, but maybe try using Save for Web or you can also automate the entire process using the Tools>Photoshop>Image Processor found in Bridge.
Photo of Glenn Davy

Glenn Davy

  • 93 Posts
  • 22 Reply Likes
Yeah, this is definitely "different". I can't even find anything on this after Googling it, so I suspect there's something I'm doing unawares that's causing this. I suspect saving for the web is probably the best way to go, but I do need to be able to "attach" the AdobeRGB profile to it. These images are going out to a magazine for printing. What's baffling is why it works 3/4's of the time, and why it always defaults to 160x106 px. That's confusing to me.

Thanks for the tip - I need to look into that one. Appreciate your time.

Glenn
Photo of Glenn Davy

Glenn Davy

  • 93 Posts
  • 22 Reply Likes
I may have found one clue. In looking at other issues where saving a file as a jpeg using Save As were a problem, one suggestion was the psd file may have been 16 bit. Mine are all that, so I'm wondering if maybe that is a possible reason? I have been trying to reproduce this problem but it's extremely hit and miss and I can't find anything common between the files that are corrupted. I'll continue on with my testing and report back if I find anything conclusive in case anyone else ever runs into this, but it looks like I'm an isolated case and that certainly leads me to believe it's not a bug but something I'm doing unawares.

Glenn
Photo of David Converse

David Converse

  • 940 Posts
  • 275 Reply Likes
A 16 bit PSD cannot be directly saved as a JPEG, since a JPEG is limited to 8 bits per channel for color. So, yes, that would be an answer.
Photo of Glenn Davy

Glenn Davy

  • 93 Posts
  • 22 Reply Likes
OK, that makes sense to me then. I guess the ones that did work were a bit of a fluke. I just figured that PS was automatically "de-bitting" (how's that for making up words! (LOL)) it as it saved it, and likely that is what was happening in the versions that came out ok, but for the ones that didn't, the "de-bitting" happened at a different point in the saving process which corrupted the output. Anyway, thanks for the input - it helped quite a bit. 

Glenn