encoding a video to make it easier to datamosh

In any case, an LZ decompressor fits in less than 100 bytes of machine instructions and a simple compressor can be implemented in not more than several hundred, all the while providing extremely high compression for its simplicity. Thus it is, at least to me, somewhat surprising that LZ was only documented academically several decades after Huffman perhaps it was thought to be too trivial? LZ can also be thought of as an extension of RLE. Even human languages have things like contractions, abbreviations, and acronyms. I think the LZ family are all pretty intuitive - just replace repeated sequences with a reference to where they occurred before. The solution to this is easy and is Huffman coding, but it doesn't make sense to show it for a ten bit message as it won't work well, and in the trite explanation of compression of 'just the symbol and then the number of times it's repeated' this isn't mentioned, so it's only half the story and people will still be puzzled because they will see that your message contains MORE entropy after 'compression', not LESS! See what I mean? It's not successfully compressed anything. And HTHTHTHTHT would be forty bits so if the message doesn't repeat simply it's now four times larger! If I introduce this simplified compression to the system and add 0-9 to the alphabet, that now needs four bits per symbol, so the message H10 is 12 bits long (which is longer than uncompressed). Yes I get that the alphabet is already agreed upon.īut if I only transmit H or T (uncompressed) that's just one bit needed per symbol. you would just transmit 'H_10' with the universally agreed upon knowledge that 'H' is 'Heads' and '_' is number of times.

Encoding a video to make it easier to datamosh