XzavieR

I have found that Affinity Photo, both stable (1.8.5) and current beta (1.9.0), can not process RW2 files from Panasonic Lumix DMC-FZ80/82 with lens correction. The RW2 files produced by this and many other Panasonic cameras contain a built-in lens correction profile for fixing distortion and chromatic aberration. The only programs I have found that are able to use this information is Adobe Lightroom (and related Adobe products like ACR) and SilkyPix, both of which do not seem to have any pre-made profiles for this camera but rather uses the parameters from the lens correction metadata to create a correction on the fly (Adobe Lightroom in particular specifically tells me this when doing lens correction on the file). In my testing of Affinity Photo's processing of these files, I have found that choosing the "Panasonic Lumix DMC-FZ45 and compatibles" profile manually, as suggested by some for mostly any Lumix FZ model does not yield a satisfactory result, with very visible distortion remaining whichever way I tweak the correction, and doing a completely manual correction also leaves a lot of visible distortion that doesn't seem to be possible to accurately compensate for without using the specific correction data embedded in the RW2 file EXIF metadata. I've found a page that details this metadata and how it is most likely used by the programs that can use it: https://syscall.eu/#pana Some other manufacturers beside Panasonic, such as Sony, also embed lens correction profiles in their RAW files these days, so having Affinity support embedded profiles would probably be a very useful improvement and would lessen the dependence on the Lensfun library.

Another user posted an example a few years back showing how DNG files created by CHDK exhibit a large amount of dead/bad/stuck pixels when developed in Affinity Photo (as opposed to in-camera conversion or developing in Lightroom/ACR). As I have a number of such files from my CHDK camera, I tried it out with the current version 1.8.x and the issue still exists. As far as I've found, support for the full DNG 1.3 specification is rare and a few years back only Adobe products could handle these files correctly. These days at least RawTherapee seems to handle these files correctly as well (it used to require applying a dead pixel filter which guessed the location of bad pixels, but doesn't anymore, these files are now developed correctly without adding the dead pixel filter). As Affinity Photo supports lens distortion correction for many CHDK cameras, it would be very nice to have support for the "badpixel opcodes" as well.

In no particular order: Bug fixes Develop persona: Batch processing and non-destructive RAW development (sidecar files) Develop persona: Eyedropper for white balance Develop persona: Support for CHDK DNG opcodes / dead pixel interpolation Develop persona: Wider parameter range for adjustments that are limited to 25% or 50% today (saturation, for example) Develop persona: Better support for OnePlus DNG files (currently they always get a green tint and almost no saturation whatsoever - Lightroom handles them correctly in these regards) and other RAW/DNG files that have similar problems in Affinity today Photo persona: Numeric parameters in Curves Photo persona: Eyedroppers for whitepoint, blackpoint and graypoint in Levels and Curves Photo persona: Numeric parameters in auto adjustments (auto color, auto contrast, auto levels etc) Photo persona: Both Fill and Opacity parameters like in Photoshop, especially for "special" blend modes like Hard Mix - and fix the wording in the Layer Effects window that says "Fill opacity" - it's just regular opacity, same as the one in the layers list. Photo and Develop persona: Crop tool extended with "Crop to bounds" and "Crop to opaque" like in Panorama mode Any slider, particularly in Develop and Tonemapping personas: Doubleclick to reset slider to zero/default.

First off, apologies for gravedigging this thread, but I hope I have something useful to add. I also run CHDK in my Canon compacts, and I'm very happy with it. I was also happily surprised to see that Affinity has support for lens correction for many CHDK cameras out of the box, something which Adobe Lightroom and Photoshop does not. I have also seen the black pixel problem on many of my CHDK DNGs when processed in Affinity, but I don't see the same problem when processing the same files in Lightroom. I'm not sure if this issue would occur on a Mac as well, where Affinity can use Apple's RAW processing. If CHDK is set to save DNG version 1.3 files, all bad pixels will be saved with a value of 0, and a DNG opcode will tell compatible software that a value of 0 is to be considered "bad". This saves some processing in the camera and makes saving DNGs faster (and you don't need to create a badpixel.bin map), since CHDK doesn't have to do anything with bad pixels except mark them as bad. Compatible raw processing software will interpolate these bad pixels from surrounding good pixels to obtain an approximate value. Affinity apparently does not (yet) support these opcodes so it doesn't know that it should interpolate the value of these pixels. It just uses the raw value from the DNG file without question, hence the black pixels. You can work around this by setting CHDK to save DNG version 1.1 files instead. This makes CHDK not use DNG opcodes, but you need to generate a badpixel.bin to use as a map of bad pixels. This might take a few attempts. With this setting, the value of any bad pixel will be interpolated by CHDK in-camera while saving the DNG. So it takes more time to save a DNG, but it won't have the black pixel problem. Hope this helps. And I also hope that Affinity will add support for interpolating bad pixels according to DNG opcodes in the future.

Maybe it'd be nice if the dropdown said "LibRaw" for clarity. Oh well.. Also, color interpretation for my OP5 files looks more balanced in the latest beta. So, thanks to the developers for that.

Well, Affinity Photo does call it the "Serif Labs Raw Engine" in the preferences, so I wasn't aware until this thread that it was based on LibRaw. But darktable uses LibRaw as well and gets the white balance right on these files when using the same WB setting ("as shot"/"camera").

Thanks, great. I tried it out with some of my own OP5 DNGs and for most of them I have to adjust both temperature and tint (mostly around 40-50% towards magenta) to get close to an OK white balance for further work outside the Develop Persona. EDIT: If you want to compare results with another editor that uses libraw for development, look at darktable. Without any adjustments, it gives me results that have a fairly neutral white balance. To be fair, I have to mention that other than the Serif RAW engine, I'm happy with where Affinity Photo is going so far.

Hi Chris, I guess Photography Blog blocks hotlinking. Here's the article with links to the samples: https://www.photographyblog.com/previews/oneplus_5_photos The photos are ordered from left to right, top to bottom, and organized into JPEG and RAW sections, so the specific files shouldn't be too difficult to find. If you use libraw, that might explain it, found this thread on the libraw forums: https://www.libraw.org/node/2334 If you look into this I'd be very interested in the results.

I was excited to see that the OnePlus A5000 (aka OnePlus 5) has been added to the Affinity RAW engine in 1.7. However I can't really see a difference between how the engine interprets the images now compared to before, when it was not officially supported. The images still come out extremely flat and heavily tinted some towards green and some towards magenta, and the Affinity RAW engine doesn't seem to agree with other RAW processors like Lightroom or RawTherapee on the white balance of the images. Even if I enter the same values for temperature, the results in Affinity doesn't reflect the results in Lightroom or RawTherapee. I'm not sure what's going wrong here, as I've also tested DNGs out of a Nexus 5 and had no issues whatsoever with them in either editor, while the OnePlus DNGs come out rather differently across these three programs. To see what I mean, here are two example images from PhotographyBlog, it's the same image but the first is a DNG and the second is the out-of-camera JPEG of the same image. https://img.photographyblog.com/reviews/oneplus_5/photos/oneplus_5_15.dng https://img.photographyblog.com/reviews/oneplus_5/photos/oneplus_5_48.jpg Another pair of DNG/JPEG images for comparison: https://img.photographyblog.com/reviews/oneplus_5/photos/oneplus_5_01.dng https://img.photographyblog.com/reviews/oneplus_5/photos/oneplus_5_27.jpg I'd be interested in hearing the Affinity teams thoughts on this.