Making Sense of the Audio Stack on Unix

Re:Making Sense of the Audio Stack on Unix by pitterpatter on Monday February 08, 2021 @02:44AM (#26061810)

>as opposed to the pulse maintainers who are jerks.

That doesn't seem fair to just throw out without proof. In all the interactions I've seen them in, they've come across alright for the most part.

[ Parent | on HN ]

Re:Making Sense of the Audio Stack on Unix by da_big_ghey on Monday February 08, 2021 @07:19AM (#26063512)

Sure, here's a good example: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge...

Maintainers unresponsive, talking about making changes but not following up. They strung the guy along for quite a while on this new codec selection mechanism problem. They claim to be in a v14.0 freeze for two months. He updated his code to work on new v14.0 to more unresponsiveness from maintainers about merging. And it goes on from there.

If you've had to use pulseaudio-modules-bt or pali's patched version rather than official pulse, this is why. By comparison, pipewire managed to get it working with little effort because its lead developer is a nice guy and responsive.

[ Parent | on HN ]

Re:Making Sense of the Audio Stack on Unix by pitterpatter on Monday February 08, 2021 @02:02PM (#26068603)

I understand both side's perspective here. I've been a contributor just waiting around for my changes to get merged. But I've also been on the other side maintaining a project which is no small feat. There's a lot that goes on that isn't obvious.

Overall a really unfortunate turn of events there. On a personal note I've been watching that space for awhile and was looking forward to Pali's great work on bluetooth.

[ Parent | on HN ]