No, I am just commenting on "difficulty" of embedding data in random bits. I have not looked to see what MQA does.
While you are correct with your RF analogy, I think I have an easier to understand one: right now we're actually all looking at random bit's being transported over the internet from the ASR webserver to our browsers. It's all encrypted, and those data streams are in essence pure noise, still, you can read this, can't you? An MQA stream is equivalent in that sense. It's just that the "encryption" scheme is far less elaborate than what is used to bring you this text. Counter to that, greater care has been taken to shape the random noise distribution into the high frequencies to make it less obvious. In RF they use something similar to get uniform power distribution called data whitening. This essentially converts any bitstream into white noise. But don't confuse this with what Amir explained in his example, it's again another principle
I'm not saying that MQA uses this technique specifically. There are other things to achieve similar results, and you'd still need to shape the result. It's just an illustration of how you can make data look seemingly random.
@mansr might know exactly what is being used.
You can do lot's of fun things with a pseudo-random generator as well. The kicker is that it is predictable, as long as you know the seed and number of iterations. This means that if you have a clock that poops out a pseudo-random number every second, you can predict the next number until eternity. You can use this for all kinds of clever schemes. So as you can see: there are many methods to generate a seemingly random signal that hides actual data. And most of them are very efficient as well: for every random byte, you get one byte of actual data back.
BTW, could be a fun experiment to take an MQA file, chop off the upper 17 bits, amplify what is left and then listen to it to see how it sounds. Especially for young people.
