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?
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?
Problems
•
Updated
9 years ago
0
14
Helpful Widget
How can we improve?
Tags
image processor
color space
adobe rgb
srgb
Responses
Official Solution
chris_cox_2148894
15.1K Messages
•
195.8K Points
9 years ago
0
0
chris_cox_2148894
15.1K Messages
•
195.8K Points
9 years ago
And what file data are you looking at?
That sounds more like QImage has a bug reading color profiles.
0
0
rebecca_hardgrave
14 Messages
•
202 Points
9 years ago
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.
0
0
rebecca_hardgrave
14 Messages
•
202 Points
9 years ago
0
0
chris_cox_2148894
15.1K Messages
•
195.8K Points
9 years ago
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.
0
0
rebecca_hardgrave
14 Messages
•
202 Points
9 years ago
I will add a screen shot of my Image Processing settings
0
0
chris_cox_2148894
15.1K Messages
•
195.8K Points
9 years ago
0
0
rebecca_hardgrave
14 Messages
•
202 Points
9 years ago
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
0
0
rebecca_hardgrave
14 Messages
•
202 Points
9 years ago
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?
0
0
jim_larocco
2 Messages
•
70 Points
9 years ago
0
0
rebecca_hardgrave
14 Messages
•
202 Points
9 years ago
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.
0
0
david_savarino
5 Messages
•
130 Points
9 years ago
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.
1
0
jim_larocco
2 Messages
•
70 Points
9 years ago
1
0
david_savarino
5 Messages
•
130 Points
9 years ago
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
1
0