I need software for that.
Well, duh.
Where can I find such software?
You'll need to write it yourself. Sadly, all the programmers who write
audio or video CODECs for a living believe that it's impossible to
compress randomly selected, high resolution, 2 hour long movies down
to a single bit, & then successfully decompress them back into
something recognisable as the original movie.
BTW, in the unlikely case that you're not actually a troll[0], & are
simply clueless about mathematics & physics, there is an intuitive,
non-mathematical way to understand why it's impossible to compress a
bunch of movies down to files that each contain a single bit, & then
recover the movies from those files:
(1) Imagine that you own DVDs of your 10 favourite movies, & you wish
to compress them down to 10 files, each containing a single bit.
(2) By definition; a single bit can only be '1' or '0'. If it can be
anything else, it's no longer a 'bit', & calling it a bit is simply
mistaken.
(3) Your hypothetical uber-compressor can only generate one of two
possible compressed files: One that contains a '1', or one that
contains
a '0'.
Problem #1: Suppose you uber-compress your favourite DVD ('The
Matrix') down to a single bit: '1'. Next, you want to compress your
next favourite movie ('Capricorn One'). Now here's where things start
to get weird, because no matter what data - or even what movie - is on
that DVD, we know that the new compressed file *must* end up being a
'0', because the compressed version of 'The Matrix' is '1', & if our
uber-compressor outputs a '1' for *both movies*, it is *impossible*
for our uber-decompressor to 'know' which movie to play!
So, it logically follows that 'Capricorn One" *must* compress to file
containing only a '0'. However, the fact that you could've picked *any
movie* (other than 'Matrix') from your shelf, & it *must* compress to
a '0', should tell you that something is seriously wrong with the
logic underlying our uber-compressor.
Now, ignoring that fo the sake of argument, let's pretend that by
some god-like miracle of software engineering, your uber-compressor
manages to play 'The Matrix' for you when you give it the '1', & plays
'Capricorn One' when it is given the '0' file. This leads us to:
Problem #2: What happens when you try to compress a *third* movie (eg;
'Final Fantasy')? The answer is that, by definition, our
uber-compressor *cannot* produce a single-bit file that will
decompress to 'Final Fantasy', because there are only two possible
single-bit files: '0' & '1', & our uber-compressor has already used
both of them! So, no matter what bit it outputs, it'll be identical to
either 'The Matrix' or 'Capricorn One', so the decompressor cannot
possibly play back the correct movie, because it has no way of telling
the difference between the uber-compressed version of 'Final Fantasy'
& the uber-compressed movie file which has the same contents.
And *that* is why there is no such thing as a video
compression/decompression system that can compress more than two
abitrarily-chosen movies down to a single bit.
This same logic can be extended to determine all sorts of useful
things about the limits on storing data efficiently, or how much data
you can squeeze through a communications medium in a given time.
'Information Theory' is the name for this field,
<
http://en.wikipedia.org/wiki/Information_theory>
which was pioneered by Claude Shannon
<
http://en.wikipedia.org/wiki/Claude_Elwood_Shannon>
HTH!
[0] And even if this explanation is wasted on you, it may help others
who aren't familiar with information theory, or who (like myself) find
the mathematical explanations & proofs difficult to grasp.
)