Placed PDF version is not compatible with the PDF export version

[Blake_S]

Can someone explain what does this mean?

The PDF export version is not known before you actually initiate the Export and select it,
yet this error seems to be thrown all the time in Live Preflight, before I actually select anything in Export function

[Blake_S]

2 hours ago, N.P.M. said:

https://affinity.help/publisher/English.lproj/pages/Panels/preflightPanel.html

I don't see any explanation here. How is it possible to perform a check when export setting is not known? What is it checking against?
Export settings are not selected on document creation, you don't specify PDF export version anywhere.

[Blake_S]

This explains the generic process of fixing issues, but still don't explain the specific check I created this post about.

When you create a document, PDF export version is not known.

In order to determine that a PDF has a conflict with a chosen export version, you need to know what that version is, and the program shouldn't know that.

So generating this error should not be possible before you initiate Export procedure and select the version there.

 

[walt.farrell]

1 minute ago, Blake_S said:

In order to determine that a PDF has a conflict with a chosen export version, you need to know what that version is, and the program shouldn't know that.

The Preflight Profile you select specifies the PDF output level to check against. Edit the profile and you'll see it, and can change it.

[Blake_S]

5 minutes ago, walt.farrell said:

The Preflight Profile you select specifies the PDF output level to check against. Edit the profile and you'll see it, and can change it.

yes this was indeed the case, although the error message is not entirely clear on what you should change, since it doesn't mention "Compatibility", which is how the setting is called in a preflight profile

[walt.farrell]

1 minute ago, Blake_S said:

yes this was indeed the case, although the error message is not entirely clear on what you should change, since it doesn't mention "Compatibility", which is how the setting is called in a preflight profile

It is the only PDF Passthrough setting, isn't it?

From your topic title the message says your files are not "compatible", and the setting is "compatibility". Seems clear enough, to me.

[Old Bruce]

5 hours ago, Blake_S said:

The PDF export version is not known before you actually initiate the Export and select it,

I am just assuming the following. When you first start up Publisher (and I mean even the very first time after having bought and installed it) there is a PDF (For Print) preset chosen for new documents. After you do set up a different Preset, perhaps an edited version, then that preset is remembered for subsequent documents.

I guess the programmers decided that it would be best to warn you about potential problems with PDFs before you go to export. Even if your intention is to export a PNG instead of a PDF.

[Intuos5]

I'm having the same issues with PDFs set to interpreted (because that allows me to see them as vectors so I can do my tracing more easily than on blurry rasterised versions. To me the burning question left unanswered is what is the difference between interpreted and passthrough? And what are the compatibility issues that the preflight panel warns about? Both pdf 1.6 and 1.7 versions have these compatibility issues in the preflight panel when set to interpreted, but I don't really know what this entails.

[Dan C]

21 hours ago, Intuos5 said:

I'm having the same issues with PDFs set to interpreted (because that allows me to see them as vectors so I can do my tracing more easily than on blurry rasterised versions. To me the burning question left unanswered is what is the difference between interpreted and passthrough? And what are the compatibility issues that the preflight panel warns about? Both pdf 1.6 and 1.7 versions have these compatibility issues in the preflight panel when set to interpreted, but I don't really know what this entails.

Passthrough essentially recreates the document using the information in the PDF, this can be quite heavy, so an alternative "interpret" mode is optional to just show a taster preview of the contents.

Lee

[Intuos5]

But why does interpret mode prompt compatibility issues in preflight then?

[Dan C]

The preview is only for viewing, not for final output.

Lee

[Intuos5]

1 hour ago, LeeThorpe said:

The preview is only for viewing, not for final output.

@LeeThorpe That's weird, because whenever I set a PDF file to passthrough mode, I get this error prompt in the preflight panel:

Whenever I hit fix, it set's the image to interpreted mode. But this doesn't change anything visually (beyond showing the vector PDF as a vector and not as a rasterised version). So if this is a viewing kind of thing, then why does it give these errors?

[ahalladay]

On 12/22/2022 at 3:03 AM, Dan C said:

The preview is only for viewing, not for final output.

Lee

I'm having a problem with this still, when I go to export to PDF, it does passthrough the PDF just fine (vectors, fonts, and all). But, when I print from Publisher, it prints the low resolution rasterized version. If I make a PDF from the print screen (MacOS), it uses the rasterized version, as well. This is a huge hassle, since I typically like to setup my document and print right from Affinity Publisher.

[walt.farrell]

7 hours ago, ahalladay said:

I'm having a problem with this still, when I go to export to PDF, it does passthrough the PDF just fine (vectors, fonts, and all). But, when I print from Publisher, it prints the low resolution rasterized version. If I make a PDF from the print screen (MacOS), it uses the rasterized version, as well. This is a huge hassle, since I typically like to setup my document and print right from Affinity Publisher.

Welcome to the Affinity forums.

Dan C is no longer participating in these forums. If you are having a problem you need to have addressed, you should probably create your own topic, either in Desktop Questions (this forum) or in the macOS Bugs forum, depending on whether you think there's a bug involved. Replying to this old topic is unlikely to get you help.

[Intuos5]

1 hour ago, walt.farrell said:

Dan C is no longer participating in these forums. If you are having a problem you need to have addressed, you should probably create your own topic, either in Desktop Questions (this forum) or in the macOS Bugs forum, depending on whether you think there's a bug involved. Replying to this old topic is unlikely to get you help.

Odd, because it shows Lee in the message signatures. Dan C's messages were more elaborate as well.

If Dan C really left the company, that's a damn shame, one of the best customer support folks I've seen around.

[walt.farrell]

2 hours ago, Intuos5 said:

Odd, because it shows Lee in the message signatures. Dan C's messages were more elaborate as well.

If Dan C really left the company, that's a damn shame, one of the best customer support folks I've seen around.

It is odd that it says Lee, I agree, and I missed that. But Dan really has left, as shown by the "(Ex) Staff" on all his posts.

[Intuos5]

1 minute ago, walt.farrell said:

It is odd that it says Lee, I agree, and I missed that. But Dan really has left, as shown by the "(Ex) Staff" on all his posts.

It's a shame he didn't have a goodbye post honestly.