ngiuristante Posted October 7, 2024 Posted October 7, 2024 Hello I found some anomaly when exporting PDF from Publisher. Shadows and/or effects are not well rendered and cause these glitches behind the text. They are rasters when I open them in Designer afterward, not just a Quicklook/Preview display bug. Not sure if it's a bug but definitely looks like one: I've tried at least 50 export before finding out what was cause the issue. It disappear when I enable JPG compression. It seems NOT enabling JPG compression causes it in all my test. macOS Sonoma 14.6.1 Publisher 2.5.5 (2636) Like I said, not sure if it's a bug or "by design" but in any case, it's also a heads up for anyone struggling like me.
walt.farrell Posted October 7, 2024 Posted October 7, 2024 Layer effects on vector elements cause rasterization of those vector elements (and elements below them). That is simply the way that Affinity applications work, as far as I know. 1 hour ago, ngiuristante said: They are rasters when I open them in Designer afterward Which are rasters? The elements that had the Layer Effects, or something else (such as the text above them)? -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop 1: Windows 11 Pro 24H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 26.0, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.6.1
Nuclear Ember Posted October 8, 2024 Posted October 8, 2024 Slightly different but related problem. When I export a PDF from Publisher with JPG compression disabled, but use NO effects (FX), I also get image glitches. There are no FX anywhere in this document, yet these and other pages all have image glitches at the top. macOS Sonoma 14.7 Publisher 2.5.5
ngiuristante Posted October 8, 2024 Author Posted October 8, 2024 18 hours ago, walt.farrell said: Layer effects on vector elements cause rasterization of those vector elements (and elements below them). That is simply the way that Affinity applications work, as far as I know. Which are rasters? The elements that had the Layer Effects, or something else (such as the text above them)? Sorry for the lack of clarity. What I mean is, each glitches become several layers of rasters per glitch. I understand FXs on layers must be rasterised as they are not necessarily supported inside a PDF. I thought an export would raster everything on a single layer where supported features would stack above. But anyway... No matter how they are rendered or technically processed, the point is; those are glitches and found it valuable to report it here.
Hangman Posted October 8, 2024 Posted October 8, 2024 Hi @ngiuristante, Could you do a File > Save as Package, Save to a new empty folder, then zip the contents of the folder and upload the zip file so we can take a look... There is a known issue relating to PDF export when certain elements appear inside a group which sounds like what you may be experiencing here but we will be able to confirm whether that is the cause by testing the file... Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 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
Nuclear Ember Posted October 8, 2024 Posted October 8, 2024 (edited) Never mind, I thought you were talking to me. Edited October 8, 2024 by Nuclear Ember
Hangman Posted October 8, 2024 Posted October 8, 2024 Just now, Nuclear Ember said: Happy to. But where to upload? Will it be available to everyone on the forum? Feel free to DM it to me if you'd rather not upload it publicly to the forum... Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 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
Hangman Posted October 8, 2024 Posted October 8, 2024 Hi @Nuclear Ember, If you turn Hardware Acceleration off under Publisher's Performance Settings which will require you to reboot Publisher and then export your file to PDF using the same settings does that remove the glitches you see at the top of the images... I think you replied to my reply to @ngiuristante which relates to a different issue... Turning Hardware Acceleration off should I believe resolve your specific problem but let us know if it doesn't... Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 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
Nuclear Ember Posted October 8, 2024 Posted October 8, 2024 7 minutes ago, Hangman said: Hi @Nuclear Ember, If you turn Hardware Acceleration off under Publisher's Performance Settings which will require you to reboot Publisher and then export your file to PDF using the same settings does that remove the glitches you see at the top of the images... Yes, that helped, thanks. Also, I hope you saw my corrected post above. I mistakenly thought you were talking to me (about sending a zipped file).
Hangman Posted October 8, 2024 Posted October 8, 2024 19 minutes ago, Nuclear Ember said: Yes, that helped, thanks. Good to hear that resolved the issue... 20 minutes ago, Nuclear Ember said: Also, I hope you saw my corrected post above. I mistakenly thought you were talking to me (about sending a zipped file). No worries at all, easily done... Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 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
ngiuristante Posted October 8, 2024 Author Posted October 8, 2024 @Hangman Here is a package of the one pager I'm working on. AspectNGCOAOnePager-ca-en-v1.0.1.zip
Hangman Posted October 8, 2024 Posted October 8, 2024 Hi @ngiuristante, Many thanks for the file... The bug is a direct result of the Picture Frames... I've removed the Picture Frames from the ten images in the attached Publisher file. When the file is exported with Allow JPEG Compression unchecked the glitches are no longer present... This is definitely a bug... I have a feeling it may already be logged but I'm not 100% sure... If you export the Attached Publisher file with JPEG Compression unchecked you should find the glitches are not longer there but let us know... Publisher File Without Picture Frames AspectNGCOAOnePager (No Picture Frames).afpub PDF Exports With and Without Picture Frames AspectNGCOAOnePager (With Picture Frames).pdf. AspectNGCOAOnePager (Without Picture Frames).pdf Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 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
ngiuristante Posted October 9, 2024 Author Posted October 9, 2024 Interesting find @Hangman and thanks for your time! I really thought the problem was only related to the exportation. I would not have guess that a type of shape/mask would cause issue. I'm not too familiar with these forums. Do you know if Affinity monitors these forums for bug report or should I write to them on another channel? Cheers!
Hangman Posted October 9, 2024 Posted October 9, 2024 Hi @ngiuristante, It's really a combination of things, the bug is effectively exporting a file containing images placed in Picture Frames to PDF when Allow JPEG Compression is unchecked causing artefacts to appear on the images in the exported file... Yes, these forums are monitored by the staff at Serif and a member of their team will pick this post up at some point and then log this as a bug if it's not already logged, so your post is already in the correct place... Once logged the thread should be tagged with a bug reference which will appear below the main title of the thread... This should then get passed to the Development Team to be fixed however there are no guarantees as to when a fix will be forthcoming... There should be no need to uncheck Allow JPEG Compression so the advice would be to keep your artwork as you have it, i.e., with the images in Picture frames and keep Allow JPEG Compression checked when exporting the file to PDF... Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 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
Staff Lee D Posted October 11, 2024 Staff Posted October 11, 2024 @ngiuristante We are aware of an issue that relates to raster corruption on PDF export on an "M' based system. If JPEG compression is enabled on the PDF export options as well as Hardware Acceleration within the apps Settings. Can you confirm if your system is 'M' based as I can then update the existing report. Hangman and ngiuristante 2
Hangman Posted October 11, 2024 Posted October 11, 2024 Hi @Lee D, With the sample file, the raster corruption happens when JPEG compression is unchecked rather than checked and appears to relate specifically to images inside Picture Frames. Is this part of the same bug you have logged? Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 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
Staff Lee D Posted October 11, 2024 Staff Posted October 11, 2024 @Hangman Opening the package file and exporting to PDF (for export) unchecking JPEG compression. Then opening the PDF in Apple Preview or Adobe Acrobat I'm not seeing any visual corruption as long as Hardware Acceleration is disabled. If I enable Hardware Acceleration and export using the same settings, I do get the visual issues on an M based system. The report we have logged that shows the same type of corruption doesn't have any reference to Picture Frames, just M based with H/A enabled. Screen Recording 2024-10-11 at 14.59.44.mp4 ngiuristante 1
Hangman Posted October 11, 2024 Posted October 11, 2024 Hi @Lee D, There is a second scenario which appears to relate to whether or not the images sit inside a picture frame... 1 hour ago, Lee D said: If I enable Hardware Acceleration and export using the same settings, I do get the visual issues on an M based system. If you enable Hardware Acceleration but remove the images from their picture frames and instead crop them then exporting either with or without 'Allow JPEG Compression' will also export the files without artefacts on an M system... i.e., with Hardware Acceleration enabled, 'Allow JPEG Compression' on or off, if the image isn't sitting inside a Picture Frame it will also export without artefacts so it seems to be more than just disabling Hardware Acceleration... This was my reason for querying whether Picture Frames play a part in the bug report... Eight PDF Exports PF = Picture Frame HA = Hardware Acceleration AJC = Allow JPEG Compression Aspect PF No | HA On | AJC Off.pdf - Result = No Artefacts - Aspect PF No | HA On | AJC Off.pdf Aspect PF No | HA On | AJC On.pdf - Result = No Artefacts - Aspect PF No | HA On | AJC On.pdf Aspect PF Yes | HA On | AJC Off.pdf - Result = Artefacts - Aspect PF Yes | HA On | AJC Off.pdf Aspect PF Yes | HA On | AJC On.pdf - Result = No Artefacts - Aspect PF Yes | HA On | AJC On.pdf Aspect PF No | HA Off | AJC Off.pdf - Result = No Artefacts - Aspect PF No | HA Off | AJC Off.pdf Aspect PF No | HA Off | AJC On.pdf - Result = No Artefacts - Aspect PF No | HA Off | AJC On.pdf Aspect PF Yes | HA Off | AJC Off.pdf - Result = No Artefacts - Aspect PF Yes | HA Off | AJC Off.pdf Aspect PF Yes | HA Off | AJC On.pdf - Result = No Artefacts - Aspect PF Yes | HA Off | AJC On.pdf Publisher File with Images Not Inside Picture Frames AspectNGCOAOnePager (No Picture Frames).afpub Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 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
jtbandes Posted December 19, 2024 Posted December 19, 2024 @Lee D I can verify that on a M1 system with macOS 15.1.1 and Affinity Publisher 2.5.7 (HA enabled), I see the following bug (which appears to be the same reported by @ngiuristante in the original post): Steps: Create a new document (default Letter template) Add a rectangle for background contrast Add some Artistic Text on top of the rectangle Add an Outer Shadow effect to the text Choose File > Export…, choose "PDF (for print)", and then uncheck "Allow JPEG compression". Export the file. You will see corrupted image output where the outer shadow effect was rasterized. The corruption is non-deterministic. If I run the same Export step a few times, I see different results: Untitled.pdfUntitled2.pdf If "Allow JPEG compression" is enabled, even if the Quality is set to 100, the corruption is gone: Untitled3.pdf
Hangman Posted December 19, 2024 Posted December 19, 2024 Hi @jtbandes, There are three factors at play here: Whether Hardware Acceleration is On or Off Whether the export Colour Space is RGB of CMYK The size of the graphic The bug affects all PDF export presets that export using a CMYK colour space when Hardware Acceleration is enabled. The bug is logged under AF-2072 and is currently awaiting a fix... I have attached four versions of the file: two using an RGB Colour Space and two using a CMYK Colour Space. One version has Hardware Acceleration enabled, and one has it disabled. Hello PDF(for print) RGB HA Off.pdf Hello PDF(for print) RGB HA On.pdf Hello PDF(for print) CMYK HA Off.pdf Hello PDF(for print) CMYK HA On.pdf Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 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
thadeusz Posted January 7 Posted January 7 Thanks for pointing out the JPG-compression workaround. Fixed it for me for the moment. Problem is also present in greyscale documents with all being set correctly to grey scale images. It's a total mess on export, glitches all over...
ngiuristante Posted January 7 Author Posted January 7 Sorry for the late reply everyone. Per your last posts, I'm glad this is not a stale case. I'm also glad there's the JPEG compression ON workaround. @Lee D I am indeed on Apple M2 Max with hardware acceleration ON. It has always remained active during all my exports. This setting is ON by default if I'm not mistaken. Let me know if I can still be of any help.
Recommended Posts