Gregory's Server@dan to be fair, a decade ago we weren't neccesarily oozing clock cycles with Audio, and some of us were getting pretty bad latency/clicks and pops. It did actually matter how things were allicated and used, and Malloc actually had several successors that did a better job by default. I've personally run into these kinds of horrendous system level issues for decades, so I can relate. That doesn't mean it's not a ridiculous convo, just that I can see why it exists 😂
|
2 comments
@mowgli @dan This was in part because the bps for packetised MPEG-4 could really pop if one of our users suddenly had a proper HD stream (still somewhat rare at that point), and that presented a challenge to smooth playback in a player with the wrong concurrency design, buffer design, or drivers (which usually have their own buffers). Custom C++ memory allocators, a la Alexandrescu's work, were part of the repertoire of stuff that helped. |
@mowgli @dan I'm not sure about audio, but I worked for a boutique MPEG-4 technology spinoff called Mediaware in 2007 where stuff that *sounded a bit like* these sorts of issues was a very real concern.