Skip to main content
Adobe Photoshop Family

14 Messages

 • 

202 Points

Sat, Sep 3, 2011 10:24 AM

Solved

Photoshop: Color problems in QImage

PS CS5 has started embedding double profiles in some of my files. Sometimes it happens just from Image Processing from ACR and sometimes when we save a file after working on it. I have my working rgb color space set to Adobe RGB. Photoshop and Bridge both recognize these files as Adobe RGB, but when I take it to the print software, Qimage recognizes them at srgb. I though it was a Qimage problem, but when the file data was dug into, you can see that it has both srgb and Adobe RGB embedded.
This problem only started July 17 : seems to be random - some sessions only has one out of 100, others have a dozen : is happening on both computers running CS5. Any ideas?

Responses

Official Solution

15.1K Messages

 • 

195.8K Points

9 years ago

The big bug (failing to parse JPEG files correctly) was in QImage, and that was triggered by a minor issue in Photoshop CS5 (sometimes including perfectly valid profiles in the thumbnails). The version of Photoshop is irrelevant, since QImage was not reading JPEG files correctly to start with.

15.1K Messages

 • 

195.8K Points

9 years ago

Very simply, what you are claiming is not possible. Not even remotely. There is only one color profile in the file.

And what file data are you looking at?

That sounds more like QImage has a bug reading color profiles.

14 Messages

 • 

202 Points

9 years ago

Can I send you some files to look at? I can send you files shot side by side that are giving me different results.
I have been talking to Mike Chaney with Qimage and sent him a file that PS is reading as and Adobe RGB and Qimage is reading as srgb, he put it through XVI32 hex editor and the info has the default color space as srgb I can attach the screen shot he sent me.

14 Messages

 • 

202 Points

9 years ago

Okay, so maybe not duel color spaces, but definitly not processing or saving files in the same color space each time. Below is the info from two files shot seconds apart and treated/processed exactly the same.

15.1K Messages

 • 

195.8K Points

9 years ago

By default, Photoshop preserves the profile in the document. That means that when you open a file with an sRGB profile, it will be saved with an sRGB profile. The working space profile only applies for documents that have no profile.

The Image Processor script has an option to convert documents to sRGB.
My guess is that you had that option on for some batches, and off for others.

14 Messages

 • 

202 Points

9 years ago

Nope, that option is definitly off. The two files above were shot seconds apart, downloaded all together, processed all together. In this session 12 out of 100 have the info like the top, and the rest were processed correctly and have the info like the bottom. Absolutely no difference in the handling of these files.
I will add a screen shot of my Image Processing settings

15.1K Messages

 • 

195.8K Points

9 years ago

Well, somewhere you are converting the image profile, or opening images that have a different profile. Photoshop can't just change the profile without the user telling it to.

14 Messages

 • 

202 Points

9 years ago

I processed the same files with CS3 and they all processed with the exact same color space, not randomly one file here and there.
So HOW am I telling it to change profiles, when they are processed exactly the same? I can accept user error - if Ican figure out why the same procedure I have used on all files are producing different results.

As of now My color settings are :
I have the settings as
Noth America Prepress 2

Working Spaces --
RGB Adobe RGB (1998)
CMYK U.S. Web Coated (SWOP) v2
Gray Dog Gain 20%
Spot 20%

Color Management Policies

All marked Preserve Embedded Profiles
and all 3 boxes checked

Conversion Options

Engine Adobe (ACE)
Intent Relative Colorimetric
All three boxes checked

14 Messages

 • 

202 Points

9 years ago

working with Mike from Qimage that looked at actual images, we have narrowed it down to the 12.0.4 update. When he updated from 12.0 to 12.0.4 he got the same behavior I am getting.
I have also narrowed down the exact date this problem started happening - July 15, 2011. All sessions to any date before that are fine - all sessions after that date have files randomly showing up with srgb.
Is there a way to check a log to see when my PS made that update?

2 Messages

 • 

70 Points

9 years ago

I think I have the same problem. My psd files are tagged pro-photo but Qimage is randomly assigning some files as srgb. If I run qimage twice, a different set gets the srgb designation. I have the professional addition and I believe this just started happening in the spring of this year.

14 Messages

 • 

202 Points

9 years ago

http://feedback.photoshop.com/photosh...

You can go to this post, although some of the posts were deleted.
Mike Cheney from Qimage found the problems in BOTH PS CS5 updated to 12.0.4 and in Qimage. He promptly fixed the Qimage Ulitmate version within 24 hours of discovering the qimage problem, so it would work with the still denied problem in CS5. Even though all participants did not experience the problem till the PS update, and had been using the different versions of qimage, and had not changed their workflow.

5 Messages

 • 

130 Points

9 years ago

I have to agree with Rebecca. SOmething happened to PS CS5 along the way. I have been using Qimage for years without color profile problems until this past summer. I reported the "sRGB" profile issue to the Qimage's Mike Cheney. He immediately responded with the "PS CS5" bug. (It did start with v 12.0.4).

I have switched back to PS CS4 and have not had the problem again.

It only affects jpegs as far as I can see. No problem with PSD or TIFF, but I only print from jpegs.

15.1K Messages

 • 

195.8K Points

Please read the existing topic (there's more in the user to user forums).

QImage had a major bug, and a trivial change in Photoshop exposed the bug in QImage. The Photoshop team researched the problem and identified the nature of the bug in QImage, which QImage then fixed.

2 Messages

 • 

70 Points

9 years ago

Actually Cheney only fixed it for those subscribing to Qimage's subscription service. Those of us who bought other editions with "life time support" have been left out.

15.1K Messages

 • 

195.8K Points

Ouch. That was an "oh, crap, how did it ever work" sort of bug in QImage. I assumed he fixed it in a dot release for everyone.

5 Messages

 • 

130 Points

9 years ago

It only appears with CS5 12.0.4. I went back to CS4 and problem solved.

This is from Mike Chaney:
"They want to blame Qimage (and BreezeBrowser, and others) but the problem is that their software is corrupting JPEG images. They claim it's a "trivial bug" in their software, yet it's been months and they've made no attempt to correct the corruption.
Perhaps one of the 800 employees they laid off was responsible for the fix, I don't know."

Here's the truth:

http://tinyurl.com/3urjl6h

15.1K Messages

 • 

195.8K Points

The truth is that QImage was not reading JPEG files correctly. QImage was searching for the first color profile in the JPEG file instead of parsing the JPEG structure correctly (sort of like searching a document for a word and assuming that what follows is the definition of the word: that doesn't even work on a dictionary)-- so it found profiles in thumbnails, and could easily have found bad profile references due to the failure to parse the file structure.
The fix was to read the JPEG structure correctly -- which is not a "workaround for an Adobe bug", but fixing a major flaw in QImage software.

Photoshop's JPEG files were not corrupt in any way, just changed in a minor detail, so there is no urgency in fixing this very trivial issue on the Photoshop side. QImage was not reading valid files correctly -- that was important to fix ASAP.

I'm really sorry to hear that the makers of QImage have chosen not to be honest with you in this matter. Mr. Chaney appears to have mischaracterized the nature of the change in the files, as well as the nature of the flaw in QImage's code.