Damasta

So, .Net 5 was released with native ARM64 support and performance optimizations for ARM architecture: ARM64 Performance in .NET 5 | .NET Blog (microsoft.com) Does this mean we can expect Affinity Photo on Windows 10 ARM64 soon?

I've used SD835 and SD850 based devices for a year now and can say both articles are misleading. If you expect core i7 performance on those - of course you'll be disappointed. But the SD850 user experience can pretty well keep up with a core i3. In fact, my previously favorite photo post-production tool Capture NX2 runs almost as fast on my SD835 as it does on my core i7 gen 8. This is not an idle statement, I've used the software extensively on both platforms. My new Surface Pro X (based on Snapdragon 8cx) is probably the most responsive and productive mobile device I've ever had and is my new daily driver. Also, Adobe is working with Microsoft on bringing a bunch of products to the the native 64bit ARM world. (It'd be a shame if Adobe were my only option on this new platform . Check how Adobe works on the Pro X: Especially considering how easy recompiling is: https://docs.microsoft.com/en-us/windows/arm/ ... can you afford to NOT support the Platform? Thanks!

Agreed. My new Surface Pro X (based on Snapdragon 8cx) is amazing. and will become my new daily driver. Also, Adobe is working on bringing a bunch of products to the the native 64bit ARM world: Thanks!

You might want to rethink this. My new Surface Pro X is extremely powerful. Microsoft is working with Adobe to bring native 64bit ARM support to the platform - It'd be a shame if they were the only alternative I have. Besides: Adobe is already working on bringing their products to 64 bit ARM: Check the rest of the Pro X, too. Color calibrated panels, Surface Dial support, and a pen with 4096 pressure points and true artistic qualities. It is a mobile creator's dream! Can you afford to NOT support these awesome new devices? Thanks

Thanks for reproducing this, John. It admittedly looks better, but tbh still has a noticeable halo. Here is output from Capture NX2. No noticeable halo IMHO. (forum won't let me upload certain jpgs right now, so here is a tif and a screenshot) I acknowledge Affinity's tone mapping looks more vivid, sunny and "alive" than D-Lighting - which is why I'd love to use it going forward. (I could prob tweak Capture NX2 to look sunnier, but then the workflow gets.... long). In any case, I still don't know WHY the halo is happening, much less how to avoid it. DSC_7357-small.tif

sure, here it is. DSC_7357.NEF

OK, found I had "apply tone curve" set in the Develop Assistant. Turned it off ("take no action") and the result is better, but still shows a strong halo:

Hi all, I'm a Nikon Capture NX2 user who finally decided to look for an alternative since Capture NX2 was discontinued a while ago. AP has been on my watch list for some time, so I thought I'd give it a try. One of the things Capture NX2 was excellent at is "D-Lighting". A Nikon feature that automatically detects shadows and brightens and enhances them, creating very pleasing pseudo-HDR photos with very little effort. It is super easy to use - just three clicks in the regular workflow. Naturally I tried to put AP to the test, and followed the great tutorial here: https://affinity.serif.com/en-us/tutorials/photo/desktop/video/341759551 "HDR from one photo". Here's the thing: the results are eye-popping... except for around sharp, high-contrast edges, where AP will introduce intense halos next to dark edges. These halos ruin the experience IMHO. Please see the difference between Capture NX2 D-Lighting and AP Tone-Mapping, especially right around the edge of the mountain side. How do I eliminate those halos?