ultra high defintion loss-less image compressor
consider you had 312.5 pentabytes of storage. according to my math, this would be enough capacity to hold every single possible 24-bit depth image with a width and height of 40 pixels.
this is in effect:
(40 horizontal x 40 vertical) (canvas)
x (256 red x 256 green x 256 blue) (different colour possibilities)
x (40 horizontal x 40 vertical) (each pixel)
x (8192) 8 kilobytes per image
320,000 terabytes (or 312.5 true pentabytes)
if you were to store such an array of images, i imagine it would look something like this on a windows ntfs drive for the first and last image possible, respectively:
including and between these files, would be a total of 42,949,672,960,000 uniquely different images.
each line represented in the example above, contains 30 bytes, or 31 bytes including delimeters.
an ultra high definition television frame is an image with 7680 x 4320 pixels. televisions often display a frame-rate of 30 frames per second.
this means that:
7680 x 4320 (pixels in an ultra high def frame)
/ 40 x 40 (each possible image in a 'patch-work quilt')
20736 (40 x 40 images)
x 31 (representations that can be made up of 31 bytes each)
642,816 (bytes for each frame)
x 30 (frames per second)
x 60 (frames per minute)
x 60 (frames per hour)
x 3 (3 hour feature-length film)
/ 1024 (kilobytes)
/ 1024 (megabytes)
/ 1024 (gigabytes)
so, an ultra high definition 3-hour film could fit in just under 194 gigabytes, without any loss in quality whatsoever, not including sound.
however, not everybody has 312.5 pentabytes to spare.
each representations of each 40 x 40 image are written in a logical order, so 'drawing' each image on the fly would be possible, without the need for any extra storage apart from caching, the codec, and the 194 gigabyte movie itself.