Hi Sharon and Sarah, what I did was exit NVDa while I was in a meeting. When I wanted out I would start it or Jaws to exit the meeting. I myself would just go into the settings and find all this out. I’ve used my I pad to go into a meeting and just double tap to turn off speech. I prefer using the I pad for those kinds of meetings. Each to their own.  If I use this computer I exit the screen reader so I do not hear so and so entered the room or left.  Same with the I phone. I just double tap and that turns off speech. I don’t know how you’d do it on a tablet that’s not apple.  Or google phone.    

Sent from Mail for Windows

hi friends

greetings from Nepal,

can we stop nvda from announcing the ms teams alerts while we are in a meeting?

thank you,

--

Dr. Sharad Koirala

Lecturer

Department of Community Medicine

Gandaki Medical College, Pokhara, Nepal

On Fri, Jan 21, 2022 at 01:02 PM, Don H wrote:

Nothing changed.

-
Well, if you've checked the NVDA speech log, and it is not sending "Cap"
prior to the letter to the synth when reading letter by letter and
encountering a capital, it seems well nigh impossible that it's not
related to the synth.

Mind you, it could be an idiosyncratic corruption in that software.  But
if you've already done the equivalent of an uninstall/reinstall on that,
there's not much more you can do.

If they won't believe there's an issue when the speech log shows that
what's being sent to the synth doesn't match what it's actually saying,
I don't know what could.
--

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)

On Fri, Jan 21, 2022 at 12:50 PM, Don H wrote:

The response I got from Code Factory was that it was a NVDA issue
which means they ain't gona do anything to fix the issue with Vocalizer.

-
Which, while unfortunate, is not at all unusual.

The, "It's not MY fault, THEY need to fix it!," game is very common in
the tech support world.  Very often it falls to the end user to compile
enough evidence to have a definitive case to lodge with whoever ends up
being "the guilty party."

As I said earlier, and others have echoed, we still don't have a
definitive answer regarding what's at fault.  But if it's not an NVDA
add-on, if other users of NVDA and the Code Factory Vocalizer do not
have this issue, all signs point to an idiosyncratic issue on your
machine.  This is not uncommon, at all.  Hence the reason I suggest a
full uninstall and reinstall of NVDA after Add-On involvement has been
ruled out.  And I do mean a full uninstall of the software, not your
settings, not updating NVDA from within if an update were to happen to
be available.  Get a copy of NVDA "from scratch."

Diagnosis in situations like this is often a long process of
elimination.  And sometimes the diagnostic process itself ends up fixing
the issue.
--

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)

Hi how much does the vocalizer and eloquence add0on cost?

Kind regards,

Kenny Peyatt jr.

To the Membership:

I left this topic open because I wanted those who wished to extend their well-wishes to Don to be able to do so.  And I am still allowing it to remain open for that purpose.

The above being said, I do not want this to spiral into a "Covid Debate" and/or "Covid Politics" topic.  Let's not go there.  If it does continue to look like it's taking that turn I will lock the topic.
--

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)

 

On Fri, Jan 21, 2022 at 11:57 AM, Steve Nutt wrote:

Synths interpret this differently, and Vocalizer will tell you it is
a capital.

-
So my earlier theory about this possibly being a synth issue (Message
#92056) <https://nvda.groups.io/g/nvda/message/92056> turns out to be right!

I really didn't expect that outcome for this specific circumstance, but
heaven knows weirder things have happened.

--

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)

It is part and part.

When the synth sees an upper case letter, it says the word capital, which is correct of course.

Even if you turn off capitals in NVDA, it still throws upper case letters.

So the fix in NVDA would be that NVDA should send all letters entered via the keyboard as lower case irrespective of their case, if that setting is switched off.

In this case, I think the synth is right, and NVDA is wrong, but what do I know.

All the best

Steve

--
To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

