Date   

Re: addon updater 22.01

 

Hi all,

Things should be back to normal.

Cheers,

Joseph


Re: no settings pannel for nvda-tonys-enhancements (was: Re: [nvda] Ms Russian Voices and NVDA)

Tony Malykh
 

The old style was to keep settings under preferences directly. New style suggests to put them under Preferences>Settings. I finally moved configuration dialogs of all my add-ons to conform with the new style.

On 1/19/2022 10:04 PM, Martin J. Dürst wrote:
Hello Tony, others,

Many thanks for your advice; I found the settings.

More generally, what's the rule for where to put add-on settings? sentenceNav is under Preferences, but Tony's enhancement is under Preferences > Settings. Why the difference?

Regards,   Martin.

On 2022-01-20 05:28, Tony Malykh via groups.io wrote:
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.




Re: Tony's add-ons: updates and new features

Tony Malykh
 

Thanks for feedback. Yes, in theory this can be done, but I am hesitating to do this myself because of increasing release engineering cost. Currently I maintain 10 separate add-ons and every year it is quite a tedious job to update all of them. I also made Tony's enhancement modular so that each feature can be turned on or off separately. However I have no problem if you or anyone else wants to cut out this part and fork it as a separate add-on.

On 1/19/2022 6:39 PM, Bhavya shah wrote:
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/


Re: addon updater 22.01

Curtis Delzer
 

I receive the same "error" and then some about "instruction . . ."

On 1/20/2022 9:06 AM, farhan israk wrote:
i am using windows 10 21h2, nvda 2021.3.1 and addon updater 22.01. I am not able to check update. If I try to check update, it shows error updating addon. Only this message. No error code or edditional  message.
-- 
Curtis Delzer
H.S.
K6VFO
curtis@...


Re: NVDA announcing Capital letters

Chris Mullins
 

Hi

Can speech viewer be used to check what is being sent to the synthesizer?

 

Cheers

Chris

 

Sent from Mail for Windows

 

From: Gene
Sent: 20 January 2022 15:03
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA announcing Capital letters

 

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

>>>> 

>>>> 

>>> 

>>> 

>>> 

>>> 

>>> 

>> 

>> 

>> 

>> 

>> 

>

> .

 

 

 

 

 


Re: addon updater 22.01

 

Hi,

Yep, I'm getting bad gateway (HTTP error 502) also.

For people needing it, the direct download link for Add-on Updater 22.01 is: https://github.com/josephsl/addonUpdater/releases/download/22.01/addonUpdater-22.01.nvda-addon

Cheers,

Joseph


Re: addon updater 22.01

Brian Sackrider
 

    I think that there is somthing wrong in the cloud also.  When I check for add on updates and also if I check for updates in the help menu iI get the same error message.  Error checking for updates.  It seems to be efecting both add on updates and nvda updates as well.

Briansackrider

On 1/20/2022 12:58 PM, Brian Vogel wrote:
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)

 


Re: addon updater 22.01

 

By the way, even trying to get to NVAccess.org is currently giving a 502.

This will almost certainly be resolved later in the day. 
--

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)

 


Re: addon updater 22.01

 

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)

 


addon updater 22.01

farhan israk
 

i am using windows 10 21h2, nvda 2021.3.1 and addon updater 22.01. I am not able to check update. If I try to check update, it shows error updating addon. Only this message. No error code or edditional  message.


Re: Using hyper-v manager with nvda

Russell James
 

Hi Sean

Thanks for your reply

I'm baffled that the hyper-v manager is what seems to be completely accessible on one machine and totally inaccessible on another..

I've never really used VMware but I have used virtualbox for many years.

Russ


On Wed, Jan 19, 2022, 10:30 PM Shaun Everiss <sm.everiss@...> wrote:
Fiddled with hyper v but never got it working though I didn't try that hard.
To be honest after the drama I have had with vmware, I am loathed to
try again unless I have a waste machine.
Technically I have a waste machine but I don't know if I really care to bother.

On 20/01/2022, Russell James <4rjames@...> wrote:
> Greetings
>
> I'm trying to use hyper-v manager on Windows 10 and on a desktop it is
> accessible however on a laptop that I'm using it does not speak at all and
> I'm using the same version of nvda on both systems.
>
> I wanted to reach out to the group to see if anyone has run into this
> before and if anyone has any suggestions on how to make hyper-v manager
> more accessible with nvda.
>
> Thank you
>
> Rus
>
>
>
>
>
>






Re: NVDA announcing Capital letters

Gene
 

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










.


Re: NVDA announcing Capital letters

Chris
 

You are probably better off raising an issue on GitHub, if its an NVDA issue, giving more information than you have here will probably help diagnose the problem

 

 


Re: NVDA announcing Capital letters

Don H
 

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







Re: NVDA announcing Capital letters

Gene
 

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




Re: NVDA announcing Capital letters

Don H
 

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


Re: NVDA add-on CloudVision

juergenkohler23@...
 

Hello alexey,
 
I have also tested your new addon version in the meantime. However, it does not work for me. I don't get any message announced.
With the old version, the image recognition on the internet worked, i.e. it is probably due to the navigator object.
If anyone else has a tip on how the new version works, I would be very grateful!


Re: NVDA add-on CloudVision

alexey
 

Yes, this problem sometimes happens, just try a few times after a few minutes, or select a file where the size is smaller


Re: Tony's add-ons: updates and new features

Simone Dal Maso
 

Hello,
I perhaps am the only person that think that there is no need for packaging another addon for sound.

Infact we will have a copy of the Volume Adjustment addon... that allow both to modify NVDa volume and app volume, both split sound where you want. So, I prefer to have all in a single addon that make more things.

Il 20/01/2022 03:39, Bhavya shah ha scritto:
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 announcing Capital letters

Marilyn and Don Bilderback
 

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

8021 - 8040 of 99861