4 ms·
Unless I'm missing something, it doesn't appear be that great in this case. The image is supposed to be a 128x32x3bpp image, so that's 12,288 bits / 1536 bytes
by tyingq 8y ago
Unless I'm missing something, it doesn't appear be that great in this case. The image is supposed to be a 128x32x3bpp image, so that's 12,288 bits / 1536 bytes, plus whatever overhead for the image format. The article says the compressed data is 1500 bytes. So, er, not much compression.
The png file on the page of the same data is 741 bytes. An uncompressed 4-bit bmp of the same data is 2250 bytes.
- jandrese 8y agoWow, that's a "why bother" level of compression. I guess the SNES didn't have a lot of CPU cycles left over to run a decompression algorithm, but even a simple deflate seems like it would have greatly outperformed this custom solution. I guess the big advantage is that this seems to have zero memory overhead.
- tyingq 8y agoCould just be this particular image, or that I'm missing something else.
- deleted 8y ago[deleted]
- Skarsnik 8y agoThe 1500 bytes size is me being lazy to search for the right size, the grammar stops at the FF header anyway so knowing the size is not that useful. To answer the initial questions, I remember that the compression ended with like 40-20% fewer bytes for things without really big empty space. Later games on the SNES used lzss like compressions. Thou my owns implementation of the compression give better results (most of the time) for the original datas of the game that the tools used by Nintendo and it's pretty naive.