Why is afphoto file so massive when saved?

[Oval]

Hi Nilla's Photography!

Have you found the reason for your problem or is your computer in vacation / dead?

[Nilla's Photography]

Not really so I am none the wiser. I haven't done your test yet as I've been working on building my new site so stopped editing photos. 

[blue_heron]

I have the same problem.

Simple files with one background layer and some adjustments become HUGE.

I don't care while I'm working, but this is very bad for archiving.

[Oval]

3 hours ago, blue_heron said:

Simple files with one background layer and some adjustments become HUGE

What helps is the use of (white) rectangles above each layer, sometimes to delete one afterwards, for example.

And perhaps this.

“Save With History” is off?

“Simple files” with what dimensions?

“HUGE” means exactly what?

[blue_heron]

“HUGE” means that a 45MB RAW file (Nikon D800) becomes a 500MB Affinity file (BG Layer plus one adjustment layer).

 

 

[Oval]

21 hours ago, blue_heron said:

becomes a 500MB Affinity file

completely OK for Serif

[Granddaddy]

You have to remember that the size of even simple Affinity Photo files were made 4 to 10 times larger with version 1.7 when compared to version 1.6 as a result of last minute file format changes required by Affinity Publisher. Serif does not consider the afphoto file format suitable for longterm storage so file size is not something they are concerned about.

https://forum.affinity.serif.com/index.php?/topic/87912-170380-huge-file-size-when-saving-16-image/&do=findComment&comment=527169

 

[walt.farrell]

1 minute ago, Granddaddy said:

You have to remember that the size of even simple Affinity Photo files were made 4 to 10 times larger with version 1.7 when compared to version 1.6 as a result of last minute file format changes required by Affinity Publisher. Serif does not consider the afphoto file format suitable for longterm storage so file size is not something they are concerned about.

https://forum.affinity.serif.com/index.php?/topic/87912-170380-huge-file-size-when-saving-16-image/&do=findComment&comment=527169

 

You have misinterpreted that post, again, Granddaddy.

@Mark Ingram was referring to a specific situation, "The example of loading a jpeg and either saving as-is, or making minor edits" which is why he concluded with "in this instance".

We discussed that before, and he supplied a follow-on comment.

 

[Cecil]

I was amazed at one post that Affinity does not recommend working from external drive.  I believe a lot of Mac users, purchasing new iMac or Mac Pro, buy smaller internal SSD (cost) and buy 1 or 2 TB external drive.  The same applies to RAM, 8 GB Apple and update from online.  As the post did not say this is a bug, is Affinity working on external hard drive processes? 

[Oval]

48 minutes ago, Cecil said:

is Affinity working on external hard drive processes? 

Perhaps Serif is. But why?

[v_kyr]

1 hour ago, Cecil said:

I was amazed at one post that Affinity does not recommend working from external drive.

Well external drives here probably meant more in the sense of cloud & net based drives, which can easilier lose their filesystem connection and often don't offer a continiously stable read/write speed throughput.

1 hour ago, Cecil said:

I believe a lot of Mac users, purchasing new iMac or Mac Pro, buy smaller internal SSD (cost) and buy 1 or 2 TB external drive.  The same applies to RAM, 8 GB Apple and update from online.

No need to ask, due to their price politics here for sure. - Though the bad nowadays, mostly everything that was once user changable (RAM, storage) is today firmly glued on MoBos, so internal upgrade chances are from startup often limited to non-existent.

[Cecil]

3 hours ago, Oval said:

Perhaps Serif is. But why?

 

[Oval]

21 minutes ago, Cecil said:

 

Is not a reason to work on external hard drive processes. The question is the size that has nothing to do with the size of the file.

[Cecil]

1 minute ago, Oval said:

Is not a reason.

I really don’t understand “Is not a reason?”  A reason for what?  If it is not advised to work from external drives and you depend, for cost reasons, to purchase external SSD and if I cannot use it with AP, that is a reason for a problem to “may” occur.  Sorry if I am misreading your post.  Until, they fix AP, Apple Photos Mojave and Catalina, I just export to SSD.  As a hobby and senior citizen, I have no deadlines.

[Oval]

7 minutes ago, Cecil said:

not advised to work from external drives

You did not read it in the help, right?

[Oval]

13 minutes ago, Cecil said:

a problem to “may” occur

Nilla's Photography does not have such a problem. Nilla's Photography just likes to have smaller files.

[Cecil]

4 minutes ago, Oval said:

Wrong.

Wrong quote, wrong info from quote, or  quote not correct?  My reason for first post was because I read the thread and later provided the quote.  I really don’t care, export works for me on my SSD, others may have problems, if afphotos file.  

[Oval]

10 minutes ago, Cecil said:

export works for me on my SSD, others may have problems

So again: Why should Affinity work on external hard drive processes? They are working to make the files smaller. At least as small as before 1.7.

[Cecil]

Just now, Oval said:

So again: Why should Affinity work on external hard drive processes? They are working to make the files smaller. At least as small as before 1.7.

Proof is in the pudding.  I also read in thread it was not Affinity’s intention for users to long term maintain afphotos files.  Please enjoy your night, not my fight for or against.  

[R C-R]

As things stand now, the important thing is to ensure that the connection to the drive where the document file is stored is continuous (not interrupted). Obviously, that is true for internal drives, & it usually is for directly connected USB & Thunderbolt external drives, but not for network ones.

[Oval]

5 minutes ago, R C-R said:

that the connection to the drive where the document file is stored is continuous

Which is in this case, because Nilla's Photography writes the file again and again (with the same error-free length).

[R C-R]

1 minute ago, Oval said:

Which it is in this cad, because Nilla's Photography writes the file again and again (with the same error-free length).

"cad"?

[Oval]

3 minutes ago, R C-R said:

cad

Sorry, you are too quick.

[R C-R]

4 minutes ago, Oval said:

Which is in this case, because Nilla's Photography writes the file again and again (with the same error-free length).

FWIW, one of the original key features of the Affinity apps was file serialization, chosen for performance reasons because it avoids the need to rewrite the entire file on each save. That is one of the reasons native format files are so large. So I wonder how they can work around that without a major overhaul of the code & the native format.

[Oval]

27 minutes ago, R C-R said:

So I wonder how they can work around that without a major overhaul of the code & the native format.

If the file size changed on average by a factor of 3 from one to the other version, then Serif could change it again and again.