Mike Chaney's Tech Corner
April 19, 2024, 10:30:09 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Qimage registration expired? New lifetime licenses are only $59.99!
 
   Home   Help Search Login Register  

Professional Photo Printing Software for Windows
Print with
Qimage and see what you've been missing!
Pages: 1 [2] 3 4
  Print  
Author Topic: off color problem  (Read 53886 times)
hardgravephoto
Newbie
*
Posts: 14


View Profile Email
« Reply #15 on: September 02, 2011, 02:13:16 AM »

I started having the EXACT same problem just about a month ago and cannot get it figured out. I use Adobe RGB (1998) and in all my processed files the color profile reads Adobe RGB in every program except Qimage. Starting on a session done on June 17th, it is just random files that end up reading at srgb.  Yesterday's session had 119 files and one of them randomly reads wrong only in Qimage.
I will be watching this thread closely and hopefull can contribute if I figure it out...

The only thing that I can think of that might be different is I am using a 64 bit computer, but I changed to 62 bit about 6 months ago
« Last Edit: September 02, 2011, 02:18:00 AM by hardgravephoto » Logged
Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3247



View Profile WWW
« Reply #16 on: September 02, 2011, 08:02:05 AM »

Hi,
Quote
Yesterday's session had 119 files and one of them randomly reads wrong only in Qimage.
Perhaps you should be asking why the other programs are producing random results!
Qimage has strict rules on how it reads the colour space of an image and the sure way (highest priority in Q) is to have the profile embedded.
Q tells you what it is seeing, hover your mouse over a thumb and and see what Qimage is seeing as a profile in the Exif bar under the thumbs, last item on the right.
Also, right click on a thumb, select Display Image Info. As you move your mouse over the thumbs, the info for each will be displayed which includes whether or not a profile is embedded.
Qimage does acknowledge Exif profile data in an image, so a camera jpeg in Adobe RGB will be recognised, however the Exif data usually says something like "unknown" (ok. with sRGB) so an assmption has to be made that unknown means Adobe RGB.
Finally, read Qimage Help CM and input profiles.
Using a 64 bit OS makes no difference, Qimage Ultimate is a  64 bit compatible program.
Terry
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4120



View Profile Email
« Reply #17 on: September 02, 2011, 12:43:03 PM »

Anyone having the problem should send me the image file.  If it's too large to send, you can use http://yousendit.com.  If you get the wrong profile, the image is mis-tagged.  Only way I can know how it is mis-tagged is to see the image/file.  I've seen some programs lately that are saving conflicting information.  They'll tag one profile in the EXIF and embed an entirely different profile in another part of the image, creating a conflict.  So if I have example(s), I can see what is going on quite easily.  Without the examples, I can do nothing.

Thanks,
Mike
Logged
hardgravephoto
Newbie
*
Posts: 14


View Profile Email
« Reply #18 on: September 02, 2011, 02:07:26 PM »

Just sent a file from yesterday's session Smiley
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4120



View Profile Email
« Reply #19 on: September 02, 2011, 03:20:54 PM »

Just sent a file from yesterday's session Smiley

Thanks.  As I thought, that file is a mess.  It has sRGB and Adobe RGB embedded multiple times.  Look at the screen capture from the file you sent.  I've circled the relevant places in the file that show that this file has sRGB tagged.  You said they were processed in PhotoShop.  How?  Anything done different to these than the others that don't have the problem?  I'm just trying to figure out what was done in PhotoShop and what the files looked like before PhotoShop hosed them.

Mike
Logged
hardgravephoto
Newbie
*
Posts: 14


View Profile Email
« Reply #20 on: September 02, 2011, 04:06:25 PM »

Now we are getting somewhere Wink

I Process with Image Processor - CS5
 Just tried running it through CS3image processor on older computer and it processed all the files with none showing up as srgb in Qimage!  So now to find the photoshop problem solution

I wonder if there were any IP updates around the time the problem started... I guess on to another forum?  Can you tell me how you got the file info in that format to look at?
Thanks so much for your help!
« Last Edit: September 02, 2011, 04:09:34 PM by hardgravephoto » Logged
admin
Administrator
Forum Superhero
*****
Posts: 4120



View Profile Email
« Reply #21 on: September 02, 2011, 04:21:22 PM »

Can you tell me how you got the file info in that format to look at?
Thanks so much for your help!

I found the location by tracing Qimage's decoding of the embedded profile and then displayed it in my hex editor.  I use XVI32 as my hex editor: it's free.  All you really have to do is open the file you sent me in XVI32 and search for ICC_PROFILE because that's the official PhotoShop tag.  It points right to sRGB... twice.  And then Adobe RGB... once.  This looks like a classic case of some program not updating the file headers properly.  I see that a lot.  You start out with an sRGB image for example, convert it to Adobe RGB, make some changes, and then save.  Sometimes the program doing the saving doesn't have sense enough to remove the original embedded sRGB and it just adds an embedded Adobe RGB.  Now you have both, and a conflict.  Anyway, that's what it looks like to me since sRGB is embedded twice and Adobe RGB once in the same file.

