Is there an addon for this client? I did not see one on the addon page.

******
Jesus says, follow me and I'll help you through the rough spots.
the world says, hey come with me. My way is broad and easy. So what if you get crap on your shoes. You can always wash it off, can't you!______

 

Family times Theatre
http://familytimes.wrighthere.net:9244/stream
Ask your smart speaker to play Family Times on tune-in

Is there an addon for this client? I did not see one on the addon page.

******
Jesus says, follow me and I'll help you through the rough spots.
the world says, hey come with me. My way is broad and easy. So what if you get crap on your shoes. You can always wash it off, can't you!______

 

Family times Theatre
http://familytimes.wrighthere.net:9244/stream
Ask your smart speaker to play Family Times on tune-in

Try being in focus mode when changing slides. That would be my suggestion.
As focus mode, nvda does not intercept space or page down etc. Are you
presenting these via PowerPoint or via a web browser. I have never, hope to
never, do a slide via a web browser, that would be a bit messey IMHO.



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sylvie
Duchateau
Sent: Tuesday, April 5, 2022 1:51 AM
To: Nvda List <nvda@nvda.groups.io>
Subject: [nvda] Sharing screen with Zoom or Microsoft Teams and NVDA



Hello all,

I regularly have to share my screen in Zoom or Microsoft Teams to present
slide content in HTML.

I used Firefox but I encountered problems, described below, and I then
tried
to use Chrome, but the problems occur as well.

For both browsers, I have the updated versions and I use NVDA 2021.3.5.

I encounter some problems with screen sharing with NVDA in Zoom, sometimes
as well in Microsoft Teams.

When screen sharing is on, some browser commands do not work anymore. For
example, pressing the space bar to show the next slide or typing an URL in
the address bar. The browser does not respond, or I can read things with
the
braille display that are updated but people I am talking to see older parts
of the slides.

Sometimes, only pressing Windows and M to access the desktop does not work
anymore.

When screen sharing is disabled again or when NVDA is not in use (for my
colleagues, for example), the problem of screen sharing and the lack of
responsiveness in the browser does not occur.

Has anybody encountered issues with screen sharing with Zoom, Microsoft
Teams and NVDA?

Thank you for any experience you may have.

Best

Sylvie

Before you decide whether to purchase voices, don't overlook the Microsoft One Core Voices.  The ones on my machine, three American voices, have better speech than the Vocalizer voices.  I haven't tried other voices but I think the voices, at least the ones I've heard, deserve more attention.

Gene

Respectfully, you might not have seen this in my initial response, but again, Vocalizer is not the easiest for me to understand. I wanted to possibly purchase it earlier, yes, that's true, but it would only be used as a backup as a last resort in case some reason Eloquence from CF was to spaz out on me.


Chris.

On 4/5/2022 6:30 PM, Rui Fontes wrote:

Vocalizer and Vocalizer Expressive from Tiflotecnia are already ready to NVDA 2022.1...


Cumprimentos,

Rui Fontes
Tiflotecnia, Lda.


Às 23:10 de 05/04/2022, Christopher-Mark Gilland escreveu:

Please tell me you're kidding! If so, there went my days of using NVDA, as though a lot say ESpeak is very clear, I have a profound hearing loss, and I do mean, profound. Like, 75 percent loss in one ear, and 80 in the other. Even with my hearing aids, I cannot understand ESpeak. Even Vocalizer is somewhat difficult. That's the main reason I bought the CF version of Eloquence. Obviously, I want to be legit! That's about the only synth I'm able to understand. I know a lot hate it worth a purple and pink passion, but it's what since the very very very early 2000's I've grown used to, so now, unfortunately, it's about all I can understand.


Please devs, don't do this, if so! You'll definitely lose a user if you do, and I'd hate that.


Chris.

On 4/5/2022 5:59 PM, Don H wrote:

So it appears that the latest beta of NVDA will not work with the code factory vocalizer/eleoquinse addon. Is this going to be true when the next released version of NVDA is available?

.

Respectfully, you might not have seen this in my initial response, but again, Vocalizer is not the easiest for me to understand. I wanted to possibly purchase it earlier, yes, that's true, but it would only be used as a backup as a last resort in case some reason Eloquence from CF was to spaz out on me.


Chris.

On 4/5/2022 6:30 PM, Rui Fontes wrote:

Vocalizer and Vocalizer Expressive from Tiflotecnia are already ready to NVDA 2022.1...


Cumprimentos,

Rui Fontes
Tiflotecnia, Lda.


Às 23:10 de 05/04/2022, Christopher-Mark Gilland escreveu:

Please tell me you're kidding! If so, there went my days of using NVDA, as though a lot say ESpeak is very clear, I have a profound hearing loss, and I do mean, profound. Like, 75 percent loss in one ear, and 80 in the other. Even with my hearing aids, I cannot understand ESpeak. Even Vocalizer is somewhat difficult. That's the main reason I bought the CF version of Eloquence. Obviously, I want to be legit! That's about the only synth I'm able to understand. I know a lot hate it worth a purple and pink passion, but it's what since the very very very early 2000's I've grown used to, so now, unfortunately, it's about all I can understand.


Please devs, don't do this, if so! You'll definitely lose a user if you do, and I'd hate that.


Chris.

On 4/5/2022 5:59 PM, Don H wrote:

So it appears that the latest beta of NVDA will not work with the code factory vocalizer/eleoquinse addon. Is this going to be true when the next released version of NVDA is available?

.

So it appears that the latest beta of NVDA will not work with the code factory vocalizer/eleoquinse addon.  Is this going to be true when the next released version of NVDA is available?





.

Maybe another idea is to have a review of the most popular addons to see
if it would be a good idea to incorporate them into the NVDA code.

On 4/5/2022 6:33 PM, Brian Vogel wrote:

On Tue, Apr 5, 2022 at 07:27 PM, Don H wrote:

    I would hope that the NVDA developers do their best to not break
    addon's while at the same time keep NVDA moving in the right direction.

-
That depends entirely on who created a given add-on, and why, and with
what intended audience.

What people need to understand is that it is always possible that an
add-on may be abandoned/orphaned, and particularly those whose history
is of the "it was created for my personal use and began making the
rounds" type.

And there are developers of some very popular add-ons who have never
even given a thought to a transition plan whereby the add-on would be
handed off to someone else were they to decide to want to walk away from
it.

These pieces of software are gifts to the community, but they don't
carry an obligation that the person that gifted them must remain
dedicated to that add-on until the day they die.  There are occasions,
and it's typically not for commercially produced add-ons, where an
add-on will be abandoned.
--

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

Scratch most feminists and underneath there is a woman who longs to be a
sex object. The difference is that is not */all/* she wants to be.

~ Betty Rollin

On Tue, Apr 5, 2022 at 07:27 PM, Don H wrote:

I would hope that the NVDA developers do their best to not break addon's while at the same time keep NVDA moving in the right direction.

-
That depends entirely on who created a given add-on, and why, and with what intended audience.

What people need to understand is that it is always possible that an add-on may be abandoned/orphaned, and particularly those whose history is of the "it was created for my personal use and began making the rounds" type.

And there are developers of some very popular add-ons who have never even given a thought to a transition plan whereby the add-on would be handed off to someone else were they to decide to want to walk away from it.  

These pieces of software are gifts to the community, but they don't carry an obligation that the person that gifted them must remain dedicated to that add-on until the day they die.  There are occasions, and it's typically not for commercially produced add-ons, where an add-on will be abandoned.
--

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

Scratch most feminists and underneath there is a woman who longs to be a sex object. The difference is that is not all she wants to be.

    ~ Betty Rollin

Hello!


Christopher-Mark Gilland wrote:

I also kind of am curious. I thought that the version from Code Factory was Sapi 5.

CodeFactory have Eloquence as SAPI5 and as a NVDA add-on, working only with NVDA, and the same for Vocalizer...



Christopher-Mark Gilland wrote

By the time it is deployed as stable, it may be working by then. I'm not ready yet to pannick, but certainly this is something worth considering.

If you are planning to buy Eloquence in SAPI5 you don't need to panic... It still work as expected...

Rui Fontes

I would hope that the NVDA developers do their best to not break addon's
while at the same time keep NVDA moving in the right direction.

On 4/5/2022 5:45 PM, Brian Vogel wrote:

On Tue, Apr 5, 2022 at 06:19 PM, Don H wrote:

    It just seems that more and more of the most recent NVDA updates
    break such things as addon's

-
That perception is actual reality.

Over the last couple of years there has been some major "under the hood"
updating going on in the NVDA core code.  That's been plainly announced,
well ahead of time, along with the fact that these changes will cause
breaks in add-on compatibility if the add-on developers do not keep up.
This is not unique to NVDA and third party add-ons.

We've seen this with NVDA and JAWS over the years as major updates were
occurring in Windows, too.  I can recall (and not just for screen
readers) how many things "broke" in the early days of Windows 10 because
the various software houses essentially did nothing to prepare for that
release ahead of time and played catch up afterward.

We see it, and it's almost impossible to avoid, with web browsing and
screen readers not infrequently as new parts of web coding come into
existence, sometimes with minimal warning.

We are now in the age of everything "as a service" and that means that
something, probably Windows primarily, and its update cadence will be
driving the cadences of lots of other stuff.  But once you get into
something like NVDA and its add-ons, the major updates to NVDA will
dictate the cadence of updates to add-ons if those add-ons are still
supported.

There can be, and almost certainly will be, periods of time where NVDA
itself and its add-ons have relatively long plateau periods where major
updates and backward compatibility breaking will not be occurring.  But
that time is not now, and as far as I can see there are some add-ons
that may very well become orphans and only work up to a given NVDA
version, because their original developers have lost interest and no one
else has picked up the ball to run with it.

And as disconcerting as that may be, I'd certainly not propose that NVDA
stop its ongoing development, some of which involves backward
compatibility breaking releases, because any given add-on might become
an orphan.  NVDA's ongoing viability depends on it continuing to be
worked on as the ecosystem in which it is immersed continues to change.
To do otherwise means that NVDA will cease to exist as a viable screen
reader in the Windows sphere.
--

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

Scratch most feminists and underneath there is a woman who longs to be a
sex object. The difference is that is not */all/* she wants to be.

~ Betty Rollin