N^M, clearly.
Amateur. Use the whole space [32x32x3 bytes = 3072 bytes] to encode a Busy Beaver.
It's still at most n^m different images.
How much information can a small image contain?
11–20 of 30 posts
Re: How much information can a small image contain?
#12Would this be a good way to avoid censorship. Encode an image by mixing it with a private key image, maybe xor the cells or something like that. Post online. Anyone with the key image can decode.
Re: How much information can a small image contain?
#13Many moons ago, I wondered what it would look like if you iteratively generated every possible image. It doesn't sound very useful at all (and it certainly isn't) but I learned C++ and SDL that way. This is probably terrible code by anybody's standards but maybe someone wants to take a look: https://github.com/svenstaro/infinerator
A story about the text version of this concept: https://en.wikipedia.org/wiki/The_Library_of_Babel
Re: How much information can a small image contain?
#14Re: How much information can a small image contain?
#15Many moons ago, I wondered what it would look like if you iteratively generated every possible image. It doesn't sound very useful at all (and it certainly isn't) but I learned C++ and SDL that way. This is probably terrible code by anybody's standards but maybe someone wants to take a look: https://github.com/svenstaro/infinerator
I think about it from the perspective of ideas, once we figure out something (how to fly, electricity) we know it. How do you brute force find that info through random/massive computation. Specifically to find the next things we don't know like jumping dimensions or FTL, etc...
Re: How much information can a small image contain?
#16Earlier quoted context omitted.
It's still at most n^m different images.
True, but the posed question was "how much information can a small image contain", not "how many unique images are there"
Those are the same things ...
Re: How much information can a small image contain?
#17Earlier quoted context omitted.
It's still at most n^m different images.
True, but the posed question was "how much information can a small image contain", not "how many unique images are there"
What's the distinction?
Specifying an element from a set of 2^n members seems equivalent to encoding n bits of information.
Re: How much information can a small image contain?
#18I was hoping this was an article about packing different executables into images like I saw on Twitter.
Re: How much information can a small image contain?
#19Many moons ago, I wondered what it would look like if you iteratively generated every possible image. It doesn't sound very useful at all (and it certainly isn't) but I learned C++ and SDL that way. This is probably terrible code by anybody's standards but maybe someone wants to take a look: https://github.com/svenstaro/infinerator
I've thought about this as well; it's one of those weird things where you realize that with enough pixel count and shading options, every image you can think of exists within the total set of generated images.
"enough" hides a surprising amount of work. Mobilise the entire planet's computers for a decade, assuming a generous Moore's law increase as well, and you might count through seventeen 8-bit grayscale pixels in that decade.
Annihilate the Sun and you won't get enough energy to drive a simple counter through thirty 8-bit grayscale pixels.
Re: How much information can a small image contain?
#20The introduction has lost me completely: such a long winded way to say that 32x32x3 bytes can represent 2^(32x32x3x8) different values.
[deleted]