I have used Qimage for years and never had an issue -- ALWAYS perfect color match to Photoshop and to what I saw on the monitor and to what printed out.  That changed a month ago and have been printing (GAG) from Photoshop.

I am using a NEC 2690WUXi2 calibrated monitor, HP B9180 printer and Windows Vista 32.  With a fresh calibration of the monitor, the colors printed in Photoshop are an exact match for what I see on the screen -- using Photoshop-managed colors.

In the past, the colors printed in Qimage Pro were equivalent and the detail slightly better than that of Photoshop plus the convenience of selecting a couple of dozen images to print and go off and let the printer do its thing in Qimage.

Now, mainly the reds are an issue -- being dull and more maroon when printed and I can see that color change in the images as shown in Qimage and they print exactly as shown in the Qimage selections on the screen.  
--For Monitor ICC, I have selected the ICC profile for the monitor I have shown above with D65 and Gamma 2.2 as usual.  
--For Printer ICC, I have selected the HP PSPro B9100-Advancced Photo Glossy as usual.
--In Qimage color management, all of the following are checked: Honor EXIF color space tag..., Monitor Profile Enabled, Printer Profile Enabled, Printer Profile Rendering Intent -- Perceptual, Embed ICC profiles in saved/converted images...

In the Printer Driver -- Application Managed Colors is selected along with the correct paper and size

I have even uninstalled the latest version of Qimage Pro and gone back to a much earlier version that worked fine, but the same exact issue occurred -- what I saw on the monitor was what printed out and what I saw for images with bright red on the monitor were dingy maroon.

Also, I RESET ALL program settings and started from scratch on setting up the ICC profiles listed above.

Any ideas as to what I have done different to cause the color shift -- I AM printing what I see in Qimage but what Qimage is seeing is NOT what Photoshop shows or prints.

Suggestions/opinions/ideas???

Thanks,

MikeSp

Hi MikeSp,

Adding to Terry's suggestion, often reds going to maroon if viewing/printing an srgb (or other) image in argb. It will always print OK (colourwise) in photoshop, if the image was edited in photoshop. It makes no difference there if you 'assign' a colourspace or if you 'convert' to a colourspace. However, before you save the image from photoshop for printing in Qimage, or any other colour managed print or view program, you need to 'convert' in photoshop to the correct colour space. If you have an assigned colour space in photoshop, it may not print correctly outside of photoshop (unless you have assigned the same colour space as is embedded in the image).

I would suggest that you check your settings in photoshop - under the 'Edit' tab, -  'Assign Profile' and 'Convert to Profile' (towards the bottom of the drop down menu), and use a sensible rendering intent, of course.

So, for example, in photoshop you can 'assign' pro-photo to your srgb image, so that you can carry out image editing, taking advantage of the smoother colour transitions obtained in sky and skin tones, and print within photoshop, since photoshop knows you have assigned pro-photo, but if you save the image, it will be saved as srgb. You must 'convert' the colourspace to srgb, or any  colourspace that the other print software can handle _before_ you save the file in photoshop. hth. 

Best wishes,

Ray 

Here is a screen capture of a red car in the Qimage print queue -- notice how maroon it appears -- and it prints out exactly the same.  The shot was taken in raw and converted into the aRGB color space by Capture One 6 Pro.  In the next posting, there is a screen capture of the image in PS.

MikeSp

Mike,
Did you check the image profile in Qimage as suggested in reply #1?
If Qimage is printing what you see on the screen in Qimage, then a profile mis-match seems to be the most likely problem.
Terry

Mike,
I know him/her very well 
Pleased to hear the problem is being solved and that we were able to help 
Terry

Good idea -- however, the issue I was having was two-fold: the wrong ICC profile in Capture One AND AND AND the wrong profile in PS too...  I DID make the assumption that once set, they would never change, but with upgrades, they did change.

Thanks,

MikeSp

Yes, fixing wherever the profile mismatch occurred (maybe something stripped the profile) is the way to be sure in the future, but you do know that Qimage can override any profile, right?  So on the problem images you have now, just use the "ICC override" filter in the image editor (batch filter in old Qimage versions) and pick the proper Adobe RGB profile for that image.  That should fix it (in Qimage anyway).

Mike

The issue with Qimage reading the ICC profile is continuing and it may or may not be based upon Qimage -- probably not, but would appreciate hearing from the experts.

I have two Adobe RGB (1998) ICC's listed in Capture One 6 Pro that I use to convert raw images to jpgs -- it doesn't matter which one I use, because WHEN I convert the same image 8 times with either of the two aRGB ICC's and send the resulting JPG's to Photoshop CS5, where it defaults to Adobe RGB, Qimage will read ~6 of the resulting images as sRGB and 2 as aRGB.  I have Photoshop set to notify me if there is an ICC color space difference and it does not do so and thus, CS5 appears to be reading the converted images ALL as aRGB.

I replaced the Adobe RGB (1998) ICC in Windows Vista 32 with a brand new copy from Adobe -- made no difference.

IF I use Adobe Camera Raw to convert my raw images to JPG's, THEN Qimage will correctly read ALL of them as aRGB.

All three programs (C1 6 Pro, PS CS5 and Qimage Pro) are normally stable, dependable programs.

BTW -- I can visually pick out the thumbnails in Qimage that are in the aRGB color space when testing with 8 of the same exact image with the raw conversion procedure although I still use the "Display Image Info" to verify.

I realize it is possible for color space ICC's to become corrupted and that several different programs can put in their own aRGB ICC.

I also realize it is unlikely that Qimage is the culprit based upon the information given above.

Thoughts/opinions as to what to do next in order to get my workflow back to a dependable aRGB color space?

Thanks,

MikeSp