Jump to content
You must now use your email address to sign in [click for more info] ×


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender

Recent Profile Visitors

1,940 profile views
  1. @Hangman Yes, I used your ZIP file from yesterday and tried it. With the files I was able to reproduce it. But if I follow your instructions and do everything exactly like that, I can no longer reproduce it. I think my brain is melting and I need to leave it for a day and then start again. I've made two updates since last time. Once Affinity 2.4.1 and a MacOS update to 14.4.1... I'll try again.
  2. @Hangman, have you tried it with documents and exported files created new from scratch? If I follow your step-by-step instructions, then I can no longer reproduce the result. If I use your "old" files, then I can reproduce it...
  3. Hello @Callum, @Hangman described it in great detail, thank you for that! I just tried again, but I can no longer reproduce the behavior with version 2.4.1. Have you changed anything internally about the color behavior during conversion? @Hangman, can you still reproduce it with 2.4.1?
  4. I tried around for ages, but couldn't for the life of me figure out what was happening. Even according to my understanding of color management, it can only be a bug. Let's wait and see if a team member comments.
  5. Thanks! Maybe someone at Serif can shed some light on this. By the way, would you mind telling me how you make color values appear as bubbles?
  6. Hi @Hangman, thank you for making such an effort. I think I expressed myself too misleadingly. The top test image on the left is an RGB image. From what I understand, after converting the document, Publisher shows me the image as it would look if I had it already CMYK. Or am I thinking wrong? This means that, conversely, the image that has already been converted to CMYK should then look identical to the image at the top left after converting the document. According to my logic, Document Setup > Color > Convert is exactly the same process as in Photo Document > Convert Format / ICC Profile.
  7. Hello @Hangman, Thank you for sharing! I have set PSO Coated v3 as the CMYK profile in my settings because that is the prepress standard for Europe – as far as I know. If I change the default setting to US Web Coated and convert, the problem doesn't actually occur. Even if I leave the default setting on PSO Coated v3, but first convert the publisher document to US Web Coated, the problem does not occur. If you have time, please try to see if you can reproduce it if you change the CMYK profile to PSO Coated v3 in the basic settings. To me, this looks very much like a bug related to the PSO Coated v3 profile. If you need to download the profile: http://www.eci.org/doku.php?id=en:downloads#icc_profiles_from_eci Thanks!!
  8. Hello @Hangman, Thanks for testing. Would it be possible for you to post me a screenshot of your General Affinity Publisher color settings?
  9. Hello, I noticed an inconsistency when converting color spaces. Admittedly, maybe a bit special, but when you stumble across it, it's difficult to understand. A colleague accidentally created a Publisher document that was actually intended for printing with RGB as the color space. The images placed in it were linked RGB images. Not a problem in and of itself, I thought. Then we subsequently converted the document into CMYK. And here, some images suddenly appeared more “saturated” in color than those that had already been converted to CMYK using the same settings. What I've found so far is this: Even if the (conversion) settings in Affinity Photo and Affinity Publisher are identical (relative colorimetric, black point compensation, color-profiles, etc.), the results of the conversion are measurable and visually different. If you place an RGB image in an RGB Publisher document and then convert that document to CMYK, the result for converted image in that document is completely different from if you previously converted the image to CMYK in Photo and then placed it in the converted Publisher document. But actually the result should be the same with the same settings, right? I have attached the example files from the screenshot in case anyone wants to test it. Thanks. Testdokument.afpub Testimage.afphoto
  10. I have a guess as to what might play a role. I've examined the PDFs more closely and sometimes Publisher seems to get confused with Trimbox etc. so that the graphic is there, but Publisher doesn't recognize the coordinates correctly. Not in the picture frame but in the software technical framework of Affinity itself, I don't know how else to describe it...
  11. @Dan C do you perhaps know of another workaround? I noticed other oddities when working in different layouts. When I export a publisher layout where I have not yet zoomed in to force loading, it sometimes happens that the affected graphic is not exported as a vector, but as a rasterized pixel image. If I then simply export the document again, the export in the second file is correct. It has also happened to me twice now that a placed graphic was not exported at all and was missing in print. Has your colleague been able to reproduce this, or has any tips as to whether you need to do anything special in the Synology settings?
  12. Hi, A little thing sometimes drives me crazy. Is there any way to specify in the PDF export dialog that "All Pages" is always selected first? For me, the setting switches back to "Current Page" for reasons I don't understand. It has happened to me a few times that I only sent the current page to a customer instead of all of them. Yes, I know I should actually check it every time, but I find that a little inconvenient. This setting may make sense, but I think that for (my) normal layout work, "All Pages" would make more sense as the default because I use it more often.
  13. Hello, In the current publisher beta, placed Affinity Publisher files with effects (e.g. logos) are fully rasterized when exported. In the current version, however, they are only rasterized where necessary. I used the exact identical export settings and checked the results with callas pdfToolbox. I am attaching sample documents. Can anyone else reproduce this? document.afpub logo.afpub Export Beta.pdf Export Current.pdf
  14. Is there any chance this bug will be fixed? Otherwise, "lock children" has very little use for me, even with the space option which is a really good idea, because I always have to deselect the object and then select it again. Otherwise the box size would no longer be correct.
  • 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.