Re: [BRLTTY] Problems when using brltty in the terminal
Hi, On Sun, May 09, 2021 at 04:35:27PM -0400, Dave Mielke wrote: > [quoted lines by Christian Schoepplein on 2021/05/09 at 22:04 +0200] > > >It would be really cool if you have another idea that could help. > > The AtSpi2 screen driver used to have a focus parameter which could > contrain it to terminal windows. We dropped that parameter when brlapi > priorities were introduced because that let tee AtSpi2 screen driver > drop its content quality when not on a terminal window, thus giving > brlapi preference to Orca. We didn't consider the possibility that > Orca wouldn't be using that brltty's brlapi interface. We could, > therefore, restore the focus parameter, but, for you, that'd mean > either waiting for 6.4 or using a development release. Of course, I'd > prefer that you'd use a development release so tat you can test it. > :-) Please let me know if the patch is in the development repo so I could test that as well. My brltty 6.0 doesn't have the double speech problem but other speech related problems which I hope to get a workarround with a new brltty version. Unfortunately we use Ubuntu 20.04 LTS at work and I couldn't find a ppa with newer Version of brltty so I have to build it myself. Thx in Advance Regards Halim ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty
Re: [BRLTTY] Problems when using brltty in the terminal
Hi, I would be intersting to test our accessibility stuff with pipewire which will replace pulseaudio. @Christian: If you don't need pulseaudio switch back to alsa and use libao output driver. Running pulseaudio through dmix has some disadvantages if you want to use usb headsets. Dmix will break Autoswitching of audio output. HTH. Halim ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty
Re: [BRLTTY] Problems when using brltty in the terminal
Hi Didier, > Am 09.05.2021 um 22:28 schrieb Didier Spaier : > 1. pulseaudio is only started on demand (when an application requires it) > 2. pulseaudio is set to use the the dmix mixer, so ends all streams go to alsa > through via this mixer. From our /etc/pulse/default.pa: > > ### In Slint, we want to share audio resources between speech apps that > ### rely on alsa and other apps that rely on pulseaudio. > load-module module-alsa-sink device=dmix > load-module module-alsa-source device=dsnoop > > 3. We include nothing in alsa configuration that redirect streams to > pulseaudio. > > All that not starting pulseaudio system wide. Are the changes in /etc/pulseaudio/default.pa the only necessary changes I have to perform on a standard Debian system, or are there other things I have to do? If yes, I’ll try it on a fresh Debian Bullsey installation. I am curious if the setup is working and if latency is really that big that it might be a problem. Cheers, Schoepp ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty
Re: [BRLTTY] Problems when using brltty in the terminal
Hi Dave, > Am 09.05.2021 um 22:35 schrieb Dave Mielke : > > [quoted lines by Christian Schoepplein on 2021/05/09 at 22:04 +0200] > >> It would be really cool if you have another idea that could help. > > The AtSpi2 screen driver used to have a focus parameter which could contrain > it to terminal windows. We dropped that parameter when brlapi priorities were > introduced because that let tee AtSpi2 screen driver drop its content quality > when not on a terminal window, thus giving brlapi preference to Orca. We > didn't consider the possibility that Orca wouldn't be using that brltty's > brlapi interface. We could, therefore, restore the focus parameter, but, for > you, that'd mean either waiting for 6.4 or using a development release. Of > course, I'd prefer that you'd use a development release so tat you can test > it. :-) I’d be happy to test also a development release, if compiling it is not to complicated ;-). Just let me know if there is is something ready to test and where to get it ;-). Thank you all for your great support and ideas to help me with the setup I have on mind and I’d like to test to have a good working environment for hopefully the next years. Cheers, Schoepp ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty
Re: [BRLTTY] Problems when using brltty in the terminal
Hi Dave, > Am 09.05.2021 um 21:45 schrieb Dave Mielke : > > [quoted lines by Christian Schoepplein on 2021/05/09 at 21:29 +0200] > >> OK; then the only solution currently is to use an older brltty version if I >> like to have a setup with speech support enabled for brltty in the Mate >> terminal? Is this right? > > Maybe. Another possibility might be to tell Orca to ignore termiinal windows. > I don't know if that's possible. Or, maybe, I have this backward. Is the > problem that you're getting double speech when you are or aren't in a > terminal window? I have this double speech when I am _not_ in the terminal window. > There were several problems with the AtSpi2 screen driver which have been > fixed recently (in 6.2, I think). That might be a reason to upgrade even > further. Sorry, I forgot to mension that I am using the latest release canidate of Debian Bullseye. It has brltty 6.3 included. It would be really cool if you have another idea that could help. Ciao, Schoepp ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty
Re: [BRLTTY] Problems when using brltty in the terminal
Hi Chistian, Le 09/05/2021 à 23:17, Christian Schoepplein a écrit : Are the changes in /etc/pulseaudio/default.pa the only necessary changes I have to perform on a standard Debian system, or are there other things I have to do? If yes, I’ll try it on a fresh Debian Bullsey installation. I am curious if the setup is working and if latency is really that big that it might be a problem. It's hard for me to answer, as I don't have a Debian installed. If memory serves, you'd have to check the alsa configuration as some settings rely on pulseaudio, which should be avoided. I could install Debian in a VM to check but that won't be soon, as I am pretty busy right now. Meanwhile you could install Slint (in a VM?) and check if the latency is acceptable. Cheers, Didier ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty
Re: [BRLTTY] Problems when using brltty in the terminal
Dave Mielke, le dim. 09 mai 2021 16:45:26 -0400, a ecrit: > [quoted lines by Samuel Thibault on 2021/05/09 at 22:39 +0200] > > >Again, the Braille part is working completely fine. > > > >The problem raised here is *speech* only. > > I'm being slow on this one. Is what's wanted, when not on a terminal window, > that Orca renders the speech but brltty renders the braille? No. The problem is with non-terminal windows. Brltty's speech driver is still getting content from the atspi2 driver, even if with SCQ_POOR level, and speaks it, in parallel of Orca doing its own speak. The simplest would be to just add an option to make the atspi2 screen driver not always return content, event at poor level, if it's not of the desired type. Another, more complex way would be to add an option to make brltty's speech only emit messages when the screen driver reports having good quality. Another, yet more complex way would be to add to speech dispatcher a notion of overriding priority. Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty
Re: [BRLTTY] Problems when using brltty in the terminal
[quoted lines by Samuel Thibault on 2021/05/09 at 22:39 +0200] >Again, the Braille part is working completely fine. > >The problem raised here is *speech* only. I'm being slow on this one. Is what's wanted, when not on a terminal window, that Orca renders the speech but brltty renders the braille? If so, what if we add something like a minType parameter? -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: d...@mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 | ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty
Re: [BRLTTY] Problems when using brltty in the terminal
Dave Mielke, le dim. 09 mai 2021 16:35:27 -0400, a ecrit: > We didn't consider the possibility that Orca wouldn't be using that brltty's > brlapi interface. Again, the Braille part is working completely fine. The problem raised here is *speech* only. Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty
Re: [BRLTTY] Problems when using brltty in the terminal
[quoted lines by Christian Schoepplein on 2021/05/09 at 22:04 +0200] >It would be really cool if you have another idea that could help. The AtSpi2 screen driver used to have a focus parameter which could contrain it to terminal windows. We dropped that parameter when brlapi priorities were introduced because that let tee AtSpi2 screen driver drop its content quality when not on a terminal window, thus giving brlapi preference to Orca. We didn't consider the possibility that Orca wouldn't be using that brltty's brlapi interface. We could, therefore, restore the focus parameter, but, for you, that'd mean either waiting for 6.4 or using a development release. Of course, I'd prefer that you'd use a development release so tat you can test it. :-) -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: d...@mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 | ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty
