|
|
|
|
|
|
by majewsky
1913 days ago
|
|
|
There was an LWN article about PipeWire [1] a while back. Among the interesting parts of the article was an explanation for the PulseAudio debacle, and why PipeWire likely doesn't have the same problem. Basically, PulseAudio exercised several kernel APIs that had existed in ALSA for a long time, but had not been used widely. Hence it uncovered a ton of bugs in device drivers that were not tested against applications using these function calls before. By now, all those bugs are fixed because PulseAudio is widely used. PipeWire is using mostly the same APIs as PulseAudio and Jack, so it's not going to have the same troubles as PulseAudio. [1] https://news.ycombinator.com/item?id=26327779 |
|
|