4 ms·
Most of these codec/signal processing projects tend to strike a nerve for me due to the ignorance of how unintelligible the processed output is (as someone who
by boneitis 3y ago
Most of these codec/signal processing projects tend to strike a nerve for me due to the ignorance of how unintelligible the processed output is (as someone who has a very difficult time with this and very regularly has to ask people to repeat themselves 4-5x even in meatspace interaction), so from the particular angle my outburst came from, it's admittedly being unfair to Discord.
However, I find the aggressiveness of these things to still be a problem.
In Discord's case, I can't wrap my head around how people find those tearing/crunching sounds that result from trying to smooth out keyboard strokes desirable; particularly because it largely washes out the speaker's output feed and sounds really bizarre and out of place. I would rather just hear their keystrokes.
If you want to smooth out the really acute/jarring occurrences a bit: fine. But as it is, people seem to want to suppress/compress to the point of throwing the baby out with the bathwater. I chalk it up to their desire to squeeze every bit of bit-compression for their marketing/employment/performance metrics. my 2c. /shrug