tcurdt Posted July 3, 2019 Share Posted July 3, 2019 Hey there, I've already in a couple of forum threads about the file size behaviour of Affinity Photo. Unfortunately things still don't quite add up for me. I've got a 10MB NEF RAW file. I've reduced to RGB/8, history is turned off and I also used "Save As" trying to trigger the file streamlining. Still the Affinity Photo file is 112MB. What am I missing? cheers, Torsten Quote Link to comment Share on other sites More sharing options...
Staff stokerg Posted July 4, 2019 Staff Share Posted July 4, 2019 Hi tcurdt and Welcome to the Forums, All i can really do is link you do this post which has comments from the Dev team who wrote the Affinity file format and explain how it works. Quote Link to comment Share on other sites More sharing options...
tcurdt Posted July 4, 2019 Author Share Posted July 4, 2019 Thanks, @stokerg Unfortunately all the infos I found and read suggested that a "Save As" should shrink the file to a reasonable size. And that's just not the case for me. Any further suggestions? Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted July 4, 2019 Share Posted July 4, 2019 I was going to ask if you'd done anything special to the file after Developing the image, but first I decided to try it myself. My 19MB NEF file becomes a 136MB RGB-16 .afphoto file when Saved. I then converted it to RGB-8 (Document > Convert...) and did a Save As, and the saved file increased to 144MB. I then opened the Snapshots panel, and deleted the background Snapshot, and did another Save As. The file size did not decrease; the byte count remained identical. I then exported as a TIFF, without compression, and got a 46MB TIFF file. Loading that TIFF file into Photo, and doing a Save As gave my a 56MB .afphoto file (including the background snapshot). I then decided to delete the background snapshot, and I did another Save As. Deleting the snapshot did not reduce the file size of the newly saved file. The byte count remained identical. (All "Save As" operations were done using new filenames.) All files are available for upload to Serif for analysis, @stokerg, if you'd like them. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
tcurdt Posted July 4, 2019 Author Share Posted July 4, 2019 Thanks, @walt.farrell, I am quite glad it's not just me Your tests exactly reflect my experience. Quote Link to comment Share on other sites More sharing options...
tcurdt Posted July 28, 2019 Author Share Posted July 28, 2019 So no further comments? Ballooning files like that is a bit of a problem for the long term. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.