manandmouse

I'd his bug as well. Extremely annoying. Toke me a while to fix. Remove the folder here: /Users/xxxxx/Library/Containers/com.seriflabs.affinitypublisher2/Data/Library/Saved Application State/com.seriflabs.affinitypublisher2.savedState

I also want this. Astute Graphics "simplify" paths is outstanding. We've been using this for vector images drawn with an iPad with a pen. It creates a lot of nodes and have to ve cleaned up. Their's tools is fantastic and I really want this in Affinity Designer. Or Affinity could create better clean up/optimise tools themselves.

Also very curios when updates of the Affinity serie will be released. Any info anyone?

I design and create Publisher documents for my customers. They edit them. We are using Dropbox to share files. Each Dropbox client gets it's own absolut path. Publisher brakes al links when editing the document with another Dropbox client. This is horrible and must be fixed. Most DTP apps have both relative and absolute paths. If the absolute path is "changed", it can use the relative path. This is not rocket science. It's just common sense. If there should be one or the other, relative path should be used. This works in all other DTP apps as I know, i.e InDesign and FrameMaker. Please fix this ASAP.

No. I already explained this. Effects should not work through transparency. You may be right if the problem was intentional. But: then it should be the same in all Affinity apps, and it's not. So it's a bug however you see it. And, as I explained, Photoshop has never done it like this. So no professional could ever be used to such a "feature". It took me a while to figure out this problem. And I'm a problem solver professional, that's one of my roles. Most people may never find this problem at all and maybe end up with leaving Affinity due to bad PDF files. I've already suggested 2 solutions to Affinity. Your "Preserver Alpha" may be a third, but it's better they just fix the bug. Easier for the user.

I already spent a lot of time proving the bug in Publisher. There is no point spending any more time. The bug is there and it can be reproduced.

https://www.flaticon.com

Note that Affinity Publisher may also not start when opening a document. The problem occur if the document has links to images that it have trouble to handle. I had a document on Dropbox. My customer also edited the same document (NOT at the same time of course). My "absolute" link and my customers absolute link to the same image, may be different (as Dropbox is a part of the users folder). It could also be naming issues etc. I can't say exactly wa the problem is, but it has to do with linked images. If I move the images, the document would open and Publisher didn't crash. So there are some "miss handling" and bugs regarding handling of links.

Found the same issue in Designer now. Have the problem got worse since the latest updates? I didn't noticed the problem there before. However, when creating a high res PDF for printing, the problem was in Designer as well. Affinity: This is a very serious problem. It shouldn't be very hard to fix it. If you find it problematic, do as adobe does with Photoshop images: The save a "merged" image automatically. This image is used by other applications. That's an easy workaround. The problem has to be fixed. You are targeting professionals with your apps and we expect your apps to create print-ready PDF's.

Ohh, I'm not annoyed. Far from it. I do express my opinion thou and doesn't agree with many statements. My experience may differ from others. I'm really pleased that Affinity has created Publisher. Affinity have given us all a way to get rid of Adobe. But I do wan't Publisher to work for professionals, that's all. However I've reported other bugs a long time ago that still are there. So... let's hope they get rid of this bug then.

Yes, you may nest the adjustment layers. Again, you can merge all layers into one and switch the other off, as I find much easier. You could probably solve it in some other ways as well, e.g masking etc. It's a workflow issue. Some images may contain 10 layers, and then it's messy to nest things as suggested. I also have customers using Affinity as per my recommendation. I really don't want to explain to them to how get around this bug. It's better for everyone that Affinity remove the bug. It took me a while to figure out this bug. Most users would not find it and will most likely end up with problems. I really want Publisher to be a good competitor to InDesign. As it is now, it's not 100% professional. Still: It's a bug. It hasn't been fixed in 1.9.1. The problem does not occur in Affinity Photo, only in Publisher. The adjustment layers should never work on transparency. It doesn't in any other apps that I know of, and I have used DTP apps since the 90's on several platforms.

Ok. I know. But I clarified that this problem is not related to mixing CMYK and RGB. It's important to start to look for the bug at the right place. I'll say that the bug is that the adjustment layers are "working through" the transparent areas (only in Publisher). As most page backgrounds are white, the bug has probably got unnoticed. A note about same workflow with Photoshop/InDesign: Photoshop actually saves a merged image automatically (default setting, can be changed). This is how I worked around the problem here. I created a merged image and turned off all adjustment layers. My wish is that Publisher will be a perfect competitor to InDesign. Therefore, it can't be bugs like this if you want to reach the professional market. As it is now, I can't trust the PDF export 100% when sending PDF to a Printing House. I've done it, and it works. But I've been working with Desktop Publishing for over 30 years and have handled PDF and PostScript problems over the years and knows what/how to check. However a "normal" user may end up with problems.

