Jump to content

Recommended Posts

Posted

Just at test and curiosity i wanted to see how much fille space would be lost for different atchins.  It seeml like recorind history states would be kilobytes in nature and would be small.  these ar my results

Jpeg Orignal Image                  3.94 Mb

Saved as Affinity                         8.04

saved with 1 Selection channel  11.9

2 Channels                          12.2

4 Channels                              8.321

5 Channelss                            12.2

6 channels                            8.33

7 Channels                           12.2

i  Histroy State                     29.6

2 HS                                         21.7

All the abobe plus 1 hist state  21.1

2 hist state                         33.7

3 his stae                            25.5

All Above with 27 hs      40.4

50 hs    72.5

75 hs    100

First question::  Why did they jump around a lot, and why were they inconsistent.  Second qustion (and the most imp):  Shouldent a simple change in a history state just be measured in Kb, it thee's nothing to record Except a few numbers.

 

Just trying to get some insight in how to handle file sitesl  Go back to the first example a 3.94 Mb image was saveds to Affinity and came out at 8.04 and that's understandable.  But the next addition of only 1 selectes could be desribe in just a few kilobyes but it was 11.9

 

Please advise!

 

Posted

By "Selection channel" do you mean creating a spare channel in the Channels panel or something else? Assuming you do mean a spare channel, are you creating them from a composite channel, a layer channel, or a pixel selection? Since spare channels are basically one channel pixel bitmaps, it should not be too surprising that their sizes vary depending on how many pixels they are mapped from.

As for why the saved file sizes vary so much, part of it is because the native file format uses a proprietary form of serialization, so changes to saved documents often are added to the end of the file instead of rewriting the whole thing on the next or subsequent saves. Because it is considered proprietary information, Serif has not shared much about the details of how this works or what exactly triggers rewriting the whole thing, so there is not much more to say about that, other than supposedly "Save as" always writes a new file with the changes 'baked in,' resulting in the minimum file size ... but in my experience this often does not result in a significant change in file size.

All 3 1.10.8, & all 3 V2.5.7 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
A
ll 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Posted

Yes it is a spare channel from the pixel selection.  I didn't realize the program would create a bitmap of the entire selection.  I was thinking it would be more like a path with just something like x and y axis values. I often work on 8x10s at 300 dpi or similar sizes and just expected files generally less than 10 15 Mb.  This will take some getting used to but it's worth it to have all this editable info packed into maybe a 50 Mb file.  Thanks for your help!  

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.