Jim_Tim Posted May 9, 2021 Share Posted May 9, 2021 Hi everyone, I have found previously that Affinity Publisher has struggled (at times) to maintain vector lines when PDF'ing certain drawings when linked into a large document. I've even had it when half a drawing on a sheet has been maintained as vector lines and half of the drawing being rasterised - which is a bit strange. However, recently I have noticed that even in the live document the imported/linked drawings have been rasterised within the document - therefore appearing rasterised even before PDF'ing. Is this a new issue? It's rasterising even the most simple of CAD drawings with no hatches or anything - see below: VECTOR: Linked file in AffPub (RASTERISED): Can anybody shed any light on what is happening here? Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted May 9, 2021 Share Posted May 9, 2021 It would help to have a sample file. 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...
Jim_Tim Posted May 9, 2021 Author Share Posted May 9, 2021 Thanks for replying so promptly Walt 🙂 Please see attached for sample files (I've included the original PDFs that are linked into the document too). SAMPLE EXISTING.pdf SAMPLE PROPOSED.pdf Sample File.afpub Quote Link to comment Share on other sites More sharing options...
Fixx Posted May 10, 2021 Share Posted May 10, 2021 My guess is Publisher is showing a preview for linked PDFs. It exports as proper vector PDF anyway. If you embed it it is editable within Publisher. Maybe this is because PDF passthrough feature? Are all linked PDFs passthrough as a rule? Quote Link to comment Share on other sites More sharing options...
Jim_Tim Posted May 10, 2021 Author Share Posted May 10, 2021 3 hours ago, Fixx said: My guess is Publisher is showing a preview for linked PDFs. It exports as proper vector PDF anyway. If you embed it it is editable within Publisher. Maybe this is because PDF passthrough feature? Are all linked PDFs passthrough as a rule? Ahhh... yes - they were on the 'passthrough' setting - so appeared as rasterised in the live document. Is this feature to help speed up the document when working in it? That's fine either way. Anyway, that has solved that particular issue - so thank you very much for that. What is still happening though - is partial rasterising of drawings after they have been exported to a PDF - see below: It looks like Affinity Publisher rasterises any areas which are near to 'effects' like 'drop shadows' - see below image. However, in the first image there are no trees/drop shadows in the area shown - so why would it rasterise this area? Very strange. Another example here (below). Everything to the left of the red dotted line (drawn in Adobe PDF) looks to be rasterised and everything to the right of the dotted line remains as vectors. It almost looks as though everything to the left of the 'drop shadows' have been rastered. It all seems very inconsistent. I actually don't mind too much about the trees and drop shadows being rasterised - but why is it rasterising the rest of the drawing!? Quote Link to comment Share on other sites More sharing options...
Fixx Posted May 10, 2021 Share Posted May 10, 2021 3 hours ago, Jim_Tim said: I actually don't mind too much about the trees and drop shadows being rasterised - but why is it rasterising the rest of the drawing!? I think it handles the whole drawing as an element and rasterizes it when effect shadow touches it in any part. That has been a problem since transparency effects were introduced in early InDesign. Possibly you can get around that by enclosing effected element to a vector container but it is probably too much hassle.. if it even works. 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.