Jump to content

Recommended Posts

Where is the bug? – Your video shows a swatch named "0975d0" with its values "066DB6" / "88c 51m 0y 0k".

Note:
• A swatch name reflects its values only for its first auto-named version.
• The color values depend on the selected mode during creation. (e.g. cmyk, rgb, hex...)
• A color mode change is influenced by the document's color space + the profile.


macOS 10.14.6, Macbook Pro Retina 15" + Eizo 24", Affinity in Separated Mode (documents merged)

Share this post


Link to post
Share on other sites

I made swatches for this customer and never changed the colour. My docs all have CMYK/8 and I export them to either Coated or Uncoated FOGRA profiles.

Share this post


Link to post
Share on other sites
26 minutes ago, abra100pro said:

I made swatches for this customer

But how did you make that swatch, and how did it get its name. You haven't shown us far enough back.


-- Walt

Windows 10 Home, version 2004 (19041.388),
   Desktop: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970
   Laptop:  8GB memory, Intel Core i7-3625QM @ 2.30GHz, Intel HD Graphics 4000 or NVIDIA GeForce GT 630M
Affinity Photo 1.8.5.703 and 1.9.0.864 Beta   / Affinity Designer 1.8.5.703 and 1.9.0.864 Beta  / Affinity Publisher 1.8.5.703 and 1.9.0.863 Beta.

Share this post


Link to post
Share on other sites

I made it by entering the hex value into the hex-field and adding it to my swatches. I use theses swatches ever since and due to a colour conflict with the printer I counter checked to find the value being different. I dunno when It happened - I just know that I did not change the swatch.

Share this post


Link to post
Share on other sites

Thanks. In that case, I have no idea what's happening.


-- Walt

Windows 10 Home, version 2004 (19041.388),
   Desktop: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970
   Laptop:  8GB memory, Intel Core i7-3625QM @ 2.30GHz, Intel HD Graphics 4000 or NVIDIA GeForce GT 630M
Affinity Photo 1.8.5.703 and 1.9.0.864 Beta   / Affinity Designer 1.8.5.703 and 1.9.0.864 Beta  / Affinity Publisher 1.8.5.703 and 1.9.0.863 Beta.

Share this post


Link to post
Share on other sites

It is not clear from the video what has caused this problem, but it seems that your 0975d0 swatch might have actually been created in CMYK mode and just renamed using the hex notation. When you assign on the video the 0975d0 swatch to the object and then double click the fill color well on the Color panel, it can be seen that you have CMYK sliders active and the CMYK values are percentages. At least on Windows this is an indication that the color definition of the object has been given and saved as a CMYK value. If an object with an RGB definition is selected, the CMYK sliders show 8-bit values (0..255).

In the example below Coated Fogra 39 is used as the CMYK color profile (and sRGB as an underlying RGB profile). First an RGB swatch is created using hex notation #0975d0 which will get a CMYK conversion value of C85 M53 Y0 K0 in this profile context. Then a CMYK swatch is created using the C85 M53 Y0 K0 definition which will get an RGB conversion value of #256db5 in this profile context. The other of the blue rectanbles has the RGB version swatch assigned, and the other the CMYK version.

When the fill well of the Color panel is double clicked, the color mode of the swatch definition is reflected in the CMYK slider values: they are percentages when showing color values for a CMYK based swatch, and 8-bit values when showing color values for an RGB based swatch.

colordef_rgb.jpg.aa309cf48fdea2fc7539d261d9d4b133.jpg

colordef_cmyk.jpg.0b58052a6736467c4294c8b4857b58fb.jpg

I am not aware of a situation which could cause an RGB based color definition in an application palette to convert to CMYK, but I have very little experience on application palettes. Is this a palette that you have used with multiple publications? Can you check whether its saved color definition for  0975d0 is really CMYK based or RGB based (or if this could be just a document-specific problem)?

Anyway, when I tested these definitions with a variety of different color profiles, both swatch definitions correctly retained their original definining color values (but were naturally converted differently to equivalent CMYK and RGB values depending on the profile). 

 

Share this post


Link to post
Share on other sites

Here is an example of how PMS 2935 C (for coated stock) and PMS 2935 U (for uncoated) are translated to CMYK when using different apps:

pms2935c.jpg.91bab3f0fc678d7d55a3a7ea8d8a2ba2.jpgpms2935u.jpg.1e8ead68221a467366f324778ee47af6.jpg

pms2935_fogra27.pdf

pms2935_fogra29.pdf

When using PSO Coated v3 and PSO Uncoated V3 (Fogra 52), all these values would again be a bit different. And none of these values would take into consideration exact properties of a specific paper. You simply cannot give "correct", generic CMYK values. If color accuracy is important and you have a specific reference (like a PMS tone), you should use spot inks. 

Share this post


Link to post
Share on other sites

Thanks Lagarto - the Pantone has nothing to do with it - I just switched shortly to it and then back to show that I really have selected the right swatch colour. But your answer above is interesting - I have to dive into this a bit more... I usually start with UncoatedFOGRA CMYK. I understand that the CMYK (and all other model's) colours is interpreted by not only the HEX code but other things like Profiles. I'm still confused about when this happened. I use this swatches in AD and APub in different documents.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.