Frank Jonen Posted October 6, 2019 Share Posted October 6, 2019 Nested Live Filters render incorrectly. Try it out. They seem to ignore the premultiplied alpha and render against a black background, then multiply the alpha.The destructive versions of the same filters don't do that. Past documents still look a garish mess. Quote Link to comment Share on other sites More sharing options...
Frank Jonen Posted October 6, 2019 Author Share Posted October 6, 2019 Addition: The destructive sharpening filters also don't work anymore on single coloured layers with alpha (it used to be possible to sharpen the alpha). Quote Link to comment Share on other sites More sharing options...
Hanterdro Posted October 6, 2019 Share Posted October 6, 2019 and selective color filter is broken as soon you change a value of the filter. backward compability of affinity is hilarious I don‘t think they are interested in fixing it... Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted October 6, 2019 Share Posted October 6, 2019 2 hours ago, Hanterdro said: and selective color filter is broken as soon you change a value of the filter. What do you mean by broken, for this case? It is possible that the filter works differently in 1.7 than in 1.6, but is interpreted correctly if you simply open an older file. That would provide backward compatibility. However, if you change the filter values, you would be working with the new behavior. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Frank Jonen Posted October 6, 2019 Author Share Posted October 6, 2019 Yeah, I opened older files. Pretty much everything I've ever done in Affinity is now for the birds. Don't even ask about client work. I've lost every client I've ever shipped Affinity files to. Quote Link to comment Share on other sites More sharing options...
Frank Jonen Posted October 6, 2019 Author Share Posted October 6, 2019 BTW… the workaround for not being able to sharpen layers anymore is: Sharpen your layer Get selection from layer (in new layer) Fill selection with white (in new layer below) Fill entire layer with Black merge the two layers Sharpen with the same parameters as before Rasterise to Mask Assign mask to layer you wanted to sharpen previously Nine steps for something that takes 1 click everywhere else. Now that's what I call progress. Quote Link to comment Share on other sites More sharing options...
Hanterdro Posted October 7, 2019 Share Posted October 7, 2019 23 hours ago, walt.farrell said: What do you mean by broken, for this case? It is possible that the filter works differently in 1.7 than in 1.6, but is interpreted correctly if you simply open an older file. That would provide backward compatibility. However, if you change the filter values, you would be working with the new behavior. exactly that‘s the issue. the correct way would be use the old filter for files from 1.6 or convert the values to the new filter. the current solution is just bad Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted October 7, 2019 Share Posted October 7, 2019 1 hour ago, Hanterdro said: exactly that‘s the issue. the correct way would be use the old filter for files from 1.6 or convert the values to the new filter. the current solution is just bad They do use the old filter, until you make a change to it. Then they use the new filter. That seems reasonable to me. What problem does it give you? Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Hanterdro Posted October 7, 2019 Share Posted October 7, 2019 1 minute ago, walt.farrell said: They do use the old filter, until you make a change to it. Then they use the new filter. That seems reasonable to me. What problem does it give you? if you adjust the old filter a little everything is totally off, as soon as you move the slider. practically you can‘t adjust 1.6 files in 1.7 with the color adjustment filter. the reason is the use the new filter with the old values, because they are too lazy to auto convert the values of the old filter to the new one. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted October 9, 2019 Staff Share Posted October 9, 2019 On 10/6/2019 at 6:02 PM, Frank Jonen said: Nested Live Filters render incorrectly. Try it out. They seem to ignore the premultiplied alpha and render against a black background, then multiply the alpha.The destructive versions of the same filters don't do that. Past documents still look a garish mess. Hi @Frank Jonen, Can you attach some sample files? It looks like the Sharpening issue is casued by Metal. With Metal OFF, it all works fine. I've logged this with our developers. Quote Link to comment Share on other sites More sharing options...
Frank Jonen Posted October 9, 2019 Author Share Posted October 9, 2019 13 hours ago, GabrielM said: Hi @Frank Jonen, Can you attach some sample files? It looks like the Sharpening issue is casued by Metal. With Metal OFF, it all works fine. I've logged this with our developers. Just created one for you. Also Metal on or off doesn't make a difference. All rendering options are messed up. Can't we just get version 1.6 with a compatibility mode for 1.7 files until you've sorted this out so the apps are usable again? Affinity Compatibility Errors.afphoto Quote Link to comment Share on other sites More sharing options...
Frank Jonen Posted October 9, 2019 Author Share Posted October 9, 2019 Also this is forced upon me. I don't care for wasting cycles. Don't force options on the users that they do not want. I want Nearest Neighbour filtering, not bilinear!It constantly keeps resetting itself. Very frustrating. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted October 16, 2019 Staff Share Posted October 16, 2019 In your example, you're using a pure white brush. Unsharp mask has never worked on just pure white (or pure black) pixels 1.6 either, so I can't see how it could break any previous documents. As before, if you have any 1.6 documents that were broken by 1.7, attach them and we can have a look Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.