4 ms·
One thing I'm slightly worried about "machine learning" in compression rather than conventional everything-is-sines mathematical approaches is the possibility o
by pjc50 6y ago
One thing I'm slightly worried about "machine learning" in compression rather than conventional everything-is-sines mathematical approaches is the possibility of odd nonlinear errors. Remember the photocopier that worked by OCR and would occasionally mis-transcribe numbers?
I don't mind compressing a phoneme to <unintelligible> as much as I would mind it compressing it to a clearly audible different phoneme.
- minikites 6y ago>Remember the photocopier that worked by OCR and would occasionally mis-transcribe numbers? For those who don't remember: http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_are_switching_written_numbers_when_scanning http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_...
- smnrchrds 6y agoThis one too: https://petapixel.com/2020/08/17/gigapixel-ai-accidentally-added-ryan-goslings-face-to-this-photo/ https://petapixel.com/2020/08/17/gigapixel-ai-accidentally-a...
- rexreed 6y agoThe OCR issue was the first thing I thought about. Machine learning is probabilistic, not deterministic, so in the case of S being converted to 5 (or 6 to 8, etc.), which definitely impacts numerical data in the case of the OCR stuff, we can expect similar voice mis-classifications. Perhaps "You're fine" might get misclassified as "you're fired".
- dqv 6y agoThis already happens with existing compression algorithms. Certain vowel sounds get collapsed, so someone will say, for example, "66" and it will come out on the other side as "6". Very annoying because you can't exactly coach a layperson on how to talk "the right way" to not trigger this vowel collapse.
- chrisshroba 6y agoI'm having a little trouble following this, could you explain a bit more? It seems to me like "66" would be pronounced "SIKSIKS", so for that to become "SIKS" would mean the "KS" (consonants) would be collapsed, no? (Not trying to refute you or anything, just understand :) )
- howinteresting 6y agoProbably turn into something like SIIIIKS.
- dqv 6y agoExactly, but sometimes it's so subtle you can't even tell it's the compression taking over.
- gopalv 6y agoAs someone with a weird sibilant that doesn't seem to compress well, I want to say that it goes across as "sɪkɪks" and I got used to saying "double six" on the phone. So I would say "seven nine double six", which is another problem if I'm talking to an American. This applies to GSM digitization and other "regular phone" compression, the newer computer calls have been better at taking the words.
- bobthechef 6y ago> you can't exactly coach a layperson on how to talk "the right way" to not trigger this vowel collapse I've never noticed. At any rate, we should not coach people to adapt to technology in this way. It is Procrustean and anti-human and unnecessarily places a burden on people that belongs to the software and the developer.
- 1-6 6y agoOne day, voice cloning may become so powerful that only word data and intonations will become part of the datastream. There could be various 'layers' in which encodes/decodes can occur. Voice Cloning would be at the very top of the stack.
- tyingq 6y ago>photocopier that worked by OCR The interesting bit was that it wasn't supposed to work by OCR...that had been deliberately turned off. The compression was too clever.
- thaumasiotes 6y ago> Remember the photocopier that worked by OCR and would occasionally mis-transcribe numbers? That was perfectly ordinary compression? The phenomenon is all over the place, most visible in autocorrect.
- bayindirh 6y agoIt was ordinary compression, something called JBIG2. It did not mistranscribe, but mark slightly different number or character blocks as same, resulting replaced parts in images. In other words, its match tolerance is a bit too lax, so it get poisoned by blocks in its own dictionary, thinking it already has the blocks for things it had just scanned. More details can be found in [0] and [1]. [0]: https://www.theregister.com/2013/08/06/xerox_copier_flaw_means_dodgy_numbers_and_dangerous_designs/ https://www.theregister.com/2013/08/06/xerox_copier_flaw_mea... [1]: http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_are_switching_written_numbers_when_scanning http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_...?
- Wowfunhappy 6y agoYes! This is why I always turn off autocorrect! It’s true that I absolutely make more typos without it, but at least they’re obvious as typos, and not different words that potentially change the meaning of the sentence.
- cbhl 6y ago[disclaimer: Personal opinion, not that of my employer.] I had a coworker play me before/after of an early version of the codec "babbling" and it was definitely uncanny valley. It looks like some work has been done on the problem since then. The second paper linked in the README.md of the repo talks about talks about a few strategies to reduce 'babbling' or 'babble'. For your reference, here's the citation and the link to the PDF. Denton, T., Luebs, A., Lim, F. S., Storus, A., Yeh, H., Kleijn, W. B., & Skoglund, J. (2021). Handling Background Noise in Neural Speech Generation. arXiv preprint arXiv:2102.11906. https://arxiv.org/pdf/2102.11906.pdf https://arxiv.org/pdf/2102.11906.pdf
- est31 6y agoBack when Lyra was announced [0], I listened to the released samples and it changed an "m" sound to an "l" sound. [0]: https://news.ycombinator.com/item?id=26309553 https://news.ycombinator.com/item?id=26309553
- beagle3 6y agoAre you aware that the same exact uncompressed recording sounds different depending on context? This is known as the McGurk effect. Very worth your two minutes if you're not yet familiar with the effect: https://www.youtube.com/watch?v=2k8fHR9jKVM https://www.youtube.com/watch?v=2k8fHR9jKVM
- taneq 6y agoWhile fascinating, that’s not the same as a codec failing silently by literally changing one word into another, equally clear word instead of getting fuzzy or unintelligible.
- ehsankia 6y agoAt the end of the day, it all comes to using the right tool for the job, and this is just another codec in your toolbox. This is no different than using, for example, a probabilistic algorithm to solve some NP-hard problem in your real world software. As long as you understand the limitations, I don't see an issue with using an algorithm that has a small non-significant (for your use-case) rate of failure. I would definitely not use this to communicate with the space station, but in the right context (Google Duo, low bandwidth), it's the perfect tool.
- ampdepolymerase 6y agoIt would be curious how the court would interpret this. Just wait for the next high profile SEC shakedown.
- beagle3 6y agoThat’s probably meant for another thread
- ampdepolymerase 6y agoI meant phone taps.
- zmix 6y agoYou mean like: "Buttle" vs. "Tuttle" ?
- swiley 6y agoIMO: the output of machine learning is correlated garbage. This is confusing to most people who are used to programs that implement an algorithm (reminder that "correctness" is part of the definition of an algorithm.)
- lonjil 6y agoThe problem with JBIG2 and why it mistranscribed is that it worked by average error, instead of something sensible like maximum error.