1. Nvda | Nvda
  2. Topics

Clearing TTS buffer

Abdulqadir Ahmad
 

Hi, sometimes I get lots of text in a terminal and i'm only interested in some part. It is mostly when i have an infinite loop in a code. The problem is, NVDA will try and read the output as it displays. Is it possible to clear the TTS buffer some how? Hitting ctrl is most times sluggish and it will take time before everything gets to normal. I hope i'm clear
Luke Davis
 

Abdulqadir Ahmad wrote:

Hi, sometimes I get lots of text in a terminal and i'm only interested in some part. It is mostly when i have an infinite loop in a code. The problem is,
NVDA will try and read the output as it displays. Is it possible to clear the TTS buffer some how? Hitting ctrl is most times sluggish and it will take time
Classical problem of every single talking computer setup I've ever used. Once the infinite scroll starts, getting the speech to stop and or getting other keys (like Ctrl+C) to work, is sometimes near impossible. Too many processes fighting for terminal resources.
Try accidentally doing a 50 page advance in a pager like less sometime. 1,250 lines shoved into the speech buffer in relatively short order. Good luck stopping that train.

The best approach I've ever found for this, is to silence speech _before_ you start the text that won't stop coming.

In NVDA, that's NVDA+S, maybe twice, on a US desktop layout keyboard, for silence speech.
Sometimes beeps speech mode can be useful for this kind of thing, but you might also want to mute it entirely.

NVDA really needs a "active reading only" speech mode, where it won't try to read anything that's happening on its own, but you can still use review keys.

Luke
Abdulqadir Ahmad
 

Thank you.
I think silencing NVDA might work.

Gene
 

You might be able to solve the problem by turning report dynamic content changes off.  The command is NVDA key 55.  That's 5 on the main keyboard.  issuing the command again turns it back on.  Its a toggle.

I hope it applies to what you are using.  It applies in the DOS prompt, and I would think it would apply here.

Gene

On 1/21/2023 5:03 AM, Luke Davis wrote:
Abdulqadir Ahmad wrote:

Hi, sometimes I get lots of text in a terminal and i'm only interested in some part. It is mostly when i have an infinite loop in a code. The problem is,
NVDA will try and read the output as it displays. Is it possible to clear the TTS buffer some how? Hitting ctrl is most times sluggish and it will take time
Classical problem of every single talking computer setup I've ever used. Once the infinite scroll starts, getting the speech to stop and or getting other keys (like Ctrl+C) to work, is sometimes near impossible. Too many processes fighting for terminal resources.
Try accidentally doing a 50 page advance in a pager like less sometime. 1,250 lines shoved into the speech buffer in relatively short order. Good luck stopping that train.

The best approach I've ever found for this, is to silence speech _before_ you start the text that won't stop coming.

In NVDA, that's NVDA+S, maybe twice, on a US desktop layout keyboard, for silence speech.
Sometimes beeps speech mode can be useful for this kind of thing, but you might also want to mute it entirely.

NVDA really needs a "active reading only" speech mode, where it won't try to read anything that's happening on its own, but you can still use review keys.

Luke
Gene
 

I made a typing error in the previous message.  The command is NVDA key 5.

Gene

On 1/21/2023 9:37 AM, Gene via groups.io wrote:
You might be able to solve the problem by turning report dynamic content changes off.  The command is NVDA key 55.  That's 5 on the main keyboard.  issuing the command again turns it back on.  Its a toggle.

I hope it applies to what you are using.  It applies in the DOS prompt, and I would think it would apply here.

Gene
On 1/21/2023 5:03 AM, Luke Davis wrote:
Abdulqadir Ahmad wrote:

Hi, sometimes I get lots of text in a terminal and i'm only interested in some part. It is mostly when i have an infinite loop in a code. The problem is,
NVDA will try and read the output as it displays. Is it possible to clear the TTS buffer some how? Hitting ctrl is most times sluggish and it will take time
Classical problem of every single talking computer setup I've ever used. Once the infinite scroll starts, getting the speech to stop and or getting other keys (like Ctrl+C) to work, is sometimes near impossible. Too many processes fighting for terminal resources.
Try accidentally doing a 50 page advance in a pager like less sometime. 1,250 lines shoved into the speech buffer in relatively short order. Good luck stopping that train.

The best approach I've ever found for this, is to silence speech _before_ you start the text that won't stop coming.

In NVDA, that's NVDA+S, maybe twice, on a US desktop layout keyboard, for silence speech.
Sometimes beeps speech mode can be useful for this kind of thing, but you might also want to mute it entirely.

NVDA really needs a "active reading only" speech mode, where it won't try to read anything that's happening on its own, but you can still use review keys.

Luke
Travis Siegel
 

Agreed.

The method that (usually) works for me is to alt tab away from the offending terminal window, wait for NVDA to stop, then alt tab back, quickly hitting control or shifting to no speech (as Luke suggested) before switching back, then doing whatever it is that will stop the scrolling.

The key here is to switch away from the terminal with the infinite scroll.  If you don't do that, you're not likely to get a word in edgewise until things are royally screwed, and by then, it's usually NVDA crashing and restarting that stops the scroll (however temporarily).

Hope this helps.

On 1/21/2023 6:03 AM, Luke Davis wrote:
Abdulqadir Ahmad wrote:

Hi, sometimes I get lots of text in a terminal and i'm only interested in some part. It is mostly when i have an infinite loop in a code. The problem is,
NVDA will try and read the output as it displays. Is it possible to clear the TTS buffer some how? Hitting ctrl is most times sluggish and it will take time
Classical problem of every single talking computer setup I've ever used. Once the infinite scroll starts, getting the speech to stop and or getting other keys (like Ctrl+C) to work, is sometimes near impossible. Too many processes fighting for terminal resources.
Try accidentally doing a 50 page advance in a pager like less sometime. 1,250 lines shoved into the speech buffer in relatively short order. Good luck stopping that train.

The best approach I've ever found for this, is to silence speech _before_ you start the text that won't stop coming.

In NVDA, that's NVDA+S, maybe twice, on a US desktop layout keyboard, for silence speech.
Sometimes beeps speech mode can be useful for this kind of thing, but you might also want to mute it entirely.

NVDA really needs a "active reading only" speech mode, where it won't try to read anything that's happening on its own, but you can still use review keys.

Luke
Bob Cavanaugh
 

This is a question I'd like to know the answer to as well. In my case,
when I'm trying to check or submit a program, NVDA says
"connecting........... uploading........... connecting........." and
on and on. If I hit control too late, I don't get the results I need
to hear, but if I hit control too soon, I have to sit through and
listen to all of that.

On 1/21/23, Abdulqadir Ahmad <2004a3abuahmad@...> wrote:
Hi, sometimes I get lots of text in a terminal and i'm only interested in
some part. It is mostly when i have an infinite loop in a code. The problem
is, NVDA will try and read the output as it displays. Is it possible to
clear the TTS buffer some how? Hitting ctrl is most times sluggish and it
will take time before everything gets to normal. I hope i'm clear
Brian's Mail list account
 

I've also noticed sometimes if you really want to hear the whole of the text on a screen with nvda/b, some programs can get into a mode where part of the page are repeated for ever, so its hard to get any idea of what is the top and what is the bottom. Luckily in this case, you can stop it, but it does need a less dumb implementation as nvda when you are using it normally, tends to only give you what it thinks are text items related to controls, and on particularly Windows screens you can find hidden text you only know about in this way. Then you can figure out which navigation mode to use to get at it.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Bob Cavanaugh" <cavbob1993@...>
To: <nvda@nvda.groups.io>
Sent: Saturday, January 21, 2023 7:53 PM
Subject: Re: [nvda] Clearing TTS buffer


This is a question I'd like to know the answer to as well. In my case,
when I'm trying to check or submit a program, NVDA says
"connecting........... uploading........... connecting........." and
on and on. If I hit control too late, I don't get the results I need
to hear, but if I hit control too soon, I have to sit through and
listen to all of that.

On 1/21/23, Abdulqadir Ahmad <2004a3abuahmad@...> wrote:
Hi, sometimes I get lots of text in a terminal and i'm only interested in
some part. It is mostly when i have an infinite loop in a code. The problem
is, NVDA will try and read the output as it displays. Is it possible to
clear the TTS buffer some how? Hitting ctrl is most times sluggish and it
will take time before everything gets to normal. I hope i'm clear
Abdulqadir Ahmad
 

Hi. Two things.
1. With regards to the infinite output, I think Gene's works best in my case. Change report dynamic content to off, run the program, stop it, then bring back report dynamic content. It stops for a couple of seconds but it's faster than switching tabs. Turning off speach didn't work for me. Maybe because the console addon i'm using is still active.
2. Bob, I think using review cursor might help in your case.

Gene
 

My idea wasn't to turn it on again, but perhaps for what you are doing that is a good way.  I was thinking of having it off and reviewing the screen by reviewing the current object. 

Gene

On 1/22/2023 1:42 PM, Abdulqadir Ahmad wrote:

Hi. Two things.
1. With regards to the infinite output, I think Gene's works best in my case. Change report dynamic content to off, run the program, stop it, then bring back report dynamic content. It stops for a couple of seconds but it's faster than switching tabs. Turning off speach didn't work for me. Maybe because the console addon i'm using is still active.
2. Bob, I think using review cursor might help in your case.


1 - 10 of 10