CS3 Save As .Jpeg Program Error

When attempting to save an RGB or CMYK file larger than 100M as a jpeg, an error message appears stating "Could not save a copy as Cfile name) because of a program error". Two questions:

1. Will resetting my prefences affect this error? If I try resetting my preferences, will my custom color swatches and patterns be erased?

2. Is there a known solution to this error?

Thanks...

When you say "larger than 100M" what do you mean? Is that megapixels, megabytes of uncompressed image data, or what? What are the pixel dimensions of the image file? Are you aware that saving a CMYK file to JPEG can lead to unpredictable results because some applications assume RGB and aren't coded to deal properly with CMYK files, even though the JPEG spec allows four-color encoding?

Here are the specifics for one particular file, which is comparable to all of the files that I've been struggling with.

Pixel Dims (137.3 M): 8000w x 6000h
Document Size: 26in x 20in
Resolution: 300 pixels/per inch
Resample Image: Bicubic(smooth gradients)

Our proprietary software prefers jpegs for uploading images to our website, thus the reason for converting .psd files specifically to jpeg formatting.

I've tried converting from RGB to CYMK and vice versa(and flattening the images during the conversion) but neither format will save as a jpeg.

Thank you for your help.

I just created an 8000x6000 px image from a large RGB pano file. To Save As JPEG I had to change it to 8 bit per channel mode from 16, but otherwise no issues. I then converted it to CMYK and Saved As JPEG (still in 8 bpc), with no problems. Both files opened properly.

You will need to be in 8 bit per channel mode, and the image will have to be flattened (otherwise you will get save as copy dialog, which will result in it being flattened). The size clearly is not an issue, nor is the CMYK mode image. Have you tried flattening and making sure image is 8 bpc?

The files are in 8bit/channel mode, and even after flattening the layers, I still get the same error message.

When I go to the Save As dialog box, and after typing a file name and clicking "Save", when the Jpeg option dialog box appears it hesitates for a long while before the contents of the dialog box are displayed. I don't know if that's related or not, but it only happens with the same files that won't save as Jpegs.

A discovery: In the Jpegs Options dialog box, when I selected Baseline (standard) instead of Baseline Optimized, the file converts to a jpeg without much hesitation. What's the difference between the baseline and optimized option? Was it just a fluke that changing the format option worked, or is it in relation to the original problem?

I was saving as Baseline. Not sure what the difference is with Baseline Optimized. I never use the other option, Progressive. Glad Baseline worked for you.

I got application errors trying to save an 18000 pixel wide banner image using baseline optimized. Using baseline standard worked (and worked quickly - the error saving baseline optimized took some time to finally pop up).

There is no "baseline" save as option. Apparently baseline optimized produces a somewhat more compact file according to this article:

<http://www.impulseadventure.com/photo/optimized-jpeg.html>

I don't know how large the file has to be for Photoshop to choke on the optimization processing, but it's clear that large image jpeg saves require changing to baseline standard. It's apparently too much to ask Photoshop to be aware of its limitations and either provide a warning beforehand or simply gray out a save as option that won't work.

It's apparently too much to ask Photoshop to be aware of its limitations
and either provide a warning beforehand or simply gray out a save as option
that won't work.




No, not really. The failure here is that PS simply assumes it has always enough RAM/ memory under any conditions and then it runs out because obviously for a 32bit app the ceiling is and will forever be 4GB (if run on a 64bit host OS like XP64). it is also further complicated by the fact that you never know how much more RAM you need until you actually have built the block pyramids for compression. Theoretically you could still have enough juice even with large images if only there pixels are distributed in such a way that they generate an "ideal" block pattern. So there you go. I guess this once more illustrates that such optimization and analysis features should be a native core function rather than plugged on in the loaders/ savers...

Mylenium

It's apparently too much to ask Photoshop to be aware of its limitations
and either provide a warning beforehand or simply gray out a save as option
that won't work.




When PS chokes on compressing an oversized optimized JPG, doesn't it offer a clear message to use baseline standard compression instead?