Probably this post was inspired by all the fuzz gibberlink made last week, which uses ggwave, another data-over-audio protocol.<p><a href="https://github.com/PennyroyalTea/gibberlink">https://github.com/PennyroyalTea/gibberlink</a>
Cool to see this done with webaudio. Reminded me of <a href="https://github.com/ggerganov/ggwave">https://github.com/ggerganov/ggwave</a>
12 years ago, I worked on this prototype - <a href="https://github.com/tanepiper/adOn-soundlib">https://github.com/tanepiper/adOn-soundlib</a><p>The original plan was to develop essential "audio QR codes" that would allow short codes to be transmitted that could be parsed by certain apps and used to drive different interactions.
Turning data into audio is a big thing nowadays with amateur radio.<p>Ironic that the author overlaps so much with that field, without noticing that they chose the same name as probably the most used amateur radio programmer in the world.<p>If you're interested, the state of the art is VARA. It's closed source though, so NinoTNC may be a more interesting choice.
There's also <a href="http://www.whence.com/minimodem/" rel="nofollow">http://www.whence.com/minimodem/</a> which implements some standard methods:<p>> standard FSK protocols such as Bell103, Bell202, RTTY, TTY/TDD, NOAA SAME, and Caller-ID
There's an Amazon-backed close-to-$100M funded established company in India called ToneTag which has its use case for sound data transfer for retail payments/etc. I still don't understand how they work from a consumer-use standpoint, but I find it fascinating.