Crolow

What does that mean ? APH ? 🙂

Hi You are right ... I don't know why that tone mapping was so slow for a few minutes. Probably windows updater or antivirus. Speed is again reasonable... Tyank you

I was checking the Affinity performance, and I realized that the process priority is set to normal, so basically it will use as less possible CPU. It should be great that the processor could set the priority of their processes to high. I didn't found something to make this not versatile but this command that you can use in a batch file can help with this : wmic process where name="Photo.exe" CALL setpriority "128" Give a try it seems to me, that the performance of the tone mapping as for example increased dramatically

Well this can be achieved local cache. Actually by default this option is disabled, enabling it makes it behaves globally and you lose complete contron on what's on your files. Doing it on the save functionnality leaves you with the choice to reuse history of not. For sure this way undo date is not portable but , should it be ? You could use the snapshots in order to do that maybe ?

I still don't see the point of saving all the data in the saved file, you need to reapply all the changes back when you load the image into memory. So it is probably useless at that time, certainly if your file ends up 3 times bigger then the original RAW file with only one layer. In the meantime i found some bug in DXO that seems to mess up a bit with TIFF compression with 16 bits format. So was confused when doing some tests related to that file size

OK, i will do some experiments Thanks. But I'm not sure it is counter productive. Loading a huge image is already huge, not sure that uncompression will be a benefit if it takes 200% of the original size 🙂AT least I can not work out an image in 10 seconds, and if it is so I can just use original image and use a LR preset or whatever

I know that NEF file that pixel info is diff on Raw images. But I'm talking about the final outpt as TIFF it is 3 times smaller then the .afPhoto. If know there is any tricks to reduce that size of .afPhotos, I can go with it 🙂

Why it so difficult ? 16 bits with lossless compression images are smaller than 16 bits images without compression (+/- 50%). Export some Affinity photo file to TIFF and convert it into TIFF 16 bits with compression. And you will see the difference. So I didn't said Affinity internal bitmaps were losing pixel information, but it could be saved another way. Maybe there is alternative to TIFF but as it is straight forward, i'm not sure , maybe using another compression algorithm

On the screenshot you can see the .afPhoto size of a NEF file that is around 30MB => 16 bits compressed. The .Tif file is an export of .Affinity to TIF and converted to 16 bits compressed. Which is as well useful if I need to do extra work, as for now I can't translate yet all my tasks frrom Photoshop or DXO in Affinity what is mainly Dust Removal wich seems a pain in Affinity and I still didn't got it to work

When using the Affinity format, it is obvious that we want to get the possibility to edit our files. So there is no need to reduce color information till final export for production. I'm now plundered with photos of 150MB that are coming from NEF files of 30 MB.