Computer Room Services
77 Exeter Close
Stevenage
Hertfordshire
SG1 4PW
T: +44(0)1438-742286
M: +44(0)7956-334938
F: +44(0)1438-759589
E: steve@...
W: https://www.comproom.co.uk

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: 20 January 2022 14:05
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA announcing Capital letters

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 this is because the beep option unhelpfully comes through the PC speaker, instead of your soundcard.

 

Some PCs don’t have a PC speaker any more, so the beep sound won’t work for them.

 

I think this should be changed in NVDA.

 

All the best

Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Marilyn and Don Bilderback
Sent: 20 January 2022 06:18
To: nvda@nvda.groups.io
Subject: [nvda] NVDA announcing Capital letters

 

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

Hi

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

Cheers

Chris

Sent from Mail for Windows

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

>>>> 

>>>> 

>>> 

>>> 

>>> 

>>> 

>>> 

>> 

>> 

>> 

>> 

>> 

> 

> 

>

> 

> 

> .

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 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

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

Hi,

This is because JAWS provides a script for Duxbury. Ironically an app for the blind is not natively accessible, this is strange to me.

All the best

Steve

--
To subscribe to our News and Special Offers list, go to
https://www.comproom.co.uk/subscribe

Computer Room Services
77 Exeter Close
Stevenage
Hertfordshire
SG1 4PW
T: +44(0)1438-742286
M: +44(0)7956-334938
F: +44(0)1438-759589
E: steve@...
W: https://www.comproom.co.uk

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Afnan
Nasir
Sent: 18 January 2022 12:58
To: nvda@nvda.groups.io
Subject: [nvda] Question about using NVDA with Duxbury products.

Hello, i hope that all are doing geat, well i've installed DBT (Duxbury Translator) to write braille, but unfortunately, NVDA is not providing spoken feedback while writing. i've also tried perkey duck by same author (Duxbury ) but results are same. can anyone guide me about the solution of it? i've tried it with jaws, and it is working fine, but i primarily use NVDA as a main screen reader, so i want to use it with NVDA. any help would be much appreciated.

This problem does not  appear to be existent with the Sapi versions of Eloquence.

I am using the Code Factory Sapi 5 Eloquence  to type this and there is no problem with capital announcement. Capitals are being indicated simply by increased pitch as expected.

Yesterday I was using the Kurzweil Sapi 4 version of Eloquence and again there was no  problem with simply hearing increased pitch to indicate capitals.

So this may be a problem confined to the Code Factory Addon versions?

I am constantly relieved that I did not go for the addon flavour given the multiple issues reported over the years with NVDA updates etc.

David Griffith

Sent from Mail for Windows

Hi,

This is a function, or problem with, certain synthesisers.

For example, if you use CodeFactory's NVDA Vocalizer add-on, and turn off all the capital options, it will still say Capital, because NVDA doesn't intercept the interpretation of the add-on itself.

JAWS has a feature called Controlled By Synthesiser, which you can switch off. If you do, JAWS does all the processing. Maybe NVDA needs something like this. Controlled By Synthesiser can be seen in punctuation settings I believe.

All the best

Steve

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

-----Original Message-----

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H

Sent: 18 January 2022 15:28

To: nvda@nvda.groups.io

Subject: Re: [nvda] NVDA announcing Capital letters

I have both beep and say cap unchecked under speech settings and NVDA still says capital before a capital letter and when typing a capital letter.

On 1/18/2022 7:53 AM, Fawaz Abdul rahman wrote:

> Hi,

> if you mean while typing, then yes.

> in the voice settings, you can find:

> Say cap before capitals  check box  not checked  Alt+c you can check

> it or use the beep option which is right after the cap option.

> good luck.

> 

> On Tue, Jan 18, 2022 at 4:47 PM Don H <lmddh50@...

> <mailto:lmddh50@...>> wrote:

> 

>     Is there a setting in NVDA that causes the word capital to be spoken on

>     capital letters?

> 

> 

> 

> 

> 

>