That's very interesting and further raises the question of what is

causing the problem.

Gene

On 1/20/2022 8:30 AM, Don H wrote:

> Tried as you described by placing a new entry in the default dictionary.

>  Still says capital when typing a capital letter.  I know the entry was

> correct because if you type the word cap in a document and try to read

> it NVDA says nothing.

> 

> On 1/20/2022 8:14 AM, Gene wrote:

>> Here is a suggestion for those who don't want to hear cap spoken.  Try

>> an NVDA speech dictionary entry for cap and place a space in the

>> pronounced as field.  Be sure to select whole word or you won't hear cap

>> wherever it appears.  Thus, Captain Kirk would be tain Kurk.

>> 

>> 

>> On a more general note, I don't understand the cause of the problem.  I

>> would think that when a capital letter is found, NVDA sends instructions

>> to the synthesizer such as raise voice, or actually sends the word cap

>> to the synthesizer.  But turning off these options doesn't eliminate the

>> word cap being spoken for some people and now one person says pitch

>> isn't raised.

>> 

>> 

>> Yet, I wouldn't think the synthesizer would do something on its own like

>> say cap if no information came from NVDA.  Perhaps someone with more

>> technical knowledge might discuss what might be causing the problems.

>> 

>> 

>> Gene

>> 

>> On 1/20/2022 8:04 AM, Don H wrote:

>>> I contacted Code Factory and they said it was a NVDA issue.  So I don't

>>> think anything will be done anytime soon to fix the problem.

>>> 

>>> On 1/20/2022 12:17 AM, Marilyn and Don Bilderback wrote:

>>>> Hello,

>>>> 

>>>> I have the beep option checked but I get no sound when I type.

>>>> 

>>>>   I try to use the tone option, but   can’t seem to choose the   right

>>>> numbers so I can use that method. I don’t hear   any change in tone

>>>> when

>>>> caps are typed.

>>>> 

>>>> I do not like the word caps spoken as I can’t hear what I am typing.

>>>> What am I missing?

>>>> 

>>>> Marilynn

>>>> 

>>>> 

>>> 

>>> 

>>> 

>>> 

>>> 

>> 

>> 

>> 

>> 

>> 

> 

> 

>

> 

> 

> .

I think something's wrong "out there in the cloud."  

I just tried the same thing with Add-On Updater Version 21.09, and got the same error.  After removing that version of the add-on, I cannot download the latest version, which is 22.01.  I am getting a "502 Bad Gateway" error when attempting to fetch the latest Add-On Updater from:  https://addons.nvda-project.org/files/get.php?file=nvda3208 

I'm going to send a quick email message to the folks at NVAccess.  I'd just wait a while and try later.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 

Tried as you described by placing a new entry in the default dictionary.
 Still says capital when typing a capital letter.  I know the entry was
correct because if you type the word cap in a document and try to read
it NVDA says nothing.

On 1/20/2022 8:14 AM, Gene wrote:

Here is a suggestion for those who don't want to hear cap spoken.  Try
an NVDA speech dictionary entry for cap and place a space in the
pronounced as field.  Be sure to select whole word or you won't hear cap
wherever it appears.  Thus, Captain Kirk would be tain Kurk.


On a more general note, I don't understand the cause of the problem.  I
would think that when a capital letter is found, NVDA sends instructions
to the synthesizer such as raise voice, or actually sends the word cap
to the synthesizer.  But turning off these options doesn't eliminate the
word cap being spoken for some people and now one person says pitch
isn't raised.


Yet, I wouldn't think the synthesizer would do something on its own like
say cap if no information came from NVDA.  Perhaps someone with more
technical knowledge might discuss what might be causing the problems.


Gene

On 1/20/2022 8:04 AM, Don H wrote:

I contacted Code Factory and they said it was a NVDA issue.  So I don't
think anything will be done anytime soon to fix the problem.

On 1/20/2022 12:17 AM, Marilyn and Don Bilderback wrote:

Hello,

I have the beep option checked but I get no sound when I type.

  I try to use the tone option, but   can’t seem to choose the   right
numbers so I can use that method. I don’t hear   any change in tone when
caps are typed.

I do not like the word caps spoken as I can’t hear what I am typing.
What am I missing?

Marilynn

.

Here is a suggestion for those who don't want to hear cap spoken.  Try
an NVDA speech dictionary entry for cap and place a space in the
pronounced as field.  Be sure to select whole word or you won't hear cap
wherever it appears.  Thus, Captain Kirk would be tain Kurk.


On a more general note, I don't understand the cause of the problem.  I
would think that when a capital letter is found, NVDA sends instructions
to the synthesizer such as raise voice, or actually sends the word cap
to the synthesizer.  But turning off these options doesn't eliminate the
word cap being spoken for some people and now one person says pitch
isn't raised.


Yet, I wouldn't think the synthesizer would do something on its own like
say cap if no information came from NVDA.  Perhaps someone with more
technical knowledge might discuss what might be causing the problems.


Gene

On 1/20/2022 8:04 AM, Don H wrote:

