benwiggy Posted May 23, 2021 Share Posted May 23, 2021 If I load a PDF that is not PDF/X compliant (but otherwise a perfectly 'normal' and valid PDF for printing) as a "Pass-through" onto a page, and then Export the page as a PDF, I get a Preflight warning that the PDF version is "not compatible with the export version" and "the PDF will be rasterized". Firstly, this seems to depend on the Preflight profile, whose default is for PDF/X-3 PDFs -- regardless of the PDF Export Profile's "Compatibility" setting for PDF versions. Secondly, the PDF does not, in fact, get rasterized. Thirdly, it claims the PDF is version 1.7, when in fact, it's actually 1.4. Or does it mean the intended version of the exported PDF? It's not clear. Fourthly, l can't remember InDesign ever complaining about PDF versions in this way: it would just create a PDF/X-3 PDF, regardless of the 'image' PDFs' versioning. Transparency might get rasterized, but that's slightly different from "This PDF will be rasterized". Is this another quirk of Affinity's bizarre approach to handling PDFs, or just a bad UI, or something else? The warning seems to be incorrect, inappropriate, and lacking in detail. Robby Poole 1 Quote Link to comment Share on other sites More sharing options...
benwiggy Posted May 24, 2021 Author Share Posted May 24, 2021 I see it's been mentioned before, here: The Preflight Profile should automatically match the requirements of the Export Preset. Having a default that throws out false warnings is 'not ideal'. Quote Link to comment Share on other sites More sharing options...
Staff Callum Posted May 25, 2021 Staff Share Posted May 25, 2021 Hi BenWiggy, Welcome to the forums As far as I'm aware this behaviour is logged as a bug it should hopefully be fixed soon. Thanks C benwiggy 1 Quote Please tag me using @ in your reply so I can be sure to respond ASAP. Link to comment Share on other sites More sharing options...
walt.farrell Posted May 26, 2021 Share Posted May 26, 2021 On 5/25/2021 at 6:04 AM, Callum said: As far as I'm aware this behaviour is logged as a bug it should hopefully be fixed soon. On 5/24/2021 at 2:58 AM, benwiggy said: The Preflight Profile should automatically match the requirements of the Export Preset. I'm curious what behavior it is that is logged as a bug. Because, it seems to me, that in the general case Preflight cannot know what is going to happen during Export because it is happening before the user has a chance to set the export options. Therefore the only general solution is for the user to first set the Preflight options to match what they will eventually set for Export. In other words, Preflight cannot "automatically match the requirements of the Export Preset" because Preflight happens before the Export options have been set. (At least, for the first time that the file is exported. Once the file has been exported once, those options could be applied to Preflight for any future Exports (though depending on what the user specifies during those future Exports there could still be a mismatch). Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
benwiggy Posted May 27, 2021 Author Share Posted May 27, 2021 A fair point, @walt.farrell. But there remain problems -- and yet again, they're all about imported PDFs. Quote Link to comment Share on other sites More sharing options...
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.