jubro Posted March 7, 2022 Posted March 7, 2022 I have always exported to jpg straight from the photo persona, exporting the 'background' layer with its sub-layers. On my humble pc this process takes quite a few seconds. I have just noticed that if I 'merge visible' all the layers of the photo, and then export the new single merged layer, the export is instant. I also checked and noticed the file sizes of the two exports are different: the export of all the layers is 11.6mb whereas the export of the 'merged visible' layer is only 8.99mb. Please can I get an explanation and advice on quality differences between the two exported versions. Obviously this is quite a difference (almost 30%) in outputted file size and therefore hard drive space used. Many thanks. Quote Affinity Photo 1.10.6.1665 / Affinity Publisher 1.10.6 - Win 10 Home 64 bit 22H2, OS Build 19045.2251 - Asus ROG G20CB - i5-6400 2.7ghz - 8gb RAM - NVIDIA GX950- BenQ BL2783
Staff stokerg Posted March 8, 2022 Staff Posted March 8, 2022 On 3/7/2022 at 8:59 AM, justinpbrown71 said: I have just noticed that if I 'merge visible' all the layers of the photo, and then export the new single merged layer, the export is instant Suspect its instant due to the Affinity not having to merge the layers, as you've already done that part. So far in my tests, i've not been able to replicate a size difference when exporting, with or without flattening layers. Do you have a sample .afphoto file you could attach before you carry out the Merge Flatten and i'll try replicating the size different with your file. Quote
jubro Posted March 8, 2022 Author Posted March 8, 2022 51 minutes ago, stokerg said: Suspect its instant due to the Affinity not having to merge the layers, as you've already done that part. So far in my tests, i've not been able to replicate a size difference when exporting, with or without flattening layers. Do you have a sample .afphoto file you could attach before you carry out the Merge Flatten and i'll try replicating the size different with your file. Thanks for your reply stokerg. Find attached an .afphoto file which I find exports two different sized jpg files, when set to Lanzos non-separable highest quality, depending on whether the CLR or the MRGD VSBL layer is selected. The Background layer is not selected when I merge visible, nor when I export. I make sure to have selected, in the check boxes, only the layers I want to be included in the jpg export. Thanks. untitled shoot-2563.afphoto Quote Affinity Photo 1.10.6.1665 / Affinity Publisher 1.10.6 - Win 10 Home 64 bit 22H2, OS Build 19045.2251 - Asus ROG G20CB - i5-6400 2.7ghz - 8gb RAM - NVIDIA GX950- BenQ BL2783
Staff stokerg Posted March 8, 2022 Staff Posted March 8, 2022 49 minutes ago, justinpbrown71 said: Find attached an .afphoto file which I find exports two different sized jpg files, when set to Lanzos non-separable highest quality, depending on whether the CLR or the MRGD VSBL layer is selected. The Background layer is not selected when I merge visible, nor when I export. I make sure to have selected, in the check boxes, only the layers I want to be included in the jpg export. Great, thanks for the file I'm running this past our QA team to see what is happening here. I do notice in the Merged layer it appears some Inpainting might of been done as the line across the floor is missing, which might account for some the difference in file size, as its technically adding pixels to the image. As soon as i know more, i'll update here jubro 1 Quote
jubro Posted March 8, 2022 Author Posted March 8, 2022 17 minutes ago, stokerg said: Great, thanks for the file I'm running this past our QA team to see what is happening here. I do notice in the Merged layer it appears some Inpainting might of been done as the line across the floor is missing, which might account for some the difference in file size, as its technically adding pixels to the image. As soon as i know more, i'll update here Thanks for your help. The inpainted merged layer though exports at a smaller size than the unmerged layer. I have tried with another file and the difference was 5mb to 9mb; even greater. And yet I have tried with a 3rd file, and the two exported at exactly the same size 🙄... Quote Affinity Photo 1.10.6.1665 / Affinity Publisher 1.10.6 - Win 10 Home 64 bit 22H2, OS Build 19045.2251 - Asus ROG G20CB - i5-6400 2.7ghz - 8gb RAM - NVIDIA GX950- BenQ BL2783
jubro Posted March 14, 2022 Author Posted March 14, 2022 On 3/8/2022 at 2:33 PM, stokerg said: Great, thanks for the file I'm running this past our QA team to see what is happening here. I do notice in the Merged layer it appears some Inpainting might of been done as the line across the floor is missing, which might account for some the difference in file size, as its technically adding pixels to the image. As soon as i know more, i'll update here Hi stokerg, Have you any news on my issue? I have begun work on a new shoot and have already run into a problem with the first image, with regards to downloading as merged: Here are two examples. The first is exported unmerged, and the second using the merged visible command. The second has an area on the floor which is considerably brighter than the first. As you can see, the file size is different too. I would like to know how the merging is affecting the image before I export anymore fotos. Exporting unmerged can take my pc a long time, up to a minute per image, whereas exporting merged is instant. Many thanks. [EDIT: Having posted the two images here there is noticeably little difference (the merged seems a bit brighter). When viewed in Windows Photo the difference is very obvious, but is not noticeable at all in AP.] [EDIT: I sent the two images to the Telegram app (uncompressed) so I could see them on my mobile phone, and the only difference is that the merged image is slightly brighter.] Quote Affinity Photo 1.10.6.1665 / Affinity Publisher 1.10.6 - Win 10 Home 64 bit 22H2, OS Build 19045.2251 - Asus ROG G20CB - i5-6400 2.7ghz - 8gb RAM - NVIDIA GX950- BenQ BL2783
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.