Claudio60 Posted July 29, 2019 Share Posted July 29, 2019 Still in this release (1.7.2.434) there is no fix for the bigger .aphoto file size generated from a .jpg photo on save, sadly. Link to comment Share on other sites More sharing options...
TEcHNOpls Posted July 29, 2019 Share Posted July 29, 2019 I don't think that's a bug. The file format is updated and it's not size but performance optimized. Thou a size optimized file format could be useful when archiving work. PaulAffinity and Mark Ingram 2 "I'm a lumberjack and I'm OK, I sleep all night, and I work all day..." Link to comment Share on other sites More sharing options...
walt.farrell Posted July 30, 2019 Share Posted July 30, 2019 4 hours ago, TEcHNOpls said: The file format is updated and it's not size but performance optimized. True. But approximately 3x bigger when saved in 1.7 than in 1.6? Claudio60 1 -- 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...
gdavis Posted July 30, 2019 Share Posted July 30, 2019 Actually, the smaller file size of 1.6 doesn't sound right. It sounds like that file is still storing the JPEG compressed image, but once you start working with the file you don't want it to JPEG compress your working data. I just tried opening a JPEG in 1.6 and saved it and yes, the afphoto file size was about the same. Then I simply right-clicked the background layer and selected rasterize then re-saved it. This new file was about 4M which is the expected size for the uncompressed image. To me this is reasonable behavior. You shouldn't expect afphoto files to be as small as the JPEG file because of the compression. As long as two working files (not just saved JPEGs) aren't drastically different between 1.6 and 1.7, I don't think there's a problem. Mark Ingram 1 Link to comment Share on other sites More sharing options...
ashf Posted July 30, 2019 Share Posted July 30, 2019 afphoto (or even psd) is not lossy format. so bigger than jpg is normal. In order to keep picture quality the same, it have to be lossless which is bigger than lossy. v1.6 file might be something wrong. Link to comment Share on other sites More sharing options...
gdavis Posted July 30, 2019 Share Posted July 30, 2019 Actually, I just found another post that mentioned that an unedited JPEG will save the original data to the afphoto file so the file size stays small. But of course once you edit it, it would have to re-compress which is not desirable so the file size goes up. Perfectly reasonable. Mark Ingram 1 Link to comment Share on other sites More sharing options...
Claudio60 Posted July 30, 2019 Author Share Posted July 30, 2019 Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted April 17, 2020 Staff Share Posted April 17, 2020 Sorry. Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum. Report a Bug in Affinity Designer Report a Bug in Affinity Photo Report a Bug in Affinity Publisher Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem. This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build. Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon Link to comment Share on other sites More sharing options...
Recommended Posts