Quark Forums

Could someone please explain to me why 100% RGB Blue in Quark 8 has a Red contamination on my monitor (MacBook 2GHz Intel Core 2 Duo)? Pure Blue either displays as: R-11%, G-0%, B-100% (QuarkXPress 7.0 Default) or R-55.3%, G-0%, B-100% (QuarkXPress Emulate Legacy) depending on which preference is selected in the Color Manager. Although the QuarkXPress 8 Color Palette tells me my Blue is pure (R-0, G-0, B-100%), it definitely doesn't look blue and I am reluctant to migrate my files from QuarkXPress 7.3 where the Blue is 100% pure on both my monitor and in the Color Palette. Any insight would be welcome. Thanks!

This appears to be a display issue only.  The blue elements output correctly as just 100% Blue and convert to CMYK the same in 7 as in 8.

Thank you Mike for your response, but I'm afraid it doesn't help me, since RGB documents still look fine in QuarkXPress 7, but are contaminated with Red in QuarkXPress 8 running on the same MacBook. It may be "a display issue" only, but it is still annoying and I'd say that it is a QuarkXPress 8 issue and, without an explanation for it, seems to be a bug. Furthermore, "DigitalColor Meter" (from Apple) shows clearly the 11% and 55.3% (!!) Red contamination of the Blue component in QuarkXPress 8 which is absent in QuarkXPress 7. For those people likely to make use of the web authoring tools in QuarkXPress 8 this will prove extremely annoying, since a correct visual assessment of screen colours now seems impossible. More help needed please!

 Hi !

I've just installed QXP 8 on my PC, equiped with Windows XP SP2 and two Dell 27" screens,  and I have the exact same problem. 

It is clearly a major bug, that render the product unusable until it is corrected. Of course, QXP 7 blue is fine.

I've placed  a bug report to the European customer service, in the hope to quickly receive a solution

 Well, I've juste received an answer from Customer support. 

Solution 1 : set Monitor Profile to QuarkXpress Legacy RGB. This is in Edit/Setup/Display (my install is in French, so I'm not sure of those names...).

Solution 2 :  set Source Parameters to QuarkXpress 7.0 Default, in Color Management

 Hope that will work for you...

 

 

Thanks Anciv, but this doesn't work. In QuarkXPress 8, with the Display (Preferences) set to "QuarkXPress Legacy RGB" and Color Manager (Preferences) set to "QuarkXPress 7.0 Default" the AppleColor Meter reading for 100% Blue is R-0, G-13.3%, B-99.2%. And with the Color Manager (Preferences) set to "QuarkXPress Emulate Legacy" the AppleColor Meter reading for 100% Blue is R-7.5%, G-2.4%, B-98.4%. It looks better, sure, but it's still fumbling in the dark and remains a major problem. Exported to QuarkXPress 7, with the Display (Preferences) set to "Automatic", it doesn't matter whether you are in "QuarkXPress 7.0 Default" or "QuarkXPress Emulate Legacy" - the same Blue reads as 100% with no problem.

 that's too bad. Then, the solutions I got are for PC.  Try to ask your Customer support rep.

Good luck !

I tried Anciv's suggestion on my iMac and it didn't work for me either, but it did give me an idea of how to proceed.

 

Display--Monitor Profile set to Adobe RGB

Color Manager--Source Setup set to QuarkXPress 7.0 Default.

 That seems to help with the RGB page elements.  I can't speak to how it will handle CMYK objects.  

 

Hope this helps

Hi Mike, thank you for continuing to help. Your suggestions seem to be the answer. With the Display and Color Manager preferences as you indicate, I made up a file of 6 colour swatches (R,G,B and C,M,Y) in QuarkXPress 7 and annotated them with their AppleColor Meter readings (the Red, Green and Blue being 100% pure). I then opened the file in QuarkXPress 8 using the same preferences and lo and behold, the AppleColor Meter readings were identical except for the Red swatch which had a Blue component of 0.4%. If, however, you set the Monitor Profile to "Apple RGB" instead of "Adobe RGB", the AppleColor Meter readings are absolutely identical and the CMY colours are possibly more accurate. Job done, I would say and confidence restored. Thanks once again.

 Glad I could help.

 I have logged this with R&D and they are working on a fix for the problem.