Saijin_Naib

Zooming in all the way to max is fine. Panning while zoomed is fine. Zooming out all the way, however, will result in an instant crash. EDIT: This appears to be a regression, as this behavior is not present in v1.6.5.123, with min zoom stopping at 0.1% gracefully. 2018-12-17 16-54-58.mp4

Saturation is still broken in .209 when developing RAW in 32bit HDR.

Perhaps you missed that this is an extant issue with the RAW engine that predates the beta and that I am keeping a consolidated log of changes in processing behavior in this single thread while referencing it in the appropriate Beta forum. I hope it isn't split as the ability to easily compare rendering across the various engines and versions will become more difficult.

Thanks! A lot of people ask if she is Russian Blue, but we think she's just an imposter. She's a shelter rescue and her sister was full black like a Bombay.

Went from this in v1.6 stable: To this in v.17 betas (188): An obvious improvement, and now this means I can likely migrate my wife off of Adobe to Affinity. The XC15-45mmF3.5-5.6 OIS PZ doesn't have a lens profile in Affinity, but that isn't on you as there isn't even one in the LensFun development library yet. Thanks!

All Assistant functions turned off, 32bit HDR as before. Shadow detail is recovered better, color is slightly more accurate and now the X-S1 Lens Profile is applied properly, but clipping is still a massive problem. The image appears to be unchanged from the Beta 184 rendering.

I hope I don't come off disparaging or too critical. I'm hugely fond of Affinity, but it just doesn't work with my RAWs well yet. I hope you can get things worked out, not only for my sensor, but for all RAWs. thanks for your work!

2018-09-30 01.22.55 [X-S1].7z I know this file is a particularly difficult sample, but I've been watching your journey to improve such files since the 1.5 release and beyond, and I'd like to see the RAW processing engine handle things like this better before 1.7x launch, if possible. I've collected a number of comparison images across other engines in this thread below: Summary: Affinity Photo does worse than most every other RAW processing engine I've tested, though I've seen improvements from v1.6 stable to v1.7 beta, though they're not drastic. However, the proper application of the Lens Profile is most welcome and appreciated.

Same here in 32bit HDR, assistant turned off except for Lens Profile, against ANY RAW/RAF file I use.

Affinity Photo Beta for Windows 1.7.0.184 (RAW Develop) All Assistant functions turned off, 32bit HDR as before. Shadow detail is recovered better, color is slightly more accurate and now the X-S1 Lens Profile is applied properly, but clipping is still a massive problem. The image appears to be unchanged from the Beta 178 rendering.

I have similar observations. I support your request.

Fuji EXR RAFs are still not supported properly at all (multiple subframes), and there is still the massive color gamut issue which has been present in Affinity Photo as far as I have used it. There has been the slightest improvement in color rendition and a bit of an improvement in shadow detail retention and now the X-S1 Lens Profile is applied properly, but overall, it still clips severely and the color is completely wrong.

The slightest of improvements in color and shadow detail rendition, and now the X-S1 Lens Profile is applied properly. Clipping is still a massive problem, and it is still far from ideal/usable.

Affinity Photo Beta for Windows 1.7.0.178 (RAW Develop) All Assistant functions turned off, 32bit HDR as before. Shadow detail is recovered better, color is slightly more accurate and now the X-S1 Lens Profile is applied properly, but clipping is still a massive problem.

You can register Affinity Photo to have an App Execution Alias, which will allow command line operations to be done against it with ease. A few "core" MS apps support this already, and a number of other released apps do as well. I can't find the documentation at present, but I believe it is only a modification to the app's manifest file to accomplish this. Big gain for a small investment from you, Serif. Here's an example:

I'm a Fuji-X Shooter as well, though I'm using the even more esoteric EXR sensor with dual-subframes, which Affinity to date has not supported terribly well. I'm hopeful that the latest beta addresses any number of these shortcomings, but currently, I use Fuji RFC to do all my developing and then dump into Affinity for further compositing or editing. I tried CaptureOne Fuji edition, but found it lacking in comparison to Fuji RFC when it came to color/brightness accuracy. I also tested every free RAW developer I could find, and found them all to handle the EXR RAFs with varying levels of inadequacy. Bayer images from my wife's X-A1 did not suffer any issues with any of the other engines I tested, including Affinity.

Agreed with all of the above.

I'd love this as well

I agree that more actions should be able to be taken during the develop, such as multiple successive passes at Chromatic Aberration removal, or Defringing, with the SAME ability to set color/sensitivty/etc that we can with the filter once developed. Swapping channels/etc should also be possible prior to developing.

I use PC/MS Store version. Will these be following the 1.7 beta shortly?

Yeah, and some older cameras from Fuji and others would develop parts of the sensor differently to expand dynamic range, etc. I have an X-S1 which does that. The Serif RAW engine is abysmal at processing my RAFs.

Yeah, I was looking to drop our Adobe CC subscription for my wife to put her on Affinity, but it still doesn't support the Fuji X-A5 or the lens she has, so it's entirely worthless. My 6-year old X-S1 doesn't even have the LensFun profile applied properly, though one exists in the development version of the LensFun library. By default, libRAW/dcRAW and LensFun should be updated with each and every point release, especially since the Store versions of the app can not have these libraries manually updated.

It'd be great if the Serif RAW engine worked properly with RAW files that had multiple sub-frames as well as offering differing demosaic algorithms. I'm in firm support of your request.

RAW/RAF attached to this post for testing. 2018-09-30 01.22.55 [X-S1].7z

Here are examples from other RAW processing engines to compare to. Not all fared well, and as noted above, only RFC rendered it correctly. DarkTable clipped a bit, visually similar to the RAW import on Affinity Photo. CaptureOne rendered the left side of the ring brighter, as it should have been, but the color was completely wrong. SilkyPix nailed the color, brightness, everything. Except the processing defaults make the image look like mush due to the excessive smoothing. LightZone: RawTherapee: DarkTable: CaptureOne v11 (Fuji Edition): RAW File Converter 3.x (SilkyPix 8.x):