Jump to content

Recommended Posts

Posted

I just tried placing a greyscale image inside a CMYK document but it ends up with a weird overlay/fill effect. If I paste the image in from Affinity Photo it appears normally (though it's probably being converted to full CMYK rather than just K).

Anyone run into this, or just a bug in the current (1.7.0.238) version?

Screen Shot 2019-02-20 at 5.52.38 PM.png

Screen Shot 2019-02-20 at 5.52.55 PM.png

Posted

Ah-ha! Took me a minute to track it down but yes, I found it. And deselecting it renders the image properly—but means it no longer exports as K only. Looks like it's just a rendering glitch in the app—with K selected (as it was by default when I imported the image) it renders incorrectly in the app but exports as it should.

  • Staff
Posted

Hi DesignStationYT,

Could you attach the image you are attaching and an AFPub file that shows this issue please? Just tried a Greyscale JPG I had, but was unable to reproduce it.

Thanks.

  • 2 weeks later...
Posted

I've stripped the file down to just the affected page. Weirdly, I was able to output the PDF without any image issues with previous beta (K only, no appearance glitches), but the most recent 1.7.0.257 now outputs the image as it appears in the screenshot above.

K_Issue.zip

  • Staff
Posted

Thanks for the files. I've recreated that and will get it passed on to development! I did find that using the 257 build that the PDF output was fine - do you have a screenshot of your PDF export settings that give the broken output?

Posted
On 3/12/2019 at 1:16 AM, Sean P said:

Thanks for the files. I've recreated that and will get it passed on to development! I did find that using the 257 build that the PDF output was fine - do you have a screenshot of your PDF export settings that give the broken output?

Yep! PDF result and settings attached here.

Screen Shot 2019-03-14 at 12.53.04 PM.png

Screen Shot 2019-03-14 at 12.53.59 PM.png

  • 2 weeks later...
Posted
On 3/15/2019 at 1:26 AM, AdamW said:

Hi. We have a candidate fix for this now. Could you try again with the next build. 

Confirming that this is fixed in 1.7.0.270. Nice work, and thank you!

×
×
  • 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.