Affinity Photo 2.1beta Unsharp Mask Artifacts ~ not resolved yet...

[wgb]

Just downloaded 2.1beta and tested my ongoing problem with AF unsharp mask. (Scan small stamp at 6,400dpi, open in AF, straighten, resize to 300dpi without resample, and then filter/unsharp mask at 30,1.8,0.  Still getting the artifacts reported with first version (and all others) of 2.0

Affinity Photo (1.10.6) still works as expected, so I am still using that version.

 

AF 2.1.afphoto

[walt.farrell]

Thanks, but this beta forum is for reporting bugs that are new to the beta, or that were claimed to be fixed but aren't. 

Problems in the retail V2 release need to be discussed in the normal Bugs forum.

Sorry. I see this was listed as a fix in Photo for macOS.

[wgb]

I believe I saw that it was claimed to be fixed...sorry if I misread that.

[walt.farrell]

13 minutes ago, wgb said:

I believe I saw that it was claimed to be fixed...sorry if I misread that.

Or maybe I missed it

Edit: I see it is listed as fixed on macOS. So if that's where you're seeing the problem, thanks for mentioning it. 

Quote

Unsharp mask produces artefacts [Photo]

 

[Chris B]

This is marked as fixed and was closed as so. We've tried on a number of machines since and 3 testers have been unable to reproduce.

The recipe we originally used to reproduce is follows:

1. Open the document
2. Filters > Sharpen > Unsharp mask 
3. Use 100px radius, factor: 4, threshold: 35%
4. Observe it all looks correct
5. Apply it
6. Observe the artefacts now appear

Has this recipe changed? Are you doing anything different?

[wgb]

Hi Chris,

Your formula is basically correct - not exact, but close enough.

At the time of THIS original post, which was for the first beta I was offered, I understood "you" thought the issue was fixed, and for me, it was NOT. This the post.

 

 

However the next beta and this morning's 2.1.0.1713 both seem to be working properly. (I submitted a positive response to the earlier beta.)

So, IMO, The last two Affinity Photo Beta 2.1.XXXXX versions I have tested both seem to have the issue fixed. 

 

I look forward to the next general release and to putting photo 2 to work.

Thanks for all this attention,

 

Bill

[Chris B]

Thanks for the feedback