Date   

Re: Typing Echo Change with 2018.1

 

Hi,

Huh? That’s new for me. So you’re saying turning this off fixed this for you? Can others test this theory?

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Sunday, March 11, 2018 8:21 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

The typing interrupt toggle under keyboard settings fixed it!?

I have never touched that setting...ever.  Is there a chance 2018.1 changed this setting somehow?  Sorry for the trouble.


Re: wordpress.com

Ashley Coleman <amc05111@...>
 

Yes, the admin center is great. I haven’t experimented with the new system yet.

Ashley

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Kingett
Sent: Sunday, March 11, 2018 10:39 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] wordpress.com

 

For the best wordpress.com experience with NVDA use their wp-admin dashboard. Don't use their new system. If you hate typing in wp-admin every time, the dashboard link on m.wordpress.com will take you to the more accessible back end.


Re: Typing Echo Change with 2018.1

Gary
 

The typing interrupt toggle under keyboard settings fixed it!?

I have never touched that setting...ever.  Is there a chance 2018.1 changed this setting somehow?  Sorry for the trouble.


Re: Typing Echo Change with 2018.1

Gary
 

Sorry for the delay in getting back to you.  It was 2AM here and I had to get sleep. :)

I will try uninstalling NVDA and going back to 2017.4 later today and follow your steps for upgrading.  I'll be in touch.

Thanks!


Re: Typing Echo Change with 2018.1

Gary
 

I just tried espeak, and yes, it still happens.


Re: wordpress.com

 

For the best wordpress.com experience with NVDA use their wp-admin dashboard. Don't use their new system. If you hate typing in wp-admin every time, the dashboard link on m.wordpress.com will take you to the more accessible back end.


Re: Typing Echo Change with 2018.1

Adriani Botez
 

Dear all,

 

I have tested NVDA regarding this issue and got following results:

  • MS Word 2016: ok
  • MS Excel 2016: ok
  • MS PowerPoint 2016: ok
  • MS Outlook 2016: ok
  • IE11: ok
  • Firefox 59: ok
  • MS Edge: ok
  • Google Chrome 64: ok

 

Please look in NVDA menu at keyboard settings. Is “interrupt speech when typing characters” enabled?

 

 

Best

Adriani

 

 

Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Brian Moore
Gesendet: Sonntag, 11. März 2018 14:41
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Typing Echo Change with 2018.1

 

What browser are people using who have this problem.  Just tried with 2018.1 and both ff 58 and chrome and can't reproduce it.  this is on windows 10 1709

I could try with ie although I never use it.  Just trying to pin it down.

 

Contact me on skype: brian.moore
follow me on twitter:
http://www.twitter.com/bmoore123

On 2018-03-11 12:28 AM, Joseph Lee wrote:

Hi,

I see. Can you try the following for me:

  1. Download several beta builds (listed below).
  2. Run each one as an installer (do not install them, just run them) with NVDA set to speak typed characters.
  3. Tell me which beta build seems slower when announcing typed characters.

 

Beta build candidates to try:

  1. NVDA 2017.4.
  2. Build 14729 (December 14, 2017): https://ci.appveyor.com/api/buildjobs/ui46m9d93xvsn7rw/artifacts/output/nvda_snapshot_master-14729,3152eacc.exe
  3. Build 14767 (January 3, 2018): https://ci.appveyor.com/api/buildjobs/w1e53fm8wj1vwqvv/artifacts/output/nvda_snapshot_master-14767,f7853f34.exe
  4. Build 14825 (February 1, 2018): https://ci.appveyor.com/api/buildjobs/54881ddsb9906a9l/artifacts/output/nvda_snapshot_master-14825,2017d1f5.exe
  5. Build 14868 (February 19, 2018): https://ci.appveyor.com/api/buildjobs/tmfpypkc4fwuoqlw/artifacts/output/nvda_snapshot_master-14868,48743675.exe
  6. NVDA 2018.1.

 

Thanks.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Saturday, March 10, 2018 9:17 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

I had tried restarting the PC earlier.  I just now tried two different syntehsizers, but no difference.

 


Re: Typing Echo Change with 2018.1

Brian Moore
 

