![]() ![]() Now your Publisher document instead of using a Fill Layer uses a Rectangle which is supported by the PDF format, so this goes out as a CMYK vector object (as the Publisher document is CMYK and not RGB like Photo), however again as the adjustments are enabled, it is getting rasterised as RGB (because the embedded document is RGB) with the background and this is causing the colour difference. Your Photo document contains a 'Fill layer' which again isn't supported by PDF so gets rasterised to RGB, and the embedded photo is also getting rasterised to RGB, as they're both in RGB the colours are the same so no difference appears but when you actually investigate the PDF you will see that the embedded afphoto file is not transparent. With that said I have passed an issue along to development as your object looks like it could retain the transparency when getting rasterised (due to the adjustments), unfortunately I don't have a time frame on when that will be done. If you investigate the resulting PDFs you can see their individual parts and see that happening. The problem is the adjustments are causing the object to get rasterised and it rasterises the background alongside, this means that there isn't any transparency on that object, so the colour mode does come in to play. So again, it's a bug, things are done in the transparency that it should never ever do. But since it works differently in Photo and Publisher, it's clearly a bug.Ī note: transparent is transparent. RGB and CMYK has the "same" transparency, i.e 0%. It could have been a "feature", i.e applying adjustment layers on things below the image, I first thought that Affinity had done so (in contrast to Adobe). If I/you make a merged variant of the image (Affinity Photo image), and switch of the adjustment layers, there is no problem (RGB image). The problem is that the adjustment layer works "through" the transparent onto the page background in Publisher. However I don't know what your exact needs are so that is something you will need to figure out yourself. To get around this depending on your needs you could, in the PDF Export Settings, set Colour Space: RGB and that will force everything to be in RGB on Export and stop the colour conversion happening. I'll pass that over to development to see if that can be done, as not all PDF versions support transparency on images. What would be useful in this situation is if the object was getting rasterised and retaining its transparency. Unfortunately it is also rasterising it with the background colour which is not completely matching because of colour conversions. afphoto is getting rasterised as an RGB image on export to PDF because the source is in RGB. When exporting the Designer document to PDF this text. afphoto file used in both documents is also in RGB/8. I believe the source of the issue here is that your 'Designer' document is actually in CMYK/8 where as the Photo one is in RGB/8. The document you've sent is actually created in Publisher and not Designer (though can be reproduced when opened in Designer). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |