Re: [orca-list] Accessibility broken under Wayland Fedora 31

[Didier Spaier <didier slint fr>]

Hi,

Sorry, I have to disagree with both of you <smile>.

Le 11/11/2019 à 15:28, Michał Zegan a écrit :
> W dniu 11.11.2019 o 12:51, Halim Sahin pisze:
> > Hi,
> > I am aware that it can be configured to use dmix because I've written
> > it many times in this list and speechd lists.
> >
> > But it doesn't change the fact that pulseaudio developers do not
> > recommend to use dmix.

Where did you read that pulseaudio developers do not recommend to use
dmix? Why? And when did they make this recommendation?
Please provide links to sustain this claim of which I am not aware.

I have read on Archwiki (so not from a pulseaudio developer)  under
"ALSA/dmix without grabbing hardware device", link:
https://wiki.archlinux.org/index.php/PulseAudio#ALSA/dmix_without_grabbing_hardware_device
this "Note: This section describes alternative configuration, which is
generally not recommended." However the Arch user who wrote that don't
say why he or she why this would be "not generally recommended".
All I know is this is the default setting in Slint and nobody complained
about it so far.

> > Using dmix doesn't resolve the mentioned usb headset problem as well.

I fail to see how this issue is related to the other one.
Anyway a solution is proposed in ArchWiki, link:
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Automatically_switch_to_Bluetooth_or_USB_headset
Did you try it?

> Please never say that you solved an issue when it was in fact a
> workaround. Even worse, an unrecommended workaround. And I don't believe
> they didn't recommend it for a reason. So, these issues are not and were
> never fixed, they are just something that can be at least partially
> worked around.

If they did recommend it for the reason, this reason should be stated.
Where has it been stated? Me, I will never follow a technical advice
given without a stated rationale that I can (try to) understand.

Anyway this is the Orca mailing list, not a Fedora or PulseAudio mailing
list, and I very much doubt that posting about these issue here will
make either the developers of PulseAudio or the maintainers of Fedora
aware of it, let alone take care of it as they probably won't read this
thread and even if they do, the will probably want to have it stated
instead in some kind of bug tracker or issues list.

Best regards,

Didier