Mtcc - matrix to coordinates compressor

[Sportman]

Trying to describe byte values different then the common binary number system I wrote Mtcc.

Mtcc take by default 128 bytes and place them in a 16 x 16 matrix like a bitmap. Not used matrix rows are excluded and same with the row/column values behind the last value in a row, this last one only if there is any gain. What is left from the matrix is stored with the shortest 128 coordinates.

It run under Windows as command line mode 32 and 64-bit and need Framework 2.0 or higher.

Command line syntax:
Compress: mtcc c input output
Decompress: mtcc d input output

Memory usage is very low, gain is also very low, probably the worst compression algorithm ever made.

There is an undocumented parameter when you put a space and number behind the output parameter the amount of matrix coordinates can be controlled, sometimes 256 can give better results then the default 128.

There is no error handling and because it's more an encoder then compressor, it's probably possible to decompress any random input file without an error.

A future idea is to split the output optional in two parts, a matrix and coordinate part, where one can be transfered secure and the other not secure to reconstruct original at destination side with both parts.

Download
http://www.metacompressor.com/download/mtcc.zip

[jethro]

Trying to describe byte values different then the common binary number system I wrote Mtcc.

Memory usage is very low, gain is also very low, probably the worst compression algorithm ever made.

This algorithm works comparatively well for very short inputs.
(Finally 'twits' can have more than 140 characters1!1!!. This can change the e-world !!1!!11).

[Sportman]

New version two changes:
- changed debug value in dynamic value to detect expanding matrix, this must improve compression ratio.
- changed limit undocumented parameter amount matrix coordinates value from 256 to 65,536.

For clearance:
The undocumented parameter amount matrix coordinates must be give with compression AND decompression.
When I wrote "it's probably possible to decompress any random input file without an error", I mean that you can take any file not compressed by Mtcc and decompress it with Mtcc possible without an error and get an expanded bogus file. For encryption handy that an unauthorized user do not know it has the wrong input file, but for testing a typo can easy be missed.

Download
http://www.metacompressor.com/download/mtcc.zip

[Sportman]

This algorithm works comparatively well for very short inputs.

Yes I noticed it too, probably because it do not write any headers and use only one bit every matrix and one byte every file overhead.

140 character do not fit in one matrix with the default setting, setting the undocumented parameter at 140 or 256 can maybe make it smaller.