What browser are people using who have this problem.  Just tried with 2018.1 and both ff 58 and chrome and can't reproduce it.  this is on windows 10 1709

I could try with ie although I never use it.  Just trying to pin it down.


Contact me on skype: brian.moore
follow me on twitter:
http://www.twitter.com/bmoore123
On 2018-03-11 12:28 AM, Joseph Lee wrote:

Hi,

I see. Can you try the following for me:

  1. Download several beta builds (listed below).
  2. Run each one as an installer (do not install them, just run them) with NVDA set to speak typed characters.
  3. Tell me which beta build seems slower when announcing typed characters.

 

Beta build candidates to try:

  1. NVDA 2017.4.
  2. Build 14729 (December 14, 2017): https://ci.appveyor.com/api/buildjobs/ui46m9d93xvsn7rw/artifacts/output/nvda_snapshot_master-14729,3152eacc.exe
  3. Build 14767 (January 3, 2018): https://ci.appveyor.com/api/buildjobs/w1e53fm8wj1vwqvv/artifacts/output/nvda_snapshot_master-14767,f7853f34.exe
  4. Build 14825 (February 1, 2018): https://ci.appveyor.com/api/buildjobs/54881ddsb9906a9l/artifacts/output/nvda_snapshot_master-14825,2017d1f5.exe
  5. Build 14868 (February 19, 2018): https://ci.appveyor.com/api/buildjobs/tmfpypkc4fwuoqlw/artifacts/output/nvda_snapshot_master-14868,48743675.exe
  6. NVDA 2018.1.

 

Thanks.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Saturday, March 10, 2018 9:17 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

I had tried restarting the PC earlier.  I just now tried two different syntehsizers, but no difference.



Re: NVDA randumly crashing?

Adriani Botez
 

Hello,

there are several issues on Github about this, for example #7237.

Do you use jaws as well?
I can reproduce this issue more often when starting jaws and exiting jaws while NVDA is running.

Best
Adriani

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Matt
Turner
Gesendet: Sonntag, 11. März 2018 13:34
An: nvda@nvda.groups.io
Betreff: Re: [nvda] NVDA randumly crashing?

Hi.

I mostly use e-speak.

As for the crashing, sometimes nvda will restart on its own, and other times I
have to manually restart it.


On 3/11/2018 5:25 AM, Brian's Mail list account via Groups.Io wrote:
I do not see this in Windows 7, but the other person has windows 8.1.
I'd expect all sorts of issues with 10, due to its numerous builds
over its lifetime thus far.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Don H" <lmddh50@adams.net>
To: <nvda@nvda.groups.io>
Sent: Saturday, March 10, 2018 11:23 PM
Subject: Re: [nvda] NVDA randumly crashing?


I am running NVDA on a Win 10 64 bit laptop and with the last two or
three versions of NVDA including 2018-1 I get NVDA crashing randomly
when I hit the windows key to open the start menu. I simply restart
NVDA and everything seems fine again until the next random crash.







Re: NVDA randumly crashing?

Matt Turner
 

Hi.

I mostly use e-speak.

As for the crashing, sometimes nvda will restart on its own, and other times I have to manually restart it.

On 3/11/2018 5:25 AM, Brian's Mail list account via Groups.Io wrote:
I do not see this in Windows 7, but the other person has windows 8.1.
I'd expect all sorts of issues with 10, due to its numerous builds over its lifetime thus far.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Don H" <lmddh50@adams.net>
To: <nvda@nvda.groups.io>
Sent: Saturday, March 10, 2018 11:23 PM
Subject: Re: [nvda] NVDA randumly crashing?


I am running NVDA on a Win 10 64 bit laptop and with the last two or three versions of NVDA including 2018-1 I get NVDA crashing randomly when I hit the windows key to open the start menu.  I simply restart NVDA and everything seems fine again until the next random crash.





Re: Typing Echo Change with 2018.1

Lino Morales
 

Well I used ESpeak with FB cause I commented on some posts. This problem doesn’t happen with ESpeak only One Core voices. I use MSS David with NVDA.

 

Lino Morales

 

From: Gene
Sent: Sunday, March 11, 2018 8:22 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

