3 ms·
So bizarre! It really shook my belief in Philips' competence at the time. I mean, take a 100 minute movie, sliced into 1-second clips. 8kB is not even enough t
by mdemare 1y ago
So bizarre! It really shook my belief in Philips' competence at the time.
I mean, take a 100 minute movie, sliced into 1-second clips. 8kB is not even enough to store all possible orders you could put those clips in. I would hate to think so ill of any of my friends or colleagues to think that they could believe such an obvious fraud.
- aeve890 1y agoIs it a sort of reversible pseudo-hashing function even possible? Or something like a seed in a deterministic procedural generator. You could store arbitrary data in a few bits. 8kb for all the redundancies and metadata even. On a second thought, the compression alone would destroy information. NVM.
- astrange 1y agohttps://en.wikipedia.org/wiki/Vector_quantization https://en.wikipedia.org/wiki/Vector_quantization https://sound.stackexchange.com/questions/45719/perceptual-noise-substitution-and-aac https://sound.stackexchange.com/questions/45719/perceptual-n...
- Dylan16807 1y ago> I mean, take a 100 minute movie, sliced into 1-second clips. 8kB is not even enough to store all possible orders you could put those clips in. Using a low hurdle to show it still failing is a good rhetorical technique, but you lowered your hurdle too far here. Yes technically specifying the order of 6000 segments takes more than 8KB. Because it takes 8.14KB. That's a rounding error. What could have been a useful argument is now a nitpick. And what if the movie was only 98 minutes, now it fits? What a mixed message. It's a good reference point, but I'd replace "is not even enough" with "would only be enough".
- mdemare 1y ago8kb to specify the order of the clips, but not a single bit is used to describe a single pixel of a single frame.
- Dylan16807 1y agoYes. That's why it's "only enough to".