feuerfloh

Ok, different people, different workflows ;) Let me explain, why this is an issue for *me*. I'm a Lightroom user. And I use Photoshop (for now) only to do things like soft proof that don't work well (or don't work at all in LR for CMYK profiles) in LR. And as LR user, I import the raw files from the camera (they have an original size of ~20MB ... 30MB) into the LR catalogue, let LR convert them into DNG format and then I can do what I want in LR (including virtual copies) - the files size doesn't increase (or if then by 4 kilo(!)Bytes). And - of course - the master file is *alaways* the DNG (i.e. RAW) together with its development settings file from which I can produce smaller JPEGs for my photo blog, yet smaller JPEGs to send it by WhatsApp, sometimes full sized TIFFs or JPEGs to produce a print. These JPEG/TIFF files are then deleted, if the print has been ordered... In addition, I can create different development paths (color and b/w, for example) from the same photo. The required additional file size: 0..4k(!)Bytes. So I have to backup the LR catalogue and the DNG files. That's all. Nothing more, nothing less. If you zip the catalogue (which does LR automatically on a weekly basis), then it shrinks to ~10% of the original size, so that is not an issue. The target of these weekly catalogue backups is my Google drive, so I don't have to care about external disks etc. In the last three years I produces about 2500 photos per year. 2500 * 30 MB = 75GB/year. That is easy to handle, including backups "in the cloud". If the file size is increased by factor 10..20 then it would be a challenge to get enough "cloud space" - I have "only" 1TB... But there's another problem (for me): Afphoto's development process is not non-destructive (i.e. always keep the original and just record the modification steps) as it is in LR. So I had to create a physical copy each time I want to go a different development path. Conclusion for me: Afphoto is more a Photoshop Competitor, not a candidate to replace Lightroom.

That's the question I'm seeking an answer for :-) - Is Affinity Photo a candidate for my daily work processing RAW files etc.

Version 1.5.0.39 When I do the following open a RAW file change some basic settings in the "Develop" persona apply changes by clicking "Develop" save the file as "afphoto" file end the session start a new session open the previously saved "afphoto" file change to the "Develop" persona then all sliders show "0%"?! I attached two screen shots. The first shows the settings that I've made in the "Develop" persona, the second shows the positions of the sliders after re-opening the file. Well, the photo itself shows my changes, but I cannot see, what I did in the last development session...

Ok, today I tried the new beta version 1.5.0.39 My steps to test it: open a RAW file (here in Nikon NEF format) in the "Develop" persona: change the blackpoint, the clarity and the vibrance. apply changes by clicking "Develop" save it as "afphoto" file Now, the file size is 170MB - compared to the 28.1 MB of the original image this is still too big for me... Why does this botter me? When I develop my photos then I want to have a result a) stores all changes but gives me b) the possibility to do further changes in the future. So saving the final result as JPEG is definetively *not* an option. But if every file increases to somewhat near 200 MB, then I'll get trouble to backup my work. After a disk crash some years ago I'm really concerned about backups...

Well, I didn't use layers at all. I played a little with some sliders (tone mapping, saturation etc.) to get a glue how it compares to Lightroom (not PS), then I saved the file as "afphoto"-file. My current process is as follows: I import the RAW-Files into Lightroom and let it convert them into DNG-Format. Then I do the development in LR. In that case, the modifications are stored in LR's catalogue - and also in the DNG file. In my example, the fully developed file is yet smaller than the original RAW - may be due to better compression in DNG than in Nikon's NEF. Another comparable process is: Develop a photo as described in LR, export it in full size as 16-Bit-TIFF, open that TIFF-file in Photoshop and apply some adjustments for soft proof (which is not longer/yet possible for many ICC profiles in LR) - two ... four adjustment layers. In such a case the size of the resulting PSD-files as about 100 MB.

Sounds good :-)

That's exactly what I noticed, too - I got a file size of 458 MB...

I tried to process a RAW foto (Nikon NEF format, camera is Nikon D3200). - The file can be opened without any problem. Fine. - Then I applied some changes in the develop persona. - Then I saved the file in Affinity's native format and got stunned. The original file has a size of 20,4 MB (24 MPix) - the converted "afphoto" file has a size of 458 MB (yes, fourhundred fifty eight megabytes)! So the size has increased by factor ~22! - I attached two screenshots that show the properties of both files (sorry, German labels...). Why??? What happes here? In fact, that's a show stopper for me because that makes the resulting files "unbackupable".