Bruce Atkinson

Further to this issue. The values in the Info Panel do not change when using other adjustments such as White Balance and Channel Mixer. MAC only.

@Callum This problem with Topaz .dng files still exists in the latest version of Affinity. Photos appear washed out and there are color casts on occasion. Has there been any progress in resolving the issue? Thanks.

Will do. Thanks

On a Mac, when I update from 1.8.6 to 1.9 will my additional (i.e., beyond the defaults) Macros, Brushes and Styles automatically transfer over or will I have to reinstall them all?

I have run into this issue as well and my workaround is, as a final step in Affinity, to select all layers and do a 'Merge Visible' before doing the Save. Once I have done that I get a message at the bottom of the intermediate window that says "Editing Complete (16MB change limit exceeded - document will be flattened) - press Save to keep these changes". When I then press Save, the image saves back into Photos without any error. Based on that, it seems to me that if the "Save" in Affinity was automatically a "Save as Flatten" rather than only a flatten depending on file size, then the error message problem would disappear. Of course, the various layers, etc. disappear as well.

Neofinder does show thumbnails of .afphoto files. And if you want to add keywords it will create .XMP sidecar files as well. It will not add geolocation info though. See https://www.cdfinder.de/guide/17/neofinder_and_photos.html

Thanks MEB, Skylum seems to talk the talk but is pretty slack on walking it. I'm glad you guys appear to be stepping up.

OK, thanks. Too bad. Has there been any interaction at all with Skylum regarding Luminar 4 as a plugin for Affinity?

I'm not sure if anyone is still having problems with this or not but I recently encountered the same issue but only intermittently. It turns out that, as LiamBates indicated, files exceeding the 16 mb limit do get saved properly and consistently. The message that accompanies the notice that the 16mb limit has been exceeded also indicates that as a result, the document has been flattened. That would suggest to me that images <16mb retain the various layers and that Photos can't handle this situation thus resulting in the 'unexpected error'. Increasing the bit depth to 16-bit does increase file size to >16mb so gets around the problem. Another option that works is to do all of the desired editing but as a last step select all of the layers and do a 'merge visible'. This too will result in a file >16mb that will then be flattened then saved OK. Perhaps a permanent solution would be for Serif to simply have the 'Save' work as the 'Save Flattened' option, similar to the Save options when opening a file in Affinity and adding layers.

Is there any update to this issue of getting Luminar 4 to work as a plugin for Affinity? Has there been any action on the sandboxing issue reported by VodkaHindJelly?

Expanded, this is what it all means 100% Radius in Detail Refinement (DR) in the Develop Persona is the equivalent of 5 pixel Radius in Unsharp Mask (UM) in the Photo Persona 100% Amount in Detail Refinement (DR) in the Develop Persona is the equivalent of Factor of 2 in Unsharp Mask (UM) in the Photo Persona

Thank you, this is most helpful!! (And BTW no offence taken)

I have tested but am unsure because of my eyesight

Oops! I forgot to indicate Unsharp Mask in Photo Persona.

I've been trying to better understand Pre- vs Output sharpening (as per Nik Collection RAW Presharpener / Output Sharpener) but using Affinity Photo. In the Develop Persona, Detail Refinement has both Radius and Amount as percents (0-100). On the other hand, in the Photo Persona, Radius is in pixels (0-100) and Factor ranges from 0-4. Two questions: 1) since Radius in both is 1-100 can I assume that e.g., 5% in DP is equivalent to 5 pixels in PP, and 2) can I assume that an Amount of e.g., 25% in DP is equivalent to a Factor of 1 (25% of 4) in PP?