Thanks for reporting it. It's a bug however you may try to explain it. It has nothing to do with PreFlight checking unfortunately. It's a bug only appearing in Publisher. - The (switched of) Fill Layer has nothing to do with it. I've attached a screenshot of an image where the fill layer is removed (has no fill layer, but still the same problem) - CMYK/RGB has nothing to do with it either(and it shouldn't as transparency is the "same" for RGB, CMYK, LAB... Transparency is transparency in all color models, it has no "color") - Attached sample where there is RGB in both Publisher and Photo - Attached sample where there is CMYK in Aff Photo "document" and the RGB in the embedded Aff Photo "image": Still no problem in Aff Photo. The reason of reporting this bug is a "Workflow" matter: Using the Affinity Photo image directly in Publisher instead of converting it to i.e PNG, is a great time saver and ensures quality. It's also one of the best Affinity features to be able to work with the Aff Photo image within Publisher. Exporting as PNG disable that feature. I always have a fill layer in my Photo images for workflow reasons, i.e checking that there is a smooth edge agains transparent. I may have different variants of the image etc etc etc. Compared to Adobe Photoshop and InDesign there has never ever been a problem with this. Never ever. I've used this workflow for decades without any issue with Adobe products. This is a bug ONLY in Aff Publisher, not in Add Photo. If there was an issue with turned off fill layer, CMYK, RGB etc as you described, surely it has to be the same for Aff Photo - but it isn't. The bug is very easy to replicate. I shouldn't be forced to "prove" the bug over and over. It's a bug. It's not my documents. It's easy to replicate by anyone. A note: Exporting the PDF from i.e Apple Preview as PNG may get rid of the error/bug. So it is some strange thing happening and there is "faulty" information in the PDF. Sending such a PDF to a Printing House you will never know the result as it depends of the Printing House's RIP.

Please confirm that this bug is going to be fixed.

Sorry, quite right. Publisher it is. Edited. No, the RGB doesn't matter. It has nothing to do with it. The problem is that the adjustment layer works "through" the transparent onto the page background in Publisher. 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). 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). But since it works differently in Photo and Publisher, it's clearly a bug. A note: transparent is transparent. RGB and CMYK has the "same" transparency, i.e 0%. So again, it's a bug, things are done in the transparency that it should never ever do. Merged_transparent_Publisher.zip

Exporting PDF using a placed masked image with adjustment layer, i.e Brightness/Contrast, the adjustment is applied on the Publisher page background. Placing the same image in a Photo document, exporting PDF is just fine. Coming from Photoshop and InDesign, adjustment layers are never done on transparent (i.e going "though" the image and passed on to the Designer background). This issue was a bit tricky to find due to the fact that it has never been an issue in other apps. Zipped file with example files Publisher/Photo and an Image with adjustment layers. I know that there are workarounds, but this bug has to be fixed. Adjustment_layer_on_transparent.zip

This is still a bug. The document background is white, even if I selected transparent. And there is a transparent "halo" around images with transparency, i.e a logo. Affinity has also document problems, i.e bugs, with Affinity Designer. Sometimes, the background is not filled with white. So there seems to be an unstable system for document backgrounds all over. I've reported this issue with screen dumps and all a long time ago. Please: reprogram the background functionality so it works properly. As it is, it's very frustrating.

Today this bug was in Affinity Photo as well. It displayed white background when it was supposted to be transparent. It did display transparent below shadows thou. Seems that it is a generic Affinity apps bug with bakgrdounds not displaying/updating correctly

Would like to see a better Clean up tool, ie as Astute Graphics Vector First Aid. It's extremely useful if the Vector image has been painted with a pen, i.e on an iPad.

Please add a great simplify path tool. Illustrator built-in vector "cleaners" is a start. But if Serif is serious about this, check in Astute Graphics plugins for Illustrator. They are really good. I've been using them. Unfortunately they don't make any plugs for Affinity. https://astutegraphics.com/plugins/vectorscribe

Even a problem with the latest version (1.7.3) of Publisher. It seems that the white background is "fixed" in the View, not on the "page": - When panning/moving the document within the view, the white area is covering different parts of the page. Can't be a very big thing to fix. But it's quite annoying, so please fix asap. Being a developer myself, I would guess that some calculations of the view/page is not correct and surely not updated appropriately. Please see attachments. - The first is after "New document" - The second after pan/moving the page within the view White should be covering everything within the thin border (page)

Not very logical. If so, you should not be able to save a change in a normal document either, i.e to prevent accidental overwriting. No it's just bad design. Adobe started it, and Affinity seems to follow without realising it'a a bad design.

It wasn´t a problem at first. But now, it's all the time. When creating a new document, it's always problem with the page background. On some documents, there is no problem. The problem is the same even if I zoom in/out. I'm running - MacOS 10.14.5 on an 27" iMac. - Graphic card: AMD Radeon R9 M295X 4GB - 2 external monitors at 90° rotation, one on each side of the iMac (total 3 monitors)

Exactly soo. It's the current solution in e.g InDesign (in InDesign all layers are global per default thou). I could see some advantages that keep global and "single page" layers appart. Then it would be master-global-local types of layers. But it's not very important. More important is to have the same layers for all pages. I.e when working with text, you could just disable all the images (to gain speed and focus). When working with multiple languages, it's crucial. You have one layer per language and works with one at a time.

This may be, as I said, a solution for a simple recurring layout. But take a minut to think about it: You have a 200 page catalog in 24 languages. Each page has it's own layout. That means that you must have 24x200 = 4800 master pages! This is not a made up example. I've been involved in productions like this over 30 years in DTP business. Global layers (or document layers) is not a strange thing. It's a very normal and good way to solve many different situations.