Re: my last boost of @fireborn's post on Linux accessibility (fireborn.mataroa.blog/blog/i-w…), I propose that fixing audio on Linux would be a good place to start. "Linux audio doesn't work" is a meme even among sighted people. I know that reducing it down to that is perhaps unfair to all of the people who work on the audio stack, but there seems to be some truth to it. Any ideas on what can be done to finally make audio output as reliable as the graphics stack? I'll put money where my mouth is.
Adrian Vovk
in reply to Matt Campbell • • •Samuel Webdev & plus
in reply to Adrian Vovk • • •@AdrianVovk
I entirely agree with you. Pipewire has made Linux audio reliable, and the preempt flags in the kernel have solved the low latency kernel issue for pro audio too.
Quite some people in the #linuxaudio scene don't want to change because a quirky system they know seems better than a reliable system they don't know.
(I should ©®™ this sentence).
@matt @fireborn
Adrian Vovk
Unknown parent • • •TTYs are very weird environments that exist outside of any kind of session, at least until you log in. They might as well not exist as far as most services can tell. This is just a legacy of how they work
The good news is that this all will be fixed sooner rather than later, because the TTY is going away. Instead it'll be replaced with a graphical terminal, which should give you access to a screen reader
Can't say much about the other issues. I've never run into them
Adrian Vovk
in reply to Adrian Vovk • • •Some of your Pipewire issues might actually be Wireplumber issues. Pipewire is just dumb media routing. The smarts, like card and output selection, belong to Wireplumber. Are you using Wireplumber?
Are the bugs you've run into known issues, or have you filed bug reports? Realistically it's possible that you're triggering bugs that others haven't encountered and so they will never be fixed because nobody knows about them