Jump to content

Broken images on export PDF-X/3 when conversion of color profile is on


Recommended Posts

Hello,

I am trying to export in PDF-X/3:2003, when I check the box to convert the images in the target color profile, the output is broken: the attached image has a diagonal line and it contains the content of two images, while the green grass should go to the top. I have this in almost all the images.

This error happens only if the JPEG Compression is disabled, if I enable it and allow it to be 100, then the problem disappears. It still seems a bug to me. As I would like to have some fine art prints out of this, I would rather leave JPEG compression disabled.

I'm using Affinity Publisher 2.3.1 on Mac OS Sonoma 14.2.1 on M3 processor.

The target color space is CMYK with an ISO Coated ECI 300% icc profile, the source color space is sRGB.

Kind regards,
Bruno

 

PHOTO-2024-02-19-14-28-54.jpg

Edited by Deepo71
Added details
Link to comment
Share on other sites

  • Staff

Welcome to the forums @Deepo71,

There's a known bug with raster elements becoming corrupted when exported to PDF on M1 devices when JPEG compression was set at 98% and having Metal compute enabled. It sounds like you're experiencing a very similar issue on your M3 except that it also occurs when the setting is disabled. I'd suggest disabling Metal Compute (last checkbox) under the app Preferences > Performance and then restarting when prompted to before attempting the export with the JPEG compression setting disabled to confirm if that resolves it.

Link to comment
Share on other sites

Hello Nathan,

Thank you for the workaround and the prompt answer, tried it and it worked fine.

Just as an additional question "there is a known bug" sounds like something that can't be fixed (easily)... is that correct?

Bruno

Edited by Deepo71
Link to comment
Share on other sites

  • Staff

Hi @Deepo71,

Happy to hear that's worked 🙂

On 2/20/2024 at 12:36 PM, Deepo71 said:

Just as an additional question "there is a known bug" sounds like something that can't be fixed (easily)... is that correct?

I wouldn't be able to comment on the feasibility of the bug being fixed as i'm not a developer but the issue is logged for their attention, and hopefully we'll see it resolved in a later version of the apps.

This thread is tagged with the bug ref so the Serif Info bot will automatically reply if there are any updates.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.