Longshadow wrote:
It has to do with how the pixel information is stored.
Think of one scenario- for simplicity sake; two rows of pixel information, 100 pixels wide:
The first row is all one color, lets say white #FFFF, the second row is alternate black (#0000) and white.
Saving the information with a certain (imaginary) algorithm could be:
100(FFFF)/50(0000,FFFF)/...
(Where "/" is the row separator.)
If both rows were all black:
100(0000)/100(0000)/...
If all pixels in the second row are all different, the algorithm could yield:
100(0000)/0000,2020,01AC,CCFF,0000,CDBF,0100,73CD,AF34, <and on for 100 pixels>
As you can see the second line information string becomes rather lengthy.
This is why more complex images require more storage space for the file. They have to save all the differences, and can't use a "shorthand" like "<number of pixels>"(<pixel color>) or "100(FFFF)".
The manufacturers try to come up with a storage algorithm that will create a small file while retaining all the image info.
It has to do with how the pixel information is sto... (
show quote)
That does make sense, so thankyou for setting it out so clearly. I had no idea of the composition, so thank you again.