Photoshop: jpg exposes bugs in QImage and ZoomBrowser

What OS are you on?

Providing the same files would be an enormous help!

No changes, the JPEG and thumbnail code hasn't changed in the dot releases.

If Canon has specific issues, they need to contact us directly with details.

There are definitely issues with file saving in 12.0.4. If you use the image processor to process raw photos into JPEG's, many times the saved JPEG's contain three embedded ICC profiles: sRGB is embedded twice and Adobe RGB is embedded once. Definitely needs to be fixed.

Impossible, yet there it is. On multiple installations, different machines. This is actually one of my customers/users. I wasn't able to replicate her problem at first but I discovered it was because I was running an old 12.0 x64 CS5. As soon as I upgraded to 12.0.4 x64, the problem appeared exactly as she was getting it. She says she's contacted you (before I did here) and she's also sent you an XVI32 dump that proves the problem, so since the images are not mine, I'd prefer that she send them to you. I'll let her know and will ask her to contact you. I was able to replicate the problem easily once she sent me a couple NEF's and gave me her settings in image processor. Thanks for the help.

I'm going to prepare a ZIP for you and send it to you. I'm waiting for permission to send you the photos since they are not mine. Here's what I found. If I put two NEF's in a folder and use image processor, it works fine. If there is an sRGB JPEG in between such that image processor processes one NEF, then the sRGB JPEG, then the next NEF, the last NEF is corrupted with the three embedded profiles. That's why I say I believe it's a variable initialization issue since it looks like the sRGB is being carried over from the JPEG being processed between the two NEF's. If you image process 1775.NEF, 1960.NEF, and then 1999.JPG (the sRGB JPEG), all is fine because the sRGB JPEG is last. As soon as you rename the JPEG to 1780.JPG so that the image processor processes the JPEG as the second image in the batch, the last NEF (1960) gets corrupted. Anyway, I'll send you the ZIP tomorrow. That should be all you need to replicate the problem because it happens every time.

The person with the XVI32 dump just showed different images with different profiles - almost certainly user error.

If one file has multiple profiles in it, then I need to get the files to examine.

You're making a lot of bad assumptions about what is going on (and what's even possible to occur).

There aren't any assumptions being made. Only observations. When I send you the three files, you'll be able to reproduce the problem. Put the two NEF's in a folder and run the image processor to convert to quality 12 JPEG's and the two converted JPEG's are fine. Put one sRGB JPEG into the folder with the two NEF's and now the NEF that is converted after the JPEG goes sour: two sRGB profiles embedded plus one Adobe RGB. That's the same NEF having a completely different result from the image processor: correctly when the JPEG isn't present in the same folder and incorrectly when the JPEG is present. Only way I can fathom that happening is a bug in CS5. Don't see how user error could cause the same NEF to convert two different ways with the exact same conversion setting, only depending on whether or not there is a JPEG converted before it or not.

OK. No response from my customer yet on getting permission for her photos (too late I guess) so I tried two of my own photos. They had the same problem: untouched raws from a Canon 5D. Doesn't look like it depends on the camera model so I just sent a ZIP file to you via yousendit. It contains all you should need (files and instructions) to recreate the problem where CS5 creates JPEG files with three embedded profiles on the conversion. Please let me know if I can be of further assistance.

Mike,
I agree it is very variable - some pictures are fine and some are not and I cannot see a pattern. But it does occur on my 7D and G11

If you have a "bad image" and are able to look at the hex you might want to try this:

open the file and then invert the image twice, I just use Ctrl I, so you get what looks like the same image back, then save it.

You will now find this is a "good image", this is what I've been using as a workaround. But if you can look at the hex you may be able to see what got fixed in the image.

Andrew, I think by doing that invert-invert, you are just forcing it to re-form the file header, overwriting the corrupted one. I think Chris will be able to reproduce/fix it now. Still looks to me like something getting cross-linked during the conversion: some "stale" piece of the header from a previously converted JPEG gets left over in the raw photo when that gets converted afterward.

I would LOVE to send you files to look at. If you like, I can shoot some that never even go through my photoshop and let you convert them yourself. I can send you converted files, I can send you files that are right and files that are wrong. Just tell how many you want and where and how to send them.
I would also like to know if there is a way to check a log noting when the newest update occured, because I know the exact date the problem came into being in my workflow. I am not blindly pointing fingers or assuming any thing, just trying to get down to the problem, that obviously I am not the only one having.

I'm going to chime in with something I ran into with with 12.0.4 x64 yesterday.

I finished working on a re-sized JPEG saved in 'Adobe 1998' to send via my Excite.com account through AT&T/Yahoo! DSL and the server sent back an error message: "File is corrupt, or larger than 25MB limit. Try again?" That was new. I tried over and over and got the same message in about 10 seconds from their server. I've never seen a "Corrupt file" message from a server on a JPG before.

I redid the same JPG file and saved it with Paint Shop Pro X3 (same 'Adobe 1998' colorspace) and it went through without a glitch. File size report by Windows Explorer was 328 KB in CS5 and 325 KB in PSP X3.

From CS5 12.0.4 x64:
Format : JPEG
File size : 329 KiB
Image Format : JPEG
Width : 656 pixels
Height : 900 pixels
Chroma subsampling : 4:4:4
Bit depth : 8 bits
Compression mode : Lossy

From PSP X3:
Format : JPEG
File size : 324 KiB
Image Format : JPEG
Width : 656 pixels
Height : 900 pixels
Chroma subsampling : 4:4:4
Bit depth : 8 bits
Compression mode : Lossy

I was wondering if anyone at Adobe Family has opened any of the files I sent? If not, please get with me so I can send you files and you can help determine the problem and solution.
Also, still wondering if there is a way to revert back to an update before 12.0.4 or to see when that update actually took affect?

Based on a search, looks like 12.0.4 was released May 3, 2011. When you actually got it on your particular computer... that could be a different story.