I contacted Code Factory and they said it was a NVDA issue.  So I don't
think anything will be done anytime soon to fix the problem.

On 1/20/2022 12:17 AM, Marilyn and Don Bilderback wrote:

Hello,

I have the beep option checked but I get no sound when I type.

  I try to use the tone option, but   can’t seem to choose the   right
numbers so I can use that method. I don’t hear   any change in tone when
caps are typed.

I do not like the word caps spoken as I can’t hear what I am typing.
What am I missing?

Marilynn

I contacted Code Factory and they said it was a NVDA issue.  So I don't
think anything will be done anytime soon to fix the problem.

On 1/20/2022 12:17 AM, Marilyn and Don Bilderback wrote:

Hello,

I have the beep option checked but I get no sound when I type.

  I try to use the tone option, but   can’t seem to choose the   right
numbers so I can use that method. I don’t hear   any change in tone when
caps are typed.

I do not like the word caps spoken as I can’t hear what I am typing.
What am I missing?

Marilynn

Hello,

I have the beep option checked but I get no sound when I type.

 I try to use the tone option, but   can’t seem to choose the   right
numbers so I can use that method. I don’t hear   any change in tone when
caps are typed.

I do not like the word caps spoken as I can’t hear what I am typing.
What am I missing?

Marilynn

Dear Tony,
Edit: I suggest packaging sound split and volume adjustment
functionality in a stand-alone add-on.
Thanks.
On 1/19/22, Bhavya shah <bhavya.shah125@...> wrote:

Dear Tony,

Have you considered packaging the Sound Split functionality as a
separate add-on? I think it is a particularly distinct piece of
functionality which merits its own add-on. I am happy to sketch some
arguments for it if needed. In my case, I don't care for the enhanced
table navigation features and the key bindings it occupies (which I am
guessing are instated by default and yes, which I could take some time
to remove) but certainly do care for the ability to delineate NVDA and
non-NVDA audio. Alternatively, I might suggest having a series of
check boxes to enable or disable logically constructed subsets of
functionality in one, unified Tony's Enhancements add-on.

Thanks.

On 1/14/22, Tony Malykh <anton.malykh@...> wrote:

Are you dealing with extremely long lines? Could you email me your file?

I just tried a file with 4000 lines and there is no perceptible delay
when using WordNav 1.7 in VSCode.

On 1/13/2022 4:22 PM, Bruno Aníbal Prieto González wrote:

Hi,
Thanks for replying. Yes, I have word nav 1.7 installed. In large
files like 400 lines for example, it takes a couple of seconds to say
the word. Is there anything extra to do? I imagine it must be
something complex

2022-01-12 15:44 GMT-03:00, Tony Malykh <anton.malykh@...>:

Have you tried the latest version of WordNav? I improved its
performance
in VSCode.

On 1/12/2022 4:31 AM, Bruno Aníbal Prieto González wrote:

Hi Tony!
Thank you so much for your awesome complements. Especially I am really
appreciating the noticeable improvement of indent nav speed in VS
Code. It's great!
I wonder if that improvement in the indent nav algorithm will be
transferable to Word Nav? VS Code doesn't behave as I would like when
navigating with Control and arrows, but with Word Nav it does. The
problem is that in larger files Word Nav causes NVDA to take a long
time to read the words.
Do you think there is a way to fix that related to how you did it with
Indent Nav?

Have a great year!

2022-01-11 17:19 GMT-03:00, abdul muhamin <abdulmuhamin600@...>:

Hello there, I’m facing a strange issue in  browser nav 2.2, whenever
I
try
to use NVDA OCR, the up and down aero keys doesn’t work, at 1st, I
thaught
it’s the problem in the latest version of NVDA, and I downgraded to
2021.3,
but the problem was still there, then I restarted my NVDA with addons
disabled, and the keys were working properly, then, I enabled the
addons
1
by 1, and I found this bug with Browser nav addon, please fix it.



Sent from Mail for Windows



From: David Ingram
Sent: Monday, January 10, 2022 8:48 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Tony's add-ons: updates and new features



I’d like to know how to get rid of ad-ons that are not compatible
with
the
latest version of nvda?  thank you.

On Jan 4, 2022, at 5:39 PM, Rowen Cary <manchen_0528@...>
wrote:



Hello,

Thanks Tony, your add-on is very useful to me, thank you for your
great
creation. For sound segmentation, is it possible to place the NVDA
sound
separately on the left or right channel without changing the
multimedia
sound? This is useful for enjoying stereo resources.

Thanks again

--
Best Regards,
Bhavya Shah
Stanford University | Class of 2024
LinkedIn: https://www.linkedin.com/in/bhavyashah125/

NVDA Menu > Preferences > Settings > Tony's enhancements  settings > Edit language map
On 1/18/2022 6:13 PM, Martin J. Dürst wrote:

I installed the nvda-tonys-enhancements add-on. But I didn't find the settings dialog anywhere. I checked the log, and I didn't find any related errors. The settings dialog of the sentenceNav is available without problems. Help is appreciated.

Regards,   Martin.