phph

Dear Affinity Users and Developers
We’re just in the process of evaluating Affinity Publisher (tested with 1.7.0.305 and 1.7.0.312) and we’ve come upon a problem with the PDF/X export:
In our workflow our print PDF files are checked in Adobe Acrobat against the preflight profile PDFX-ready Sheetfed Offset Classic HQ V1.5. Among other things this profile checks the MD5 checksums of the used ICC profile against a pre-defined list of profiles known to be appropriate for offset printing.
When exporting a PDF as PDF/X-1a with the ICC profile ISO Coated v2 300% (ECI) from Affinity Publisher the preflight returns this error:
Looking at the preflight report in the section Output Intents I noticed a difference between a PDF exported from InDesign and Affinity Publisher:
The Output Intent is stated as ISO Coated v2 300% (ECI) for the InDesign-PDF and as ISO Coated v2 300% (ECI) (Custom) for Affinity Publisher The Color Management Module had a value of HDM (InDesign) and lcms (Affinity Publisher). Primäre Zielplattform (in English probably: Primary Target Platform): empty (InDesign) and Apple Computer, Inc. (APPL) (Affinity Publisher) Profil erstellt mit (in English probably: Profile created with): Heidelberger Druckmaschinen AG (HDM ) (InDesign) and lcms (Affinity Publisher) The other fields were the same in both files. So I suspected this to be the reason for the different MD5 checksums. But not being an expert on the ins and outs of PDFs and colour management I turned to HilfDirSelbst.ch where we discussed this (in German) in this thread. Olaf Drümmer of callas concluded (my translation):
So the question is
Is Affinity Publisher correct in changing the meta-data of the profile when writing the PDF file? And if so: Would PDFX-ready need to append their list of MD5 checksums to include those of profiles created with lcms? Any insights and suggestions would be greatly appreciated!
Best
phph

Hi everyone
As we’re still experiencing the failure of the preflight check in Adobe Acrobat even with the latest Publisher beta:
Has anyone been able to export a PDF-X1a with a profile such as ISO Coated v2 that passes the preflight profile PDFX-ready Sheetfed Offset Classic HQ V1.5.? We continue to get the error
Thanks for any input!

Dear Affinity Users and Developers
We’re just in the process of evaluating Affinity Publisher (tested with 1.7.0.305 and 1.7.0.312) and we’ve come upon a problem with the PDF/X export:
In our workflow our print PDF files are checked in Adobe Acrobat against the preflight profile PDFX-ready Sheetfed Offset Classic HQ V1.5. Among other things this profile checks the MD5 checksums of the used ICC profile against a pre-defined list of profiles known to be appropriate for offset printing.
When exporting a PDF as PDF/X-1a with the ICC profile ISO Coated v2 300% (ECI) from Affinity Publisher the preflight returns this error:
Looking at the preflight report in the section Output Intents I noticed a difference between a PDF exported from InDesign and Affinity Publisher:
The Output Intent is stated as ISO Coated v2 300% (ECI) for the InDesign-PDF and as ISO Coated v2 300% (ECI) (Custom) for Affinity Publisher The Color Management Module had a value of HDM (InDesign) and lcms (Affinity Publisher). Primäre Zielplattform (in English probably: Primary Target Platform): empty (InDesign) and Apple Computer, Inc. (APPL) (Affinity Publisher) Profil erstellt mit (in English probably: Profile created with): Heidelberger Druckmaschinen AG (HDM ) (InDesign) and lcms (Affinity Publisher) The other fields were the same in both files. So I suspected this to be the reason for the different MD5 checksums. But not being an expert on the ins and outs of PDFs and colour management I turned to HilfDirSelbst.ch where we discussed this (in German) in this thread. Olaf Drümmer of callas concluded (my translation):
So the question is
Is Affinity Publisher correct in changing the meta-data of the profile when writing the PDF file? And if so: Would PDFX-ready need to append their list of MD5 checksums to include those of profiles created with lcms? Any insights and suggestions would be greatly appreciated!
Best
phph

yes, please fix this. I see people have been mentioning it for over a year. Although a brush and brush preset are not necessarily the same thing please highlight it or something. Working with various brushes at same time I lose sight of which shape I selected last. There's no name of brush or any type of visual identification what I'm working with.

I have the same problem. So to keep the composition non destructive, I select the layers affected by the live filters > Edit > Copy Merged > Paste.
Al least it keeps the original layers for future change, but of course, the copy merged must be done again after the change and before the new export.
Not workflow friendly
I am on mac
 

Free Mockup A2 poster design for Instagram posts
 
Download it for free here.

Exact same problem here since the first beta. So at least this behaviour is consistent
I guess as long as ICC profiles written by Publisher have the "wrong" MD5 checksum the preflight will fail. You could add the wrong checksum to your preflight profile so it stops complaining. However, your printshop may still complain then.

Glad that Serif is looking into this, and I agree that right now, Layers is actually Objects. It's very similar to how Illustrator works, except that each Illustrator object in the Layers panel is a subset of a layer and is only visible if you expand the layer by clicking the disclosure triangle. Everything has to be on a layer, and if you make or paste in a new object, it goes onto the currently selected Layer. As it is right now, I can move my Publisher objects on to layers but it's a pain and if I'm not paying attention, objects can either end up on or off a layer.
It's not the only feature I've found that I feel is incorrectly and misleadingly named. I still think in Photo that the Perspective feature should be named Skew, and a proper Perspective feature should be added.

Hi melriksdesign,
Welcome to Affinity Forums
Global layers are already planned for an upcoming update (after Publisher's release eventually but I may be wrong here).

Same here,
my work depends on "global" layers aka the InDesign layers.
Example: a brochure which I design for 6 different languages:
masterpages used for different types of pages (cover, intro, detail,…) layers used for different content (languages) and backgrounds. I have al my pictures and backgrounds in one layer, text on the others, so I can easily switch which brochure I can edit or export to PDF. This is really necessary if we want to use aPub for long and complicated documents.