1. nvda@nvda.groups.io
   Date   
Error while updating to NVDA 2018.1 via the NVDA update utility.

Arianna Sepulveda
 

Hello, All,


I just tried installing the NVDA 2018.1 update via the NVDA update
utility, and got the following error. I'm not sure what is relevant,
so I just coppied the entire output of the log viewer.

INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation
INFO - core.main (18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 192, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.

Should I try updating again?


Thanks,
Ari
Re: Typing Echo Change with 2018.1

Robert Mendoza
 

Hi Joseph,

Sorry for the late in my respond. I went again to double-check the keyboard settings then I noticed that the option for Speech interrupt for typed characters is uncheck though in my recollection I never altered this even before. and now I am back again in using the 2018.1 fine for now -the lag in typing were solved. Thanks again.


Robert Mendoza
On 3/11/2018 12:06 PM, Joseph Lee wrote:

Hi,

Does running NVDA in “safe mode” aka add-ons disabled help?

Cheers,

Joseph

 

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

 

Yes! I noticed it here so I decided to go back to older version and use my flash drive. Not specifically  for the mobile facebook but as well with typing to notepad that some kinda delay or what. I even tried to adjust the keyboard settings but got the same results. I think I will be working for now and use 2017.4 version.

 

Robert Mendoza

On 3/11/2018 11:36 AM, Lino Morales wrote:

Que pasa Gary. Yeah I’ve noticed this too. When I’m writing a status or replying to someone in the FB mobile site that’s when it happens.

 

Lino Morales

 

From: Gary
Sent: Saturday, March 10, 2018 10:34 PM
To: nvda@nvda.groups.io
Subject: [nvda] Typing Echo Change with 2018.1

 

I upgraded to the latest release of NVDA today and right away I noticed a change that is, well, quite annoying to me.

I am a fast typist who prefers to have typed characters repeated.  Since upgrading NVDA today, the letters I type are read back to me extremely slowly, where as previously, i was hearing the key I typed instantly.

Similarly, in a web browser when I use NVDA+F7 to jump to a link, there is also a delay.  For example, if I know the link I want is "Search", I could hit the S and NVDA would immediately say "Search" and I could then hit enter.  Now, NVDA says "S", there is a delay, then it says "Search".  Is this a new feature that has a setting I can't find to change it, a bug, or am I the only person noticing this?

 

 
Question about transferring espeak data between NVDA & Braillenote touch version

Jessica D <jldail13@...>
 

Hi,

Yesterday, I bought eSpeak for my Braillenote touch.

I’m really enjoying it, and its totally boosted my productivity.

I’m now using eSpeak with NVDA, and was wondering if it was possible to transfer my settings and other data between the 2 versions?

 

Thanks,

Jessica

 

 

Sent from Mail for Windows 10

 
Re: Typing Echo Change with 2018.1

Rosemarie Chavarria
 

I don't have a braille display. Can't afford one.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian's Mail list account via Groups.Io
Sent: Sunday, March 11, 2018 1:31 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

Do all of you have Braille displays?
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: "Gary" <ironmangary@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 6:08 AM
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

Rosemarie Chavarria
 

I've used the one-core voices and they're really great.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Devin Prater
Sent: Sunday, March 11, 2018 5:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

I agree, eSpeak needs lots of work, still. But the worst part of Open Source is that we all talk about it, but nothing gets done, we all wish, but never act, and there is only one person working on eSpeak. I know, we can't all program. But, with Windows 10, there are the OneCore voices, created by Microsoft which we can use, so we are no longer limited to eSpeak.

On 3/11/18, 7:05 PM, "nvda@nvda.groups.io on behalf of Rosemarie Chavarria" <nvda@nvda.groups.io on behalf of knitqueen2007@gmail.com> wrote:

I've noticed that about e-speak too. The word "for" when with other words soundlike "fer".



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Dejan Ristic
Sent: Sunday, March 11, 2018 12:01 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

Let me remind you of the word for, which, if followed by another word, seems to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is
a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07: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

Rosemarie Chavarria
 

Hi, Joseph,

 

I tested it and unchecking speech interrupt does cause NVDA to lag for me so I checked it again.

 

Rosemarie

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Sunday, March 11, 2018 9:15 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] 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: espeak and pronunciation of some words

Devin Prater
 

I agree, eSpeak needs lots of work, still. But the worst part of Open Source is that we all talk about it, but nothing gets done, we all wish, but never act, and there is only one person working on eSpeak. I know, we can't all program. But, with Windows 10, there are the OneCore voices, created by Microsoft which we can use, so we are no longer limited to eSpeak.

On 3/11/18, 7:05 PM, "nvda@nvda.groups.io on behalf of Rosemarie Chavarria" <nvda@nvda.groups.io on behalf of knitqueen2007@gmail.com> wrote:

I've noticed that about e-speak too. The word "for" when with other words soundlike "fer".

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Dejan Ristic
Sent: Sunday, March 11, 2018 12:01 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

Let me remind you of the word for, which, if followed by another word, seems to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is
a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07: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: outlook 2016 calendar

Rosemarie Chavarria
 

I have the outlook 2013 calendar buthaven't tried it yet.

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Angelo Sonnesso
Sent: Sunday, March 11, 2018 11:17 AM
To: nvda@nvda.groups.io
Subject: [nvda] outlook 2016 calendar

 

Has anyone had success with the outlook 2016 calendar?

I never had a problem with older versions of outlook, but now I can only read the dates.

Thanks

 

73 N2DYN Angelo
Re: Typing Echo Change with 2018.1

Roger Stewart
 

Interesting!  I just checked, and mine is checked but I have no typing echo delays at all!  As snappy and responsive as ever.

Roger









On 3/11/2018 6:56 PM, Gene wrote:
Did you check or uncheck it?  It should be unchecked by default and when unchecked, I don't have the problem.  I'm not using the newest NVDA version but it has been unchecked whenever I've used a new version.
 
Gene
----- Original Message -----
From: Gary
Sent: Sunday, March 11, 2018 11:28 AM
Subject: Re: [nvda] Typing Echo Change with 2018.1

I checked "speech interrupt for typed characters."  It was unchecked, although I never touched it previously, so I can't say how it was set prior to 2018.1.
Re: Typing Echo Change with 2018.1

Gene
 

I see that I mistakenly said it should be unchecked by default.  It should be checked by default.  You want speech interrupted in most cases.  So what is causing the problem?  Is the update acting as though the setting is unchecked when the update is done?  Then when you uncheck and check it again, does it properly have this setting off?  It sounds as though that is what is happening.  That when the update occurs, the setting acts as though it is unchecked, and then unchecking and checking it again causes it to perform correctly.
 
Gene
----- original Message -----

Sent: Sunday, March 11, 2018 12:46 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1

I just unchecked min and oh yeah buddy there is a lag. When I checked again. No more lag.

 

Lino Morales

 

From: Chris via Groups.Io
Sent: Sunday, March 11, 2018 1:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Mines checked, unchecked it lags

 

 

From: Lino Morales
Sent: 11 March 2018 17:41
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Gary was it on or off. Also for the rest of the list is it on by default? I think mine is on currently.

 

Lino Morales

 

From: Gary
Sent: Sunday, March 11, 2018 11:20 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: espeak and pronunciation of some words

Rosemarie Chavarria
 

I've noticed that about e-speak too. The word "for" when with other words soundlike "fer".

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Dejan Ristic
Sent: Sunday, March 11, 2018 12:01 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

Let me remind you of the word for, which, if followed by another word, seems to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is
a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07: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

Gene
 

If it is checked by default, that is an error and the default setting should immediately be changed to unchecked.  In most situations, speech should be interrupted when typing.  It is only in very specific settings, such as when playing MUDS or when in a chat room where you want to type while reading a message that this setting should be checked.  See the following discussion:
 

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

Hi,

By default, it should have been checked, but looks like it wasn’t. Thanks for the update on this.

Cheers,

Joseph

 

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

 

I checked "speech interrupt for typed characters."  It was unchecked, although I never touched it previously, so I can't say how it was set prior to 2018.1.
Re: Typing Echo Change with 2018.1

Gene
 

Did you check or uncheck it?  It should be unchecked by default and when unchecked, I don't have the problem.  I'm not using the newest NVDA version but it has been unchecked whenever I've used a new version.
 
Gene

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

I checked "speech interrupt for typed characters."  It was unchecked, although I never touched it previously, so I can't say how it was set prior to 2018.1.
Re: Typing Echo Change with 2018.1

Gene
 

I just tried this.  There may not be a delay.  .  What may be happening is that since typing doesn't interrupt letterss, then letters get behind because every letter is announced and it isn't interrupted while the person is typing.  so if you type faster than the letters are announced, you can get ahead of what is being read.  Is typing interrupt on by default in the new build of NVDA?  If so, there is no question that the setting should be off, as it was until recently by default.   
 
I'm testing on a slow computer but later tonight, I'll test on a fast one.  At this point, based on this one computer, it looks as though what I said has a good chance of being correct.  No delay, but if you type quickly, you get ahead of speech when every letter is announced in full as you type.
 
Gene
----- Original Message -----

