Lukc666

I have a bit of a sub-question - can anyone recommend any software that would reliably convert a whole pdf to a specified color space? Something that I could perhaps bolt onto my Affinity workflow for color management vis-a-vis printers?

Thank you for that detailed breakdown of the process and situation! I appreciate it. I feel like a step-by-step breakdown of this workflow would be incredibly useful in the help / tutorial files and avoid a lot of pain in production.

Hello everyone. Adobe products have a useful PDF export feature, where you can convert the color space of a file while preserving numbers. For example, if you convert from SWOP to Fogra, it will - crucially - ensure that 100K black stays 100K black and doesn't become an unpredictable CMYK rich black. I haven't been able to find anything similar in Affinity Designer (or Affinity Publisher) and would like to know whether this feature exists, if not, whether there is some kind of hacky workaround to replicate it, and - possibly - whether this feature might be on the development roadmap? My workflow to get a sense of where I would have used the feature: I was designing a document for both screen use and physical printing. Since perfect color fidelity was not crucial, I initially set up the file as a generic CMYK and set up a series of global colors. Including 100K black. So far so good, right? For exporting to RGB, it didn't matter that much whether numbers were preserved or not. All fine and dandy. Then comes the printing and the printer requires a specific color space. Fine, I load up the color profile, export ... and the printer comes back to me that they couldn't print it, because it was all rich blacks. I had specifically set up a global 100K black and used that, but on export into the new color space that 100K black was converted to something like 30.40.30.70. This was incredibly frustrating, because I couldn't figure out where things had gone wrong - I hadn't expected the program to convert my 100K into a rich black without letting me know in advance. Let me tell you, it took quite a while before I figured out what was going on. Then I had to change the document color space (not at export) and go "fix" all the blacks manually. This was ... not fun. Thank you for your help and comments folks, —L.

Thank you. I've kept wondering if I was doing something wrong or it was a bug. Good to see it wasn't just me, and elegant "hack-fix".

Oh, yes, with multiple overlapping artboards it won't work. And it has one major flaw: me forgetting to resize at the end! Hah. 😅

A hacky trick I use - and I know it's kind of dumb - is: 1) get very obvious post-it and write message to self: "REDUCE ARTBOARD SIZE BY 5mm* ON EACH SIDE BEFORE OUTPUT!" 2) Resize artboard by 5mm* on each side from the center. 3) Work on artwork with visible bleed. 4) Reduce artboard size by 5mm* on each side from the center. 5) Output. 6) Throw away post-it. *or whatever the bleed is. I'm embarrassed to admit ... but it ... uh ... does the job.

I'm experiencing beachballs when changing styles / moving layers / some other operations in Designer and Publisher V2. I suspect it could be something with how it's rendering UI elements? But I have no clue.

Yeah. If it's not fixed by the time I finish my current project, I'll probably shift back to InDesign for a bit. It's really a pain. Every now and again I also lose trackpad gesture zoom (have to enable manual zoom, zoom in and zoom out, then it usually comes back). They're two little, persistent bugs, that really frustrate my concentration. Same setup as Pete, but 16" MBP.

Mmm, a moderator commented on the issue when I brought it up some months earlier. I didn't have the issue on an Intel mac, but it showed up when I got a new M1 mac.

I've come to check if there's any word on this bug being fixed. For all those struggling with this issue, I suspect it has something to do with the embed / linked file feature. A way I undo the bloat (for a while, until it happens again) is to: 1. open Resource Manager 2. select all files 3. switch them all to embedded 4. then switch them all to linked 5. save your file. Your file size is reduced again. The bloat will return, but this manages it for a while.

I've been told this is a problem with Affinity Publisher on the M1 chipset. With repeated saves, the save file grows huge. I suspect it's some corruption in the way it handles images in the document. Using the resource manager to switch external assets to embedded and back to linked generally fixes the issue - for a while. I've literally just come to the forum to ask if there are any plans to fix this bug. It's getting very annoying.

Update: After using scrubby zoom with zoom tool, the trackpad gesture started working again.

I've also had this happen to me. I've had pinch / spread gesture to zoom in / out regularly stop working on Affinity Publisher, but there turning the scroll and zoom setting in preferences on/off fixed it. However, on Af Designer this time, it didn't work. Restarting the app didn't work either. Chip Apple M1 Pro, 16-inch 2021 MBPro

Ah! Thank you for the clarification — I had thought about doing some local-only disk tests.

I installed Affinity Publisher on a new M1 macbook pro and moved my main work files to icloud to have access from both the new and old machines. File Structure: icloud > project folder > project file (originally c. 7 MB) icloud > project folder > assets > linked image files (total c. 500 MB) Quite soon I noticed that Publisher became very unresponsive and saving a file took a long time. After checking, I saw that the project file was mushrooming with each save. Soon it had grown from around 6 MB to 750 MB plus. Eventually, after some online digging, I tested the following "hack-around" which brought the project file back to its normal size: 1. open resource manager 2. make all (apparently) linked files embedded 3. make all embedded files linked 4. save project file However, the file bloat returns regularly and I have to do the "linked > embedded > linked" trick every few days. Has anyone else come across this bug? Does anyone have any clue what's going on? I suspect some kind of interaction between Publisher and iCloud.