GeirSol Posted May 22, 2023 Posted May 22, 2023 Hi! I'm creating a book from several pdfs of music score. There was an issue with Affinity not handling ligatures correct on import, so I'm relying on Pdf-passthrough to get correct display. Now I get this warning in the preflight: How do I handle this? Quote
Hangman Posted May 22, 2023 Posted May 22, 2023 Hi @GeirSol, Is the placed PDF a PDF 1.4 file or a different flavour of PDF, e.g., PDF/X-4? First check your preflight settings to ensure the pdf passthrough option matches the pdf version you are exporting to and if it already does then currently the only way to get around this issue without your exported pdf being rasterised and any K100 values being split into CMYK rich black values is to export to pdf using a pdf version equal to or higher than PDF 1.4, e.g., PDF 1.7. GeirSol 1 Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3027 | Affinity Photo Beta 2.6.0.3027 | Affinity Publisher Beta 2.6.0.3027 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
GeirSol Posted May 22, 2023 Author Posted May 22, 2023 3 hours ago, Hangman said: Hi @GeirSol, Is the placed PDF a PDF 1.4 file or a different flavour of PDF, e.g., PDF/X-4? First check your preflight settings to ensure the pdf passthrough option matches the pdf version you are exporting to and if it already does then currently the only way to get around this issue without your exported pdf being rasterised and any K100 values being split into CMYK rich black values is to export to pdf using a pdf version equal to or higher than PDF 1.4, e.g., PDF 1.7. Thanks! My pdfs are output from Sibelius in pdf 1-4 My preflight is set at Pdf/X 1a2003 Hangman 1 Quote
Hangman Posted May 22, 2023 Posted May 22, 2023 Hi @GeirSol, Hopefully, setting your pdf passthrough setting to PDF 1.4 wil have solved your issue... Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3027 | Affinity Photo Beta 2.6.0.3027 | Affinity Publisher Beta 2.6.0.3027 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
GeirSol Posted May 22, 2023 Author Posted May 22, 2023 10 minutes ago, Hangman said: Hi @GeirSol, Hopefully, setting your pdf passthrough setting to PDF 1.4 wil have solved your issue... Ok, do I need to check with my print-house if they're ok with pdf 1-4? Or pdf 1-7? Quote
Hangman Posted May 22, 2023 Posted May 22, 2023 14 minutes ago, GeirSol said: Ok, do I need to check with my print-house if they're ok with pdf 1-4? Was the initial issue of Affinity not handling some of the ligatures correctly down to not having the font loaded on your system e.g., the Lelandia font family or whichever font you used in Sibelius or is it more down to the way Affinity is translating the pdf itself? Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3027 | Affinity Photo Beta 2.6.0.3027 | Affinity Publisher Beta 2.6.0.3027 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
GeirSol Posted May 22, 2023 Author Posted May 22, 2023 1 minute ago, Hangman said: Was the initial issue of Affinity not handling some of the ligatures correctly down to not having the font loaded on your system e.g., the Lelandia font family or whichever font you used in Sibelius or is it more down to the way Affinity is translating the pdf itself? It was Affinity not importing ligatures correct. I have all fonts on my system. Font: Academico Hangman 1 Quote
Recommended Posts
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.