It can be tried and it's unlikely CCleaner would cause problems.  But I am very skeptical that it will accomplish anything.  If the problem started with a new version of NVDA, why would the registry suddenly and coincidentally become corrupted at that time?  And one or two other people have said they have the same problem when the new version is used.  It's strains credulity that coincidentally, two or three people had the same problem when trying a new version and that the problem is caused by the registry suddenly becoming corrupted on three computers in exactly the same way when a new version is being tried. 

 

If someone wants to try registry cleaning with CCleaner, it is unlikely to cause problems and they may want to.  But I'm very skeptical.

 

Gene

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

Sent: Sunday, March 11, 2018 7:15 AM

Subject: Re: [nvda] Typing Echo Change with 2018.1

 

I had the problem with a portable version of NVDA, where the speech did not follow the cursor movement in an application. Registry clean solved this problem. So why not trying it? I don’t see any big issues in cleaning registry with CCleaner. I didn’t hear of any issue raising after cleaning registry with that program.

 

 

Best

Adriani

 

 

Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Gene
Gesendet: Sonntag, 11. März 2018 13:13
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Typing Echo Change with 2018.1

 

I see no reason to do anything with the registry.  Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory.  The problem started with a new release of NVDA.  Other people have reported this problem.  Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk.  I don't believe in taking even small risks for no benefit.  is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?

 

Gene

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

Sent: Sunday, March 11, 2018 2:32 AM

Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Garry,

 

Do the letters appear on the screen as fast as you type? Or are they delayed?

 

Please run a CCleaner and clean your registry. Does the issue still occur?

 

Best

Adriani

 

Von meinem iPhone gesendet


Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@...>:

Hi,

Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.

Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Ok, that's really odd.  All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue.  I'm confused to how that could be possible. :/

 


Re: Typing Echo Change with 2018.1

Gene
 

It can be tried and it's unlikely CCleaner would cause problems.  But I am very skeptical that it will accomplish anything.  If the problem started with a new version of NVDA, why would the registry suddenly and coincidentally become corrupted at that time?  And one or two other people have said they have the same problem when the new version is used.  It's strains credulity that coincidentally, two or three people had the same problem when trying a new version and that the problem is caused by the registry suddenly becoming corrupted on three computers in exactly the same way when a new version is being tried. 
 
If someone wants to try registry cleaning with CCleaner, it is unlikely to cause problems and they may want to.  But I'm very skeptical.
 
Gene

----- Original Message -----
Sent: Sunday, March 11, 2018 7:15 AM
Subject: Re: [nvda] Typing Echo Change with 2018.1

I had the problem with a portable version of NVDA, where the speech did not follow the cursor movement in an application. Registry clean solved this problem. So why not trying it? I don’t see any big issues in cleaning registry with CCleaner. I didn’t hear of any issue raising after cleaning registry with that program.

 

 

Best

Adriani

 

 

Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Gene
Gesendet: Sonntag, 11. März 2018 13:13
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Typing Echo Change with 2018.1

 

I see no reason to do anything with the registry.  Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory.  The problem started with a new release of NVDA.  Other people have reported this problem.  Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk.  I don't believe in taking even small risks for no benefit.  is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?

 

Gene

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

Sent: Sunday, March 11, 2018 2:32 AM

Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Garry,

 

Do the letters appear on the screen as fast as you type? Or are they delayed?

 

Please run a CCleaner and clean your registry. Does the issue still occur?

 

Best

Adriani

 

Von meinem iPhone gesendet


Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@...>:

Hi,

Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.

Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Ok, that's really odd.  All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue.  I'm confused to how that could be possible. :/


Re: Typing Echo Change with 2018.1

Lino Morales
 

Actually I’ve noticed this problem myself in NVDA 2017.4 and 2017.3. I’m using horrid Espeak right now cause I’ll be checking my Facebook before church.

 

Lino Morales

 

From: Gene
Sent: Sunday, March 11, 2018 8:12 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

I see no reason to do anything with the registry.  Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory.  The problem started with a new release of NVDA.  Other people have reported this problem.  Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk.  I don't believe in taking even small risks for no benefit.  is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?

 

Gene

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

Sent: Sunday, March 11, 2018 2:32 AM

Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Garry,

 