Mike
Logged
hardgravephoto
Newbie
*
Posts: 14


View Profile Email
« Reply #22 on: September 02, 2011, 04:51:31 PM »

I switched color preferences in PS to North America Prepress and so far so good.  I did have it on North America General purpose - gone to custom by changing only the RGB setting from srgb to Adobe RGB.
Thanks so much for you help!!! Grin
 I'll let you know if things keep going great in the next week or if I still have issues.
Logged
hardgravephoto
Newbie
*
Posts: 14


View Profile Email
« Reply #23 on: September 03, 2011, 09:51:44 AM »

Problem not found and fixed after all Cry 
Now to find out why PS CS5 is randomly assinging some files with double color space profiles...
Any suggestions on where to look welcome.
Logged
rayw
Sr. Member
****
Posts: 440


View Profile
« Reply #24 on: September 03, 2011, 01:24:52 PM »

If it is .psd files that are  giving the problems, then you you need to know that that is 'owned' by Adobe, and from time to time they will change the specification. You should be able to get the latest specification of the  format from Adobe. I would imagine that Adobe can read their own file formats OK, but third parties - e.g. Qimage, and others, may not have been able to implement the latest changes.

Best wishes,

Ray
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4120



View Profile Email
« Reply #25 on: September 03, 2011, 02:04:04 PM »

If it is .psd files that are  giving the problems, then you you need to know that that is 'owned' by Adobe, and from time to time they will change the specification. You should be able to get the latest specification of the  format from Adobe. I would imagine that Adobe can read their own file formats OK, but third parties - e.g. Qimage, and others, may not have been able to implement the latest changes.

Best wishes,

Ray

Adobe has not published a PSD spec since PhotoShop 5.0 from a decade ago.  That's why not even their own products (Lightroom) are fully compatible with the PSD format.  I think PhotoShop is hosing JPEG files in this case though so PSD is likely not part of the problem.  Another thing Adobe likes to do is take an existing/international spec and add their own "tweaks" to it.  After a while, people claim that it is part of the spec when it is not.  Black point compensation in ICC profiles and alpha channels in TIFF files are good examples of that.  Lots of programs support those Adobe abominations but only because Adobe can get away with cheating... not because they are part of any spec but just because they are a big company.  I only mention that because the information in this thread means that Adobe either has a pretty major bug in their JPEG saving routine, or I guess it's possible that they added a new "feature" where they changed how profiles are embedded in JPEG's to show a "history" of all the profiles ever used.  Sounds ridiculous to me but you never know with Adobe.

Mike
Logged
hardgravephoto
Newbie
*
Posts: 14


View Profile Email
« Reply #26 on: September 03, 2011, 04:20:21 PM »

Only a jpg problem thus far,  Adobe claiming that it is impossible so I am sending files to someone there and the screenshot Mike attached with the red circles - we will see...
« Last Edit: September 03, 2011, 04:27:18 PM by hardgravephoto » Logged
admin
Administrator
Forum Superhero
*****
Posts: 4120



View Profile Email
« Reply #27 on: September 03, 2011, 05:41:21 PM »

Only a jpg problem thus far,  Adobe claiming that it is impossible so I am sending files to someone there and the screenshot Mike attached with the red circles - we will see...

Not to let Adobe off the hook... but I've tried replicating the problem and I can't so far.  You said you used "File", "Scripts", "Image Processor" in CS5.  I tried that with a number of options (on raw files), saving as JPG, and I only get one ICC profile embedded and not three like you got.  I'm starting to wonder now if it is a CS5 problem or somewhere else (before) CS5.  Could you send me one sample image before it goes through the CS5 image processor and tell me all your image processor settings so I can try replicating it?  Example: send me your 1775 image as it was before the image processor ever saw it.  Then let me know what settings you were using in image processor so I can repeat it.  I want to see if (a) the image before it went into the image processor had the problem and (b) if not, what the image processor does to it.  I know it's not a Qimage problem but a few other people have had the same issue and it would help me to know exactly what program/process is creating the problem and when (under what conditions).

Thanks,
Mike
Logged
hardgravephoto
Newbie
*
Posts: 14


View Profile Email
« Reply #28 on: September 03, 2011, 05:47:07 PM »

I sent it yesterday with YouSendit, I'll send you another one that processed correctly also.

I put two images that were shot side by side with the different results into the XVI32 and did a screen shot to send to Adobe
sending now

Acutally, I process by selecting all in bridge folder, going to tools - photoshop- image processor
I usually don't go to scripts, then image processor, but I can try that

« Last Edit: September 03, 2011, 06:05:13 PM by hardgravephoto » Logged
rayw
Sr. Member
****
Posts: 440


View Profile
« Reply #29 on: September 03, 2011, 06:17:26 PM »

Mitrajoon, the op of this thread uses psd files. Hardgravephoto said he had the exact same problem If he's not using psd, then it is not the same problem, and i guess it should be in a different thread.
Logged
Pages: 1 [2] 3 4
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Security updates 2022 by ddisoftware, Inc.