From: Gary
Sent: Sunday, March 11, 2018 10:20 AM
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: outlook 2016 calendar

Ralf Kefferpuetz
 

Works good for me, use the tab key when you hear the dates…

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Angelo Sonnesso
Sent: Sonntag, 11. März 2018 19:17
To: nvda@nvda.groups.io
Subject: [nvda] outlook 2016 calendar

 

Has anyone had success with the outlook 2016 calendar?

I never had a problem with older versions of outlook, but now I can only read the dates.

Thanks

 

73 N2DYN Angelo
Re: espeak and pronunciation of some words

Adriani Botez
 

Dear all,


I think eSpeak has to be adjusted from scratch. It is very hard to get to a point where every word is being pronounced correctly. This is a matter of accent and phonemes which are very limited in eSpeak development.

If we begin to assess every word in eSpeak, we will find thousants and thousants of words which are mispronounced. Don't forget eSpeak supports more than 50 languages. So, developing this synthesizer word by word is not a long term solution.

So, in my view, if another speech synthesizer becomes free (i.e. eloquence or vocalizer), every user will change to it unless eSpeak is being vastly improved from scratch.


Best
Adriani

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Dejan
Ristic
Gesendet: Sonntag, 11. März 2018 20:01
An: nvda@nvda.groups.io
Betreff: Re: [nvda] espeak and pronunciation of some words

Let me remind you of the word for, which, if followed by another word, seems
to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is
a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07: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

Adriani Botez
 

Hello,

this setting is available since years. It makes sense for people who are using a braille display because they can read a part of a document in braille while listening to another part of the document reported by speech.

Or for people who must type something manually, for example text strings which cannot be copied. This function works well together with the setting "allow skim reading in say all". That setting can also be toggled in keyboard settings.


Best
Adriani

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von zahra
Gesendet: Sonntag, 11. März 2018 19:48
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Typing Echo Change with 2018.1

if i uncheck them, nvda is slow in reporting characters.

On 3/11/18, Don H <lmddh50@adams.net> wrote:
I have no lag no mater if these are checked or not.

On 3/11/2018 12:46 PM, Lino Morales wrote:
I just unchecked min and oh yeah buddy there is a lag. When I checked
again. No more lag.

Lino Morales

*From: *Chris via Groups.Io
<mailto:chrismedley=btinternet.com@groups.io>
*Sent: *Sunday, March 11, 2018 1:45 PM
*To: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject: *Re: [nvda] Typing Echo Change with 2018.1

Mines checked, unchecked it lags

*From: *Lino Morales <mailto:linomorales001@gmail.com>
*Sent: *11 March 2018 17:41
*To: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject: *Re: [nvda] Typing Echo Change with 2018.1

Gary was it on or off. Also for the rest of the list is it on by
default? I think mine is on currently.

Lino Morales

*From: *Gary <mailto:ironmangary@gmail.com>
*Sent: *Sunday, March 11, 2018 11:20 AM
*To: *nvda@nvda.groups.io <mailto: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.





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

Dejan Ristic
 

Let me remind you of the word for, which, if followed by another word, seems to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is a stand alone word, as is the case in the first line of my message.

On 11/03/2018 07: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

zahra
 

if i uncheck them, nvda is slow in reporting characters.

On 3/11/18, Don H <lmddh50@adams.net> wrote:
I have no lag no mater if these are checked or not.

On 3/11/2018 12:46 PM, Lino Morales wrote:
I just unchecked min and oh yeah buddy there is a lag. When I checked
again. No more lag.

Lino Morales

*From: *Chris via Groups.Io <mailto:chrismedley=btinternet.com@groups.io>
*Sent: *Sunday, March 11, 2018 1:45 PM
*To: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject: *Re: [nvda] Typing Echo Change with 2018.1

Mines checked, unchecked it lags

*From: *Lino Morales <mailto:linomorales001@gmail.com>
*Sent: *11 March 2018 17:41
*To: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject: *Re: [nvda] Typing Echo Change with 2018.1

Gary was it on or off. Also for the rest of the list is it on by
default? I think mine is on currently.

Lino Morales

*From: *Gary <mailto:ironmangary@gmail.com>
*Sent: *Sunday, March 11, 2018 11:20 AM
*To: *nvda@nvda.groups.io <mailto: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.




--
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
outlook 2016 calendar

Angelo Sonnesso
 

Has anyone had success with the outlook 2016 calendar?

I never had a problem with older versions of outlook, but now I can only read the dates.

Thanks

 

73 N2DYN Angelo
44281 - 44300 of 80943  
More
Home Messages Hashtags Subgroups About Features Pricing Updates Terms Help Twitter