French sysadmin, opensource enthusiast, privacy advocate.
Piracy against the oppression.
Présence inconsistante sur X.
Mastodon et tout le reste en lien 👇
Real Time Audio on general purpose operating systems is ridiculously hard to code.
Unfortunately (and unlike the visual system!) humans are *really* good at noticing audio hitches.
In video, you might have ~16ms to process a video frame, and if you miss the deadline, eh, just continue to display the existing frame. It’ll hitch…but a lot of people won’t notice. The eye is fairly forgiving, mostly deals in averages.
If you miss a SINGLE audio sample (.00002 sec at 44.1khz!) it’s super obvious!
The ear was basically made to detect discontinuities in waveforms; the real life equivalent would be like a twig snapping. The waveform collapse (single audio sample dropped) spreads energy across every frequency band at once, almost every hair cell in your cochlea fires!
There’s not really a great way to fix this. You can sample and hold, (either just the sample or the whole buffer), but the splice to the next chunk will have a *very* audible seam. Smarter systems will crossfade, and then really intelligent protocols like modern bluetooth will attempt to pitch-bend the seam.
But every single one of those “fixes” costs latency and CPU time…which you don’t have in real time audio!
@FrenchResponse Let me say this as a French citizen:
Stfu, please. I don't like the guy in the quoted post, but please, stfu. This will not help to prevent child abuse neither terrorism. You know it, I know it, everybody knows it. You want control, you want to abolish freedom.
@loutreelectrik@Nolzim_@iconoclaste_sp C'est très bien tout ça (sans ironie)
Par contre on n'est pas obligé de dire que c'est ok parce que c'est moins pire. Je pisse aussi au cul de Sony, Microslop, Epic, EA, Tencent, AV etc. (même Valve dans une moindre mesure)
Cette industrie me dégoûte, big N n'est qu'un exemple.