Christian Luidolt

Hi @Christian Luidolt,
Thanks for spotting this. Issue logged. 

Hi Christian,

Just to confirm this is something we're aware off as LibraTraining says (thank you!). I will get your comments passed on to development.

Thank you

Same issue/bug discussed here:
In that thread the issue was logged for the developers by a moderator:
So it does appear they are aware of the issue.
 

We've fixed quite a few issues in during the beta cycle, so yours might have just been one of them. I can't see anything in your crash report, as it's crashing in on of your dlls (nothing unexpected). Let us know if you have any more issues while running the beta

I've now had the app crash on my Mac when making edits in that file. Also, at some view magnifications, the blur suddenly is not rendered. I think I'm now seeing the problems you've had with the file, so the problems are not on Windows only.
Here is a file without a Symbol containing the blur, but you'll need to edit the blur independently in each of the two background Master Pages.
template-blur without symbol.afpub
 

 

You wrote about a crash when adding a blur layer to the Assets panel. I suggested you use a Symbol, not an Asset.
Here is your file modified: template-blur with symbol.afpub
 

Here's what seems to be happening:
a Master Page with mode Normal and containing an enabled blur filter is blended as Normal a Master Page with mode Normal and not containing an enabled blur filter is blended as if the mode is Passthrough Besides that anomaly, Passthrough should be a selectable mode, and the default mode, for a Master Page, just as it is for a Symbol or Group or Layer object. I wonder why that's not the case.
Back to the problem at hand: the quickest solution is to move the blur filter outside of the Master Page named SaturationLightness but still keep it inside each of Chapter1Background and Chapter2Background Master Pages. If you want to be able to adjust the blur in one place and have it simultaneously affect every page of the document that contains either Chapter1Background or Chapter2Background, use a Passthrough mode Symbol containing the blur filter.
 

Hi Christian,
You are not quite right (and I've made the same mistake) in describing the unusual behaviour of Passthrough as being the same as Normal when the group contains a mixture of live filter/adjustments and other types of object. True, in that scenario, the live filters/adjustments fail to affect objects below the group; however, the other objects in the group do have their blend mode honoured in blending with objects below the group. If these other objects in the group have Normal blend mode, then yes, Affinity's Passthrough becomes identical to Normal.
To make Passthrough behave the same as in Photoshop, put a page-sized white vector Rectangle or Pixel object with Multiply blend mode (or a black one with Add or Screen blend mode) as the lowest object in the Passthrough group. In Affinity Photo, a Fill object can be used instead of a Rectangle or Pixel object.
 

@walt.farrell
thanks, "grouping" the adjustment layer did the trick (now I hope that the bleed issue will be fixed)

I think this is a variant of an issue we already have logged, so I'll tweak that issue to cover this recipe too.
Thanks for the report, hope you also had a nice easter!

I'm not sure that's a problem with Passthrough specifically, Christian.
In my experience a Master Page that contains only an adjustment layer has no affect on document pages it is applied to, regardless of its blend mode.
You need to Group the adjustment layer, even with itself (select the adjustment layer, Layer > Group), before it will have any effect on the document page contents. Edit: Or, you could put it into a (Layer) layer on the Master Page.
Also, of course, you need to move the Master Page layer above the other layers on the document page

There is a related bug report, by the way:
 

Thanks, I've passed this on.
It seems duplicating doesn't treat it like creating another ToC, which would be the workaround for now

We have made fixes/improvements to this area (Linked documents can be opened as embedded via layers panel) of the program in the latest release.
The fixes and how to update are described in these forum posts.
Affinity Publisher 1.8.3 for Windows         ( Microsoft Store and Affinity Store ) Affinity Publisher 1.8.3 for macOS            ( Mac App Store and Affinity Store ) We would appreciate you checking that this issue has now been resolved for you,

Thank you - is fixed in 1.8.2.620 😀

Apologies for the delay!
It is not intended, it should be doing the same as Edit Document, I've logged this.
Thanks for the letting us know

This should be fixed in 1.8.2, if it's not let me know

The expected behaviour is in 1.8. The line should either be cut at the node, or have a full, sharp corner. 

Change mitre in the Stroke panel at least to 2. To save you some work, you can add the correct frame to the Styles panel and apply the style to the existing frames.

Affinity Publisher 1.8.2.619 Beta solves this performance issue for my document - thanks for fixing 😀
moving, deleting, duplicating, adding pages is done almost immediately

Yes, I can confirm that with a Linked .afphoto file in a Publisher document:
Double-clicking on the file on the page, or using Edit Document, gives a new tab with the .afphoto file name in it. After changes are made in that new tab, File > Save updates the original file. Publisher will notify you that the Linked file has changed, and will automatically update it's preview copy if the Preferences are set for that. This is intended new behavior in 1.8, I believe.
  Double-clicking on the file's thumbnail in the Layers panel treats it as an Embedded file, rather than a Linked file. The new tab says "Embedded" rather than giving the file name. After changes are made, you cannot use File > Save, but must simply close the tab. The changes that were made are saved only locally. This appears to be the way that Linked document files (vs Linked image files) worked in 1.7. I do not think this is intended behavior.

That makes sense

Problem can still be reproduced with Affinity Publisher 1.7.0.221 on other computer running Windows 7 (but it took little longer)

Problem can still be reproduced with Affinity Publisher 1.7.0.221 on Windows 10 (but it took little longer), wil test on Windows 7 on Monday.

Thanks Christian I shall take a look and speak to Jon P also