|
Title: Since upgrading PS CS4 to CS6 Qimage Pro darkens some images Post by: cutupguy on February 26, 2013, 01:52:25 AM Win 7 (64)
Here is a problem I am having with Qimage Pro v2010.210, that started after upgrading to Photoshop CS6: Saturation and brightness look good in PS and in Bridge, but when I load the same files in Qimage Pro, the image goes dark and the colors are desaturated for lack of a more technical term. See screen shot of the same file displayed in Qimage on the left and Bridge CS6 on the right; (http://www.Photocutouts.com/newsitepics/newsletter-pics/qimage-screen.jpg) (This photo has ProPhoto RGB color profile) Here is a screen shot of my Qimage setups; (http://www.photocutouts.com/newsitepics/newsletter-pics/qimage-preferences.jpg) The most perplexing thing is that it does NOT happen on all images. The prints from Qimage Pro print exactly like what Qimage displays. Other prints in the same print job looked in QI just like they did in Bridge and PS and they printed that way. Something is happening to some images between PS and QI. My work flow is I take my customer's .jpgs and open them in Adobe Camera RAW and send them to Photoshop with ProPhoto RGB color profile. I then print them in QI without making any edits. What have I done!? Thanks for any help! Al Title: Re: Since upgrading PS CS4 to CS6 Qimage Pro darkens some images Post by: Fred A on February 26, 2013, 10:41:55 AM Quote The most perplexing thing is that it does NOT happen on all images. The prints from Qimage Pro print exactly like what Qimage displays. Other prints in the same print job looked in QI just like they did in Bridge and PS and they printed that way. Something is happening to some images between PS and QI. My work flow is I take my customer's .jpgs and open them in Adobe Camera RAW and send them to Photoshop with ProPhoto RGB color profile. I then print them in QI without making any edits. What have I done!? Thanks for any help! Hi Al, First let's verify the profile you show in the Color Management box along side of UNKNOWN. I can't see it, and I want to be sure it's a common sRGB type. Next, your workflow... To the best of my knowledge, not being a CS expert, I don't think you can take your customer's jpg and put it into Adobe Camera Raw. Then you say you send them to Photoshop (from where? Bridge) "WITH" the prophoto Rgb profile. What does with mean.? Is the profile embedded in some images and dropped in others? I assume they are still JPGS? I can ask you to hover the mouse pointer over the thumbnail and read the information at the lower left (The Hotbar). It will tell you the colorspace and if you see asterisks, that color profile is embedded. The easier and faster way to solve this is if you would be so kind to send me the image that you show in your screen snap. Send that one and one other if you can that is working OK. Please don't resave, or resize... just send the exact image that you use as an illustration. My email address is: wathree.ssz@verizon.net I can handle 20 megs per email, Or you can use the free file transfer service and send whatever you wish. https://www.wetransfer.com/ Awaiting your reply. Fred Title: Re: Since upgrading PS CS4 to CS6 Qimage Pro darkens some images Post by: admin on February 26, 2013, 05:52:24 PM It sounds like it could be the same bug from CS5. It's sad... but it wouldn't surprise me if Adobe still hasn't fixed this bug in CS6:
http://ddisoftware.com/tech/qimage-ultimate/qimage-exposes-photoshop-cs5-%2812-0-4%29-jpeg-corruption-bug/ Try the Qimage Ultimate demo because it has an improved (header) parser that doesn't stumble on the Adobe header format spec violation. If the Qimage Ultimate demo doesn't have the problem, it's likely the same bug. Regards, Mike Title: Re: Since upgrading PS CS4 to CS6 Qimage Pro darkens some images Post by: cutupguy on February 26, 2013, 10:27:43 PM You must be right, Mike. I installed the Demo of Qimage Ultimate and the offending file showed up as it should. No wonder I couldn't figure out what I was doing!
I just ordered the full version. Note to Fred: Thanks for your thoughtful reply. I really appreciate your efforts, but it looks like Mike has a good workaround for Adobe's bug. |