Jump to content
You must now use your email address to sign in [click for more info] ×

APub: Please (weeping) help with the PDF CMYK Debacle


Recommended Posts

OK, here's the deal. Whenever I "place" anything created outside Affinity Publisher into Affinity Publisher, and then export the publication to PDF for CMYK printing, APub changes the CMYK values in the placed file!

I have tried placing PDF files and Affinity Designer files, always the same result. I have tried every setting I can think of under preferences and PDF export that I can find. I don't want this! Why does it do this? I want to stay with APub, but this issue has me and our publishing company back with InDesign. 

I export to PDF from Designer, color values remain correct. I import the same file to APub, then export the page to PDF, the color values have changed! This is especially vexing with 100% black, which ALWAYS gets changed to a combination of CMYK values. My printer can't work with this. 

However, if I fill a square with 100% black in APub, then export to PDF, the color value remains 100% black. Argh! But, if I import a PDF or a native Designer file, then export the page to PDF from APub, I get a mix of CMYK values instead of 100% black. Argh again!

This CANNOT be right. There HAS to be a simple switch fix for this. Surely SOMEBODY out there has solved this. Please help! 

Thank you in advance. 

Link to comment
Share on other sites

The 'easiest' would be to avoid colour conversion between APub and placed document and export, by setting both files, .afpub and afdesign, to the same colour space & profile and export with this profile "As document" (in Export > More > … ).

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 only

Link to comment
Share on other sites

My experience when placing AD content using the same color profile is similar, so color definitions should be retained, at least when not using complex adjustments (I cannot say whether they would be applied similarly as when applied to native Publisher objects or when used in Designer and resolved, or exported from, there). But PDFs placed for passthrough is a completely different and more complex story.

There the rule of thumb is that you cannot use PDF/X-based export methods with PDF content that is created with non-PDF/X  based methods, and have it passed through. Instead, this content will always be rasterized and with incorrect color values. So whenever placing PDFs to be passed through and they are not PDF/X-based, export using "PDF (press-ready)", which uses PDF v.1.7. When using PDF/X-based export method, all PDF content to be passed through must be PDF/X-based and produced with the same or minor PDF version number, except when using PDF/X-1a:2003, which will rasterize all placed PDF-content.

As for reading color values, it should be noted that if the design contains any transparency, Affinity apps typically apply sRGB blending space to transparency groups which confuses at least Adobe Acrobat Pro. It certainly confuses most users, prepress personnel included, and I am not sure if it would confuse RIP, as well, resulting in getting wrong colors on paper.

The following clip demonstrates the complexity that using an RGB blending space applied to CMYK objects causes for interpreting color definitions of an Affinity produced PDF file. It was exported using the default PDF 1.7 "PDF (press-ready)" preset that embeds the document ICC. Not embedding the document ICC makes initial reading of color values in Adobe Acrobat Pro a bit less confusing because the simulation profile does not need to be matched with the document profile, but it does not resolve the problem related to mixing RGB and CMYK color modes in transparency groups. In the end, the video shows how a PDF 1.7 exported from InDesign with default settings, with placed Publisher created PDF files, uses DeviceCMYK blending space for the transparency group and shows correct color values in Output preview no matter which simulation profile is used (that's because all color involved operations, including transparency blend space are DeviceCMYK and not dependent on profile-based calculations). 

Note that if you place Designer content in a Publisher file (or any Affinity file) and it uses different color profile, all color values are recalculated so e.g. CMYK values won't be just passed through. Passing through is only supported in placed PDF content, and there, too, in a very limiting way. Note too that placed Designer content will have their native color profiles applied, while placed non-Designer files that are interpreted (e.g. AI files, PDF placed for interpretation, EPS files), will have the profile assignment done according to the setting in Preferences > Color.

 

Link to comment
Share on other sites

On 5/12/2023 at 7:31 PM, thomaso said:

The 'easiest' would be to avoid colour conversion between APub and placed document and export, by setting both files, .afpub and afdesign, to the same colour space & profile and export with this profile "As document" (in Export > More > … ).

Thank you for the replies. I will try the suggestions (away from the office at the moment). But, bottom line, no one so far knows a straightforward fix. Hmmm. InDesign just leaves the values the same when exporting placed CMYK PDF content to InDesign PDF. APub changes them. If one of these works, at least we could work them into our work flow. 

Link to comment
Share on other sites

  • 5 months later...

affinity publisher is just the worst offender when it comes to placed pdf documents. i would recommend, if possible, converting all pdfs to eps documents or us the action "convert all fonts to outline" in acrobat pro and then place those pdfs as interpreted. 

passthrough is just not working with any pdf besides publishers own. specially adobe pdf exports don't work in publisher. 

just outline fonts in acrobat and then interpret the placed pdf is the best option, highly recommended, all colors as expected, no errors.

downside, you will need to purchase a full license for acrobat pro

 

image.png.074359ef386912159008b6ed665cd9c2.png

Link to comment
Share on other sites

just in case you are wondering: nothing helps that situation,

1) pdf/x output intent set to same as publisher document - wrong colors on passthrough

2) every single element tagged with same profile as the publisher document - wrong colors on passthrough

3) complete pdf decalibrated and all elements set as device cmyk - wrong colors on passthrough

Link to comment
Share on other sites

Your problems are probably caused by having non-PDF/X-based or PDF/X-1a-based PDFs placed for passthrough, and exporting using any PDF/X method. These kinds exports are typically rasterized by Affinity apps. If you have non-PDF/X-based placed PDFs that you want to pass through, the best choice to succeed is choosing "PDF (press-ready)" that by default uses PDF version 1.7, convert color spaces to CMYK, and deselect profile embedding. This will create a Device-CMYK PDF with native color values and original fonts embedded, and respects overprint attributes, etc. [EDIT: and passes through all kinds of PDFs]. If your placed PDFs are all PDF/X-based [EDIT: and you need to use PDF/X-based export method], you should choose PDF/X-4, to make sure that export PDF uses the same or later PDF version as placed PDFs. 

Converting to EPS might work, but then it is good to know that overprint attributes are not honored, and spot colors are not supported. These are Affinity-specific limitations (and fonts left embedded would automatically be converted to curves, too). Letting Affinity interpret placed PDFs, especially if fonts have been converted to outlines, might work, but then you need to pay attention to possible color profile conflicts, because interpreted (CMYK) PDFs will be assigned the working color (CMYK) profile, not the document color profile (and never discarded and just passed through, as by default happens when working with Adobe apps). And if there is a profile conflict at export time, all CMYK color values will be recalculated (causing e.g. K100 blacks becoming four-color blacks).

Link to comment
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

Terms of Use | 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.