01/09/2010, 04:54 PM
Zombie Wrote: [ -> ]The video probably won't compress well, however the file structure (container) probably has a lot of redundancy. Open one in a hex editor and you'll probably find a fair amount of null (0x00) bytes. Not exactly sure what the padding is for, perhaps there's something to do with attaining CBR.
126/189 = 0.6772486...
Overhead equal to about ~50% of data? Don't remember program streams to have so much overhead, sounds like a goddamn transport stream.
Zombie Wrote: [ -> ]It's lossless, and there's always a size premium for lossless encoding, whether it's video (x264 lossless vs crf20), audio (FLAC vs AAC) or image. And for the images you're testing, JPEG can probably throw off a lot of redundancy.
Not only PNG, I dislike lossless on a whole. Lossless pretty much screams waste, and the more complicated the medium, the more waste. And no normal human can tell the difference between high bitrate lossy and lossless anyway, under normal circumstances.
Zombie Wrote: [ -> ]Also you don't mention bit-depth. I believe PNG has the ability to use 16-bits per channel, along with a full alpha channel, none of which JPEG can achieve.
Which is useless for everything besides for some very limited applications (and for those, you may as well use goddamn RGBA). Really, have you ever even seen a 64bit image? I mean 99% of the stuff wee get these days are 24bit or 32bit (dubbed "true color"). Someone needs to design something that supports 256bit, just so they can go "my fucking image is better than yours" and "I'm 200 years ahead of time".
Also, in the comparison, I certainly did not use 64bit, so the results aren't skewed. (Unless PNG is retarded and automatically upsamples my stuff, which I doubt).