Do the letters appear on the screen as fast as you type? Or are they delayed?

 

Please run a CCleaner and clean your registry. Does the issue still occur?

 

Best

Adriani

 

Von meinem iPhone gesendet


Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@...>:

Hi,

Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.

Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Ok, that's really odd.  All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue.  I'm confused to how that could be possible. :/

 


Re: Typing Echo Change with 2018.1

Adriani Botez
 

I had the problem with a portable version of NVDA, where the speech did not follow the cursor movement in an application. Registry clean solved this problem. So why not trying it? I don’t see any big issues in cleaning registry with CCleaner. I didn’t hear of any issue raising after cleaning registry with that program.

 

 

Best

Adriani

 

 

Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Gene
Gesendet: Sonntag, 11. März 2018 13:13
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Typing Echo Change with 2018.1

 

I see no reason to do anything with the registry.  Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory.  The problem started with a new release of NVDA.  Other people have reported this problem.  Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk.  I don't believe in taking even small risks for no benefit.  is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?

 

Gene

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

Sent: Sunday, March 11, 2018 2:32 AM

Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Garry,

 

Do the letters appear on the screen as fast as you type? Or are they delayed?

 

Please run a CCleaner and clean your registry. Does the issue still occur?

 

Best

Adriani

 

Von meinem iPhone gesendet


Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@...>:

Hi,

Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.

Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Ok, that's really odd.  All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue.  I'm confused to how that could be possible. :/


Re: Typing Echo Change with 2018.1

Lino Morales
 

 

Gary. Did you try using ESpeak NG? Just curious.

 

Lino Morales

 

From: Gary
Sent: Sunday, March 11, 2018 1:08 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Ok, that's really odd.  All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue.  I'm confused to how that could be possible. :/

 


Re: Typing Echo Change with 2018.1

Gene
 

I see no reason to do anything with the registry.  Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory.  The problem started with a new release of NVDA.  Other people have reported this problem.  Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk.  I don't believe in taking even small risks for no benefit.  is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?
 
Gene

----- Original Message -----
Sent: Sunday, March 11, 2018 2:32 AM
Subject: Re: [nvda] Typing Echo Change with 2018.1

Garry,

Do the letters appear on the screen as fast as you type? Or are they delayed?

Please run a CCleaner and clean your registry. Does the issue still occur?

Best
Adriani


Von meinem iPhone gesendet

Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@...>:

Hi,

Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.

Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Ok, that's really odd.  All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue.  I'm confused to how that could be possible. :/


Re: espeak and pronunciation of some words

Gene
 

Is this a new problem?  Are other things improved?  If this is a new problem and there are no improvements, maybe those who are trying to improve the dialect or variant should be asked, politely, and with appreciation for their efforts, to just leave things alone unless they have a good cadre of native born speakers of a certain dialect to evaluate proposed changes.  Wasn't there a lot of dissatisfaction with changes made a few versions of NVDA ago when a newer version of E-Speak was used?  It sounds to me as though whoever is making changes is making things Genearlly worse, even if this or that improvement may improve something.
 
Gene

----- Original Message -----
Sent: Sunday, March 11, 2018 2:18 AM
Subject: Re: [nvda] espeak and pronunciation of some words

My voice is English America and variant is Max.





On 3/11/2018 3:15 AM, John Isige wrote:
Mine was Variant Max. Also shows up for all Ivans, John, and at least one of the Klats/Clats, I don't feel like checking them all. Voice is English America.


On 3/11/2018 1:10, John Isige wrote:
He was content with the content of the book. Both "contents" sound fine to me in that sentence. Nazarene is indeed wrong, it should sound like Nazareen but sounds like Nazaren, except the 'ren' part is accented. That would be a useful trick if you could reproduce it, but it's wrong here. Also, 'reproduce' sounds a bit more like 'riproduce' then 'reeproduce'.


On 3/11/2018 0:54, Governor staten wrote:
I'll try to describe this as best I can. Take the word "content". The stress in this word is wrong, or, very much off. This is the case with other words too. Nazarene should sound like Nazareen. I'm sure there are other words like this I, and others, could think of.


Any word with the letter "o" is likely to have the stress wrong. Monster is another example. This could just be me. Does anyone else hear what I'm hearing?













Re: Typing Echo Change with 2018.1

Brian's Mail list account <bglists@...>
 

Please remove any drivers in your user area manually as well though. Not sure whether revo can do this or not.
Brian

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

----- Original Message -----
From: "zahra" <nasrinkhaksar3@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 7:40 AM
Subject: Re: [nvda] Typing Echo Change with 2018.1


garry,
you can uninstall nvda 2018.1 completely and try installation of nvda
17.4 fresh install.
try it and see can you use 2017.4 without problem that you described?

On 3/11/18, Adriani Botez <adriani.botez@gmail.com> wrote:
Garry,

Do the letters appear on the screen as fast as you type? Or are they
delayed?

Please run a CCleaner and clean your registry. Does the issue still occur?

Best
Adriani


Von meinem iPhone gesendet

Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@gmail.com>:

Hi,
Hmmm, that’s really odd indeed. Do you have access to another computer
with a similar setup where you can test these builds? Also, if you are
comfortable installing beta software releases, do you mind installing
2017.4 back (and disable update checking via general settings dialog) and
see if it improves things a bit? If it does improve things, then please
install each of the beta builds (in sequence as described in my email) and
let us know if you notice any changes.
Also, an advanced warning for people really tempted to do the following
(and in order to avoid another instance of miscommunication like VS2017
runtime problem a few weeks back): just because you can’t reproduce a
problem DOES NOT MEAN you can close an issue or ignore it. Who knows if
the problem reported by a user might happen to you one day, or the
reporter found a solution that works for him or her that might or might
not apply to others. There are some in the community (who shall remain
nameless) who downplay the severity of a problem when they can’t reproduce
it or think their version of Windows is immune. No, a problem reported by
a user is still a problem if it negatively affects productivity for them,
potentially marring their NVDA experience. Some of you may think that what
Gary is going through is a minor anoyance, but if this problem affects his
productivity, then it should still be investigated to find out why, hence
my suggestion to let him try different beta builds. I’m saying all this
because I think we should change our attitudes about providing support for
newcomers and/or those who are experiencing problems we can’t reproduce
(easily).
Cheers,
Joseph

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

Ok, that's really odd. All of them were slow on the typing echo,
including 2017.4, which is what I was running previously without issue.
I'm confused to how that could be possible. :/

--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali


Re: espeak and pronunciation of some words

Brian's Mail list account <bglists@...>
 

Its not the variant, but the other variable where you can select us rp west mids etc that can make a significant difference.
Brian

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

----- Original Message -----
From: "Rob Hudson" <rob_hudson_3182@gmx.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 7:10 AM
Subject: Re: [nvda] espeak and pronunciation of some words


Governor staten <govsta@gmail.com> wrote:
I'll try to describe this as best I can. Take the word "content". The
stress in this word is wrong, or, very much off. This is the case with
other words too. Nazarene should sound like Nazareen. I'm sure there are
other words like this I, and others, could think of.

What variant. There are a lot of espeak variants here.


Re: espeak and pronunciation of some words

Brian's Mail list account <bglists@...>
 

I do suspect here that the people now developing it have a different accent to the original developer. as a matter of interest, is the RP version any better?
OK its posher, but for me still is not quite right. Often has been wrong for ages according to how I speak!

Brian

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

----- Original Message -----
From: "John Isige" <gwynn@tds.net>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 7:10 AM
Subject: Re: [nvda] espeak and pronunciation of some words


He was content with the content of the book. Both "contents" sound fine to me in that sentence. Nazarene is indeed wrong, it should sound like Nazareen but sounds like Nazaren, except the 'ren' part is accented. That would be a useful trick if you could reproduce it, but it's wrong here. Also, 'reproduce' sounds a bit more like 'riproduce' then 'reeproduce'.


On 3/11/2018 0:54, Governor staten wrote:
I'll try to describe this as best I can. Take the word "content". The stress in this word is wrong, or, very much off. This is the case with other words too. Nazarene should sound like Nazareen. I'm sure there are other words like this I, and others, could think of.


Any word with the letter "o" is likely to have the stress wrong. Monster is another example. This could just be me. Does anyone else hear what I'm hearing?