Date   

Re: NVDA 2019.3.1 and External Soundcard and Firefox

Pele West
 

Hi Quentin

Thanks for your suggestions. Apologies if the message below seems a
little muddled. I have done so much uninstalling and reinstalling lately.

Before I wrote my first message I tried to change the output device in
the way you describe. The problem is that NVDA does not seem to see the
external sound card.

I started off by installing NVDA from a portable version created using a
different machine. The first time I did this, NVDA could see the sound
card and I was able to set it.

When I found it would not work with Firefox I uninstalled NVDA and
deleted the NVDA folder in AppData. Since then it has not been possible
to change to the external sound card as NVDA does not see it.

I use Window-Eyes on this machine and it works perfectly with the
external sound card.

I have also run the NVDA Com Registration Tool twice, and Firefox still
does not work. However, it does work using Chrome and Internet Explorer.

Both machines use Windows 7.

Is it worth trying to install NVDA from a download installation and
configuring it?

Pele


NVDA/NextUp naturally speaking voices

Robert Doc Wright godfearer
 

I have tried these voices with NVDA and ten seconds later NVDA locks up. I have tried both 16 and 32bit.
******
Something to think about, Since God has forgiven it, who are you to keep picking it back up!


Re: installing the Alan voice

Rosemarie Chavarria
 

I got the add-on but I can't get it to work. Is there some kind of driver I need to install? If not, how do I get the voice to work?

On 2/23/2020 1:26 PM, Kevin Cussick via Groups.Io wrote:
No You only need the addon and the voice I have no language pack installed here and it just works.

On 22/02/2020 00:44, Roger Stewart wrote:
Also, you need the English Language pack.

Roger






On 2/21/2020 4:44 PM, Kevin Cussick via Groups.Io wrote:
Well yes, but first You need the driver the RH voice nvda addon.

On 21/02/2020 22:35, Rosemarie Chavarria wrote:
I think so. Isn't Alan just a voice?



On 2/21/2020 2:32 PM, Kevin Cussick via Groups.Io wrote:
Hi,   do You have the addon for the sinth installed?

On 21/02/2020 22:22, Rosemarie Chavarria wrote:
I hit enter on the add-on but it wouldn't install. What do I do now?



On 2/21/2020 2:01 PM, Kevin Cussick via Groups.Io wrote:
Hi,   OK just hit enter on the addon and as long as nvda is running it should just install.

On 21/02/2020 03:37, Rosemarie Chavarria wrote:
Hi, everyone,


How do I install the RH voice Alan to the other voices? It's in the add-ons list but I can't install it. I forgot how to add an extra voice.


Thanks for your help in advance.


Rosemarie













Re: Strange issue with Windows 10's OCR

Aravind R
 

even in pdf file, if i press insert+ r, only blank screen is
displayed. does anybody know how to get better result?

On 24/02/2020, Quentin Christensen <quentin@...> wrote:
Hi Kara,

I'm not sure why you get better results with one OCR than the other, but
someone asked recently about Komplete Kontrol and I found a few
resources for them which might help (I haven't used it myself so really
have very little idea):

Firstly, https://kk-access.com/ has information about the accessibility
mode and how to set it up.

I also found this page on Native Instruments' blog:
https://blog.native-instruments.com/designing-for-the-visually-impaired-and-how-its-changing-how-software-is-made/

Here is a YouTube video which might help:
https://www.youtube.com/watch?v=uHdDgwp4OTU

There is also an email group for support: komplete-kontrol
-access+subscribe@...

Regards

Quentin.

On Sun, Feb 23, 2020 at 9:09 AM Kara Goldfinch <kara.louise18@...>
wrote:

Hi everyone.

I use a Komplete audio 6 audio interface, which has an inaccessible
control panel that I can sort of use via OCR. However, for some
inexplicable reason, I get better results when using the legacy OCR
add-on
than I do with Windows 10's built-in engine.

I have the add-on installed in a portable copy of 2019.,2.1, but since
every other add-on I use is now supported under 2019.3.1, It seems
pointless keeping this around if I can get it sorted.

So I was wondering if any of you know why this might be. I have checked
my screen resolution and scaling; both are set to their recommended
values. The app also can't be maximised.

Windows 10's OCR engine works everywhere else. It's literally just this
one thing I need to use the legacy add-on for.

I'm using Windows 10 home Version 1909 (OS Build 18363.657).

Thanks in advance for any help.

Kara


--
Quentin Christensen
Training and Support Manager

NVDA 2019.3 rc2 now available for testing:
https://www.nvaccess.org/post/nvda-2019-3rc2-now-available-for-testing/

Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>




--
--
nothing is difficult unless you make it appear so.

r. aravind,

Assistant manager
Department of sales
bank of baroda specialised mortgage store, Chennai.
mobile no: +91 9940369593,
email id : aravind_069@..., aravind.andhrabank@....
aravind.rajendran@....


Re: code factory vocalizer expressive voices

Quentin Christensen
 

Hi Afik,

You can purchase the Code Factory voices from: https://codefactoryglobal.com/app-store/voices-for-nvda/

Kind regards

Quentin.

On Mon, Feb 24, 2020 at 1:35 AM Afik Souffir <afik.souffir@...> wrote:

 

 

Hi,

 

I'd like to know when can I buy the code factory addon with vocalizer expressive voices, compatible with 2019.3 and later.

 

 

Afik

 

 

 



--
Quentin Christensen
Training and Support Manager



Re: code factory vocalizer expressive voices

mattias
 

download it from codefactory.es
i run it myself

Den 23 februari 2020 15:35:59 skrev "Afik Souffir" <afik.souffir@...>:

 

 

Hi,

 

I'd like to know when can I buy the code factory addon with vocalizer expressive voices, compatible with 2019.3 and later.

 

 

Afik

 

 

 


Re: NVDA 2019.3.1 and External Soundcard and Firefox

Quentin Christensen
 

Hi Pele,

In NVDA's synthesizer settings, you can select your output device.  Press NVDA+control+S, then press TAB once to move to output device.  Use the arrows to select the desired device and enter to start using it.  If something doesn't work right, you can press NVDA+control+r to revert to the saved settings.

Re NVDA reporting unknown in Firefox, you could try running NVDA's COM Registration Fixing Tool from the tools menu.  Press NVDA+N then T to get to the tools menu then use the arrow keys to select that option and enter, then follow the prompts.

Regards

Quentin.

On Sat, Feb 22, 2020 at 11:04 PM Pele West <pele.westlists@...> wrote:
Hi Everyone

I have installed NVDA on a Windows 7 machine. The machine has 2
soundcards. I want to direct NVDA to the external soundcard, but it
cannot see it.

How do I persuade it to recognize it?

Window-Eyes sees it as Speakers USB Audio.

Also, I have installed and uninstalled the latest version of Firefox a
number of times but NVDA still will not work with it. It will work with
Chrome.

Can anyone advise me on these points?

Thanks 

pele West







--
Quentin Christensen
Training and Support Manager



Re: Strange issue with Windows 10's OCR

Quentin Christensen
 

Hi Kara,

I'm not sure why you get better results with one OCR than the other, but someone asked recently about Komplete Kontrol and I found a few resources for them which might help (I haven't used it myself so really have very little idea):

Firstly, https://kk-access.com/ has information about the accessibility mode and how to set it up.


Here is a YouTube video which might help: https://www.youtube.com/watch?v=uHdDgwp4OTU

There is also an email group for support: komplete-kontrol-access+subscribe@...

Regards

Quentin.

On Sun, Feb 23, 2020 at 9:09 AM Kara Goldfinch <kara.louise18@...> wrote:

Hi everyone.

I use a Komplete audio 6 audio interface, which has an inaccessible control panel that I can sort of use via OCR. However, for some inexplicable reason, I get better results when using the legacy OCR add-on than I do with Windows 10's built-in engine.

I have the add-on installed in a portable copy of 2019.,2.1, but since every other add-on I use is now supported under 2019.3.1, It seems pointless keeping this around if I can get it sorted.

So I was wondering if any  of you know why this might be. I have checked my screen resolution and  scaling; both are set to their recommended values. The app also can't be maximised.

Windows 10's OCR engine works everywhere else. It's literally just this one thing I need to use the legacy add-on for.

I'm using Windows 10 home Version 1909 (OS Build 18363.657).

Thanks in advance for any help.

Kara



--
Quentin Christensen
Training and Support Manager



backup speech dictionaries

Don H
 

Having made several additions to the dafault NVDA speech dictionary, is there a way to back it up?


Re: NVDA and touch screens

Luke Robinett
 

Hmm, well it’s working now. I guess it was just temporarily confused. Haha. Thanks again.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Sunday, February 23, 2020 3:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and touch screens

 

Hi,

Is NVDA installed on the laptop? If yes, it might be that NVDA isn’t detecting touch capability on your laptop’s monitor (for this, we need a short log fragment).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Luke Robinett
Sent: Sunday, February 23, 2020 4:43 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA and touch screens

 

Hi everyone,

 

I recently purchased a touch screen monitor for my desktop PC and NVDA works as expected – when I touch the screen, it speaks aloud whatever I touch. However, I just got a new laptop that also has a touch screen and NVDA is not behaving that same way. When I touch my laptop’s screen, whatever I touch is activated immediately instead of spoken aloud. Does anyone know why this might be? I looked through NVDA’s settings but didn’t find anything. Strange that it would be different on these two machines.

 

Thanks,

Luke R.

 


Re: NVDA and touch screens

Luke Robinett
 

Hi Joseph and thank you for the fast response. Yes, NVDA is freshly installed, though perhaps I should try a restart first. I’ll let you know if the issue persists after that.

 

Thanks

Luke R

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Sunday, February 23, 2020 3:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and touch screens

 

Hi,

Is NVDA installed on the laptop? If yes, it might be that NVDA isn’t detecting touch capability on your laptop’s monitor (for this, we need a short log fragment).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Luke Robinett
Sent: Sunday, February 23, 2020 4:43 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA and touch screens

 

Hi everyone,

 

I recently purchased a touch screen monitor for my desktop PC and NVDA works as expected – when I touch the screen, it speaks aloud whatever I touch. However, I just got a new laptop that also has a touch screen and NVDA is not behaving that same way. When I touch my laptop’s screen, whatever I touch is activated immediately instead of spoken aloud. Does anyone know why this might be? I looked through NVDA’s settings but didn’t find anything. Strange that it would be different on these two machines.

 

Thanks,

Luke R.

 


Re: NVDA and touch screens

 

Hi,

Is NVDA installed on the laptop? If yes, it might be that NVDA isn’t detecting touch capability on your laptop’s monitor (for this, we need a short log fragment).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Luke Robinett
Sent: Sunday, February 23, 2020 4:43 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA and touch screens

 

Hi everyone,

 

I recently purchased a touch screen monitor for my desktop PC and NVDA works as expected – when I touch the screen, it speaks aloud whatever I touch. However, I just got a new laptop that also has a touch screen and NVDA is not behaving that same way. When I touch my laptop’s screen, whatever I touch is activated immediately instead of spoken aloud. Does anyone know why this might be? I looked through NVDA’s settings but didn’t find anything. Strange that it would be different on these two machines.

 

Thanks,

Luke R.

 


NVDA and touch screens

Luke Robinett
 

Hi everyone,

 

I recently purchased a touch screen monitor for my desktop PC and NVDA works as expected – when I touch the screen, it speaks aloud whatever I touch. However, I just got a new laptop that also has a touch screen and NVDA is not behaving that same way. When I touch my laptop’s screen, whatever I touch is activated immediately instead of spoken aloud. Does anyone know why this might be? I looked through NVDA’s settings but didn’t find anything. Strange that it would be different on these two machines.

 

Thanks,

Luke R.

 


Re: installing the Alan voice

Roger Stewart
 

Hmmmm. Interesting. The person who first posted about the RH voice on this list said you need the nvda add on, the English Language Package add on, and then any voice you want.  I can try removing the English Language package and see if it still works.  If it does, then I wonder why it is offered as an nvda add on and why this person said we need it to make it work.
Roger

On 2/23/2020 3:26 PM, Kevin Cussick via Groups.Io wrote:
No You only need the addon and the voice I have no language pack installed here and it just works.

On 22/02/2020 00:44, Roger Stewart wrote:
Also, you need the English Language pack.

Roger






On 2/21/2020 4:44 PM, Kevin Cussick via Groups.Io wrote:
Well yes, but first You need the driver the RH voice nvda addon.

On 21/02/2020 22:35, Rosemarie Chavarria wrote:
I think so. Isn't Alan just a voice?



On 2/21/2020 2:32 PM, Kevin Cussick via Groups.Io wrote:
Hi,   do You have the addon for the sinth installed?

On 21/02/2020 22:22, Rosemarie Chavarria wrote:
I hit enter on the add-on but it wouldn't install. What do I do now?



On 2/21/2020 2:01 PM, Kevin Cussick via Groups.Io wrote:
Hi,   OK just hit enter on the addon and as long as nvda is running it should just install.

On 21/02/2020 03:37, Rosemarie Chavarria wrote:
Hi, everyone,


How do I install the RH voice Alan to the other voices? It's in the add-ons list but I can't install it. I forgot how to add an extra voice.


Thanks for your help in advance.


Rosemarie













Re: installing the Alan voice

Kevin Cussick
 

No You only need the addon and the voice I have no language pack installed here and it just works.

On 22/02/2020 00:44, Roger Stewart wrote:
Also, you need the English Language pack.
Roger
On 2/21/2020 4:44 PM, Kevin Cussick via Groups.Io wrote:
Well yes, but first You need the driver the RH voice nvda addon.

On 21/02/2020 22:35, Rosemarie Chavarria wrote:
I think so. Isn't Alan just a voice?



On 2/21/2020 2:32 PM, Kevin Cussick via Groups.Io wrote:
Hi,   do You have the addon for the sinth installed?

On 21/02/2020 22:22, Rosemarie Chavarria wrote:
I hit enter on the add-on but it wouldn't install. What do I do now?



On 2/21/2020 2:01 PM, Kevin Cussick via Groups.Io wrote:
Hi,   OK just hit enter on the addon and as long as nvda is running it should just install.

On 21/02/2020 03:37, Rosemarie Chavarria wrote:
Hi, everyone,


How do I install the RH voice Alan to the other voices? It's in the add-ons list but I can't install it. I forgot how to add an extra voice.


Thanks for your help in advance.


Rosemarie











Re: When creating a input gesture, is there a way to know you're not creating a Windows 10 keyboard shortcut?

Luke
 

A quick note here. It was a new document I opened in Libre Office so if I press control S, a save as dialogue box will come up Because I have not named the document yet as opposed to A saved document If I open a document that I have saved and bring it up and then press control S,It will save it but no save as dialogue box will come up because it already has a name. If I want to rename  The document I have to go to file and arrow down to save as.     

On Feb 23, 2020, at 3:27 PM, Luke via Groups.Io <bugsyman35@...> wrote:


Hmm, Now I’m curious If I  Would have  pressed NVDA + F2 to pass the next key through, I wonder if that would have worked. Maybe I will try that tomorrow as I am done with the PC for today. Oh, And I did have a document open in Libre office  when I pressed control S. Thanks for your information and help.   
On Feb 23, 2020, at 2:46 PM, Brian Vogel <britechguy@...> wrote:

Well, remember that all keyboard shortcuts are context sensitive.

CTRL+S only works under Windows where it makes sense for it to work, which is a very limited number of circumstances.

The CTRL+S instances you describe are actually ones that would be handled by the programs over which NVDA is running.  Since NVDA is allowing you to create a shortcut that is the same, the hierarchy I described before is still in effect.  Windows ignores it, NVDA gets it and processes it, and nothing further happens.   You could, of course, use the NVDA pass-through command to override that CTRL+S and pass it to the program just to test this out.  If you did, whether in Firefox or Libre Office, they should then be passed the CTRL+S for processing.  And even then, they'll only process it if the context is correct that a Save can be done.  If you had not opened any file in Libre Office, a Save command is ignored.

All of the above being said, you are trying to do the absolutely most sensible thing and that is to create a keyboard shortcut that is unique to NVDA for the purpose intended.  It makes life so much easier that way!
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: When creating a input gesture, is there a way to know you're not creating a Windows 10 keyboard shortcut?

Luke
 

Hmm, Now I’m curious If I  Would have  pressed NVDA + F2 to pass the next key through, I wonder if that would have worked. Maybe I will try that tomorrow as I am done with the PC for today. Oh, And I did have a document open in Libre office  when I pressed control S. Thanks for your information and help.   

On Feb 23, 2020, at 2:46 PM, Brian Vogel <britechguy@...> wrote:

Well, remember that all keyboard shortcuts are context sensitive.

CTRL+S only works under Windows where it makes sense for it to work, which is a very limited number of circumstances.

The CTRL+S instances you describe are actually ones that would be handled by the programs over which NVDA is running.  Since NVDA is allowing you to create a shortcut that is the same, the hierarchy I described before is still in effect.  Windows ignores it, NVDA gets it and processes it, and nothing further happens.   You could, of course, use the NVDA pass-through command to override that CTRL+S and pass it to the program just to test this out.  If you did, whether in Firefox or Libre Office, they should then be passed the CTRL+S for processing.  And even then, they'll only process it if the context is correct that a Save can be done.  If you had not opened any file in Libre Office, a Save command is ignored.

All of the above being said, you are trying to do the absolutely most sensible thing and that is to create a keyboard shortcut that is unique to NVDA for the purpose intended.  It makes life so much easier that way!
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: When creating a input gesture, is there a way to know you're not creating a Windows 10 keyboard shortcut?

 

Well, remember that all keyboard shortcuts are context sensitive.

CTRL+S only works under Windows where it makes sense for it to work, which is a very limited number of circumstances.

The CTRL+S instances you describe are actually ones that would be handled by the programs over which NVDA is running.  Since NVDA is allowing you to create a shortcut that is the same, the hierarchy I described before is still in effect.  Windows ignores it, NVDA gets it and processes it, and nothing further happens.   You could, of course, use the NVDA pass-through command to override that CTRL+S and pass it to the program just to test this out.  If you did, whether in Firefox or Libre Office, they should then be passed the CTRL+S for processing.  And even then, they'll only process it if the context is correct that a Save can be done.  If you had not opened any file in Libre Office, a Save command is ignored.

All of the above being said, you are trying to do the absolutely most sensible thing and that is to create a keyboard shortcut that is unique to NVDA for the purpose intended.  It makes life so much easier that way!
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: When creating a input gesture, is there a way to know you're not creating a Windows 10 keyboard shortcut?

Luke
 

Hi! After I read your reply I did do what you suggested. I erased my old input gesture for screen curtain And used control S And yes, NVDA let me assign that command. so after that I went to the fire fox browser and pressed control S end it toggled The screen curtain, so, no save as dialogue box came up. for confirmation I tried it out in  Libre office and I got the same result. so beware, NVDA does override windows 10 keyboard shortcut commands. At least with that instance. That can create potential confusion. That would be cool if one Turned on the input help on And let’s say I pressed control S the input would tell me the windows keyboard shortcuts as well.  On Feb 23, 2020, at 12:43 PM, Brian Vogel <britechguy@...> wrote:

Luke,

          The easiest way to determine what will happen is to intentionally create (or attempt to create) an NVDA input gesture that you know to also be a Windows Keyboard Shortcut and see what happens.

           There is an order of precedence in the processing of keyboard shortcuts:

1.  Windows
2.  Screen Reader
3.  Program being controlled by screen reader.

My guess is that even were NVDA to allow you to create an input gesture that is already a Windows keyboard shortcut, it will never be seen by NVDA to begin with, as Windows will snag and process any keyboard shortcut it recognizes first, and that is then no longer passed down to anything lower in the order of precedence.

Try creating one and then report back on what happens (or doesn't happen).  I would expect that NVDA probably filters for known Windows keyboard shortcuts as part of input gesture creation, but I do not know this for certain.

--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: NVDA log

Jackie
 

Ok, but, nonetheless, the log entries will differ w/the addons
disabled. It'll pose less of a distraction.

On 2/23/20, brice Mijares <bmijares33@...> wrote:
Jackie, I again disabled add ons. I'll work with it this way for a while
again annd see if it happens again.

On 2/23/2020 10:43 AM, Jackie wrote:
Brice, please consider disabling all addons & then see if insert q
works. Please also insure that the capslock or number pad insert keys
are checked if you're trying to use them.

It's really not very fair to ask the NVDA developers to troubleshoot
an issue w/addons enabled, as the problem could be caused by an issue
unrelated to core NVDA functionality. If the problem persists w/the
addons disabled, then that's a different matter altogether. I suspect
that's not the case, as this is obviously not a problem most folks are
having & is therefore essentially localized to your particular
situation.

Again, please try disabling all addons & see if the problem persists.
If it does not, then re-enable addons 1 at a time, trying to use
insert q after each addon is enabled until the keystroke no longer
works.

The other thing is, might you have inadvertently gone into input
gestures & changed the keystroke? In that case, then it can be fixed
via the input gestures pane, or uninstalling NVDA along w/user
configuration files & then reinstalling.

I hope these comments help. They're not meant to be critical.

On 2/23/20, brice Mijares <bmijares33@...> wrote:
who do I send my NVDA log to. I'm still having a problem with NVDA key Q
to quit or restart NVDA. I've already uninstalled NVDA and reinstalled.

here is a copy of the log.

DEBUG - __main__ (10:16:58.170) - MainThread (9456):
Provided arguments: ['C:\\Program Files (x86)\\NVDA\\nvda.exe', '-r',
'--debug-logging']
INFO - __main__ (10:16:58.170) - MainThread (9456):
Starting NVDA version 2019.3.1
DEBUG - __main__ (10:16:58.170) - MainThread (9456):
Debug level logging enabled
DEBUG - core.main (10:16:58.463) - MainThread (9456):
Core starting
INFO - core.main (10:16:58.463) - MainThread (9456):
Config dir: C:\Users\Owner\AppData\Roaming\nvda
DEBUG - core.main (10:16:58.463) - MainThread (9456):
loading config
INFO - config.ConfigManager._loadConfig (10:16:58.463) - MainThread
(9456):
Loading config: C:\Users\Owner\AppData\Roaming\nvda\nvda.ini
DEBUG - config.profileUpgrader.upgrade (10:16:58.479) - MainThread
(9456):
Current config schema version: 3, latest: 3
DEBUG - fileUtils.FaultTolerantFile (10:16:58.494) - MainThread (9456):
C:\Users\Owner\AppData\Roaming\nvda\nvda.inixgzn8ybf.tmp
INFO - config.ConfigManager._loadConfig (10:16:58.579) - MainThread
(9456):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{'schemaVersion': '3', 'upgrade': {}, 'update': {'autoCheck': 'True',
'startupNotification': 'True', 'allowUsageStats': 'True',
'askedAllowUsageStats': 'True'}, 'general':
{'showWelcomeDialogAtStartup': 'False', 'language': 'Windows',
'saveConfigurationOnExit': 'True', 'askToExit': 'True',
'playStartAndExitSounds': 'True', 'loggingLevel': 'INFO'}, 'speech':
{'synth': 'oneCore', 'outputDevice': 'Microsoft Sound Mapper', 'espeak':
{'voice': 'en', 'variant': 'max', 'rate': '30', 'pitch': '40',
'inflection': '75', 'volume': '100'}, 'sapi5': {'voice':
'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\TTS_MS_EN-US_DAVID_11.0',

'volume': '100', 'rate': '65', 'beepForCapitals': 'True', 'pitch':
'55'}, 'oneCore': {'voice':
'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech_OneCore\\Voices\\Tokens\\MSTTS_V110_enUS_DavidM',

'volume': '100', 'rate': '20', 'pitch': '50', 'rateBoost': 'True'},
'dectalk': {'voice': 'Paul', 'rate': '55', 'pitch': '17', 'inflection':
'40'}}, 'braille': {'autoTether': 'False', 'tetherTo': 'review',
'noBraille': {'port': ''}}, 'keyboard': {'useCapsLockAsNVDAModifierKey':
'True', 'speakTypedCharacters': 'True', 'speakTypedWords': 'False',
'speakCommandKeys': 'False', 'beepForLowercaseWithCapslock': 'True'},
'mouse': {'enableMouseTracking': 'True'}, 'wintenApps':
{'updateCheckTime': '1536927831'}, 'audio': {'audioDuckingMode': '1'},
'virtualBuffers': {'useScreenLayout': 'False',
'autoFocusFocusableElements': 'True'}, 'reviewCursor': {'followFocus':
'False', 'followCaret': 'True'}, 'uwpOcr': {'language': 'en-US'},
'documentFormatting': {'autoLanguageSwitching': 'True',
'reportClickable': 'False'}, 'presentation': {'reportTooltips': 'True',
'reportDynamicContentChanges': 'True', 'progressBarUpdates':
{'progressBarOutputMode': 'beep'}}, 'clipContentsDesigner':
{'confirmToCopy': 'True', 'confirmToCut': 'True', 'separator': ''},
'textnav': {'crackleVolume': '35'}, 'screenCurtain': {'active':
'False'}, 'development': {}, 'speechViewer': {'x': '68', 'y': '44',
'width': '500', 'height': '500', 'displays': ['(1366, 768)'],
'autoPositionWindow': 'False'}, 'vision': {'NVDAHighlighter':
{'highlightFocus': 'False', 'highlightNavigator': 'False',
'highlightBrowseMode': 'False'}, 'screenCurtain': {}}}
DEBUG - core.main (10:16:58.679) - MainThread (9456):
setting language to Windows
INFO - core.main (10:16:58.679) - MainThread (9456):
Using Windows version 10.0.18363 workstation
INFO - core.main (10:16:58.679) - MainThread (9456):
Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019,
23:09:19) [MSC v.1916 32 bit (Intel)]
INFO - core.main (10:16:58.679) - MainThread (9456):
Using comtypes version 1.1.7
INFO - core.main (10:16:58.679) - MainThread (9456):
Using configobj version 5.1.0 with validate version 1.0.1
DEBUG - core.main (10:16:58.705) - MainThread (9456):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.710) -
MainThread (9456):
Listing add-ons from C:\Users\Owner\AppData\Roaming\nvda\addons
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.710) -
MainThread (9456):
Loading add-on from
C:\Users\Owner\AppData\Roaming\nvda\addons\addonUpdater
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.710) -
MainThread (9456):
Found add-on addonUpdater - 20.02.2. Requires API: (2019, 2, 0).
Last-tested API: (2020, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.710) -
MainThread (9456):
Loading add-on from C:\Users\Owner\AppData\Roaming\nvda\addons\clipspeak
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.715) -
MainThread (9456):
Found add-on clipspeak - 1.1. Requires API: (2018, 3, 0). Last-tested
API: (2019, 3, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.715) -
MainThread (9456):
Loading add-on from C:\Users\Owner\AppData\Roaming\nvda\addons\remote
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.720) -
MainThread (9456):
Found add-on remote - 2.3. Requires API: (2019, 3, 0). Last-tested API:
(2019, 3, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.720) -
MainThread (9456):
Loading add-on from
C:\Users\Owner\AppData\Roaming\nvda\addons\resourceMonitor
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.720) -
MainThread (9456):
Found add-on resourceMonitor - 20.01. Requires API: (2019, 3, 0).
Last-tested API: (2019, 3, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.720) -
MainThread (9456):
Loading add-on from
C:\Users\Owner\AppData\Roaming\nvda\addons\systrayList
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.725) -
MainThread (9456):
Found add-on systrayList - 4.0. Requires API: (2019, 3, 0). Last-tested
API: (2019, 3, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.725) -
MainThread (9456):
Loading add-on from
C:\Users\Owner\AppData\Roaming\nvda\addons\wintenApps
DEBUG - addonHandler._getAvailableAddonsFromPath (10:16:58.725) -
MainThread (9456):
Found add-on wintenApps - 20.02.1. Requires API: (2019, 3, 0).
Last-tested API: (2020, 1, 0)
DEBUGWARNING - touchHandler.touchSupported (10:16:59.035) - MainThread
(9456):
No touch devices found
DEBUG - core.main (10:16:59.310) - MainThread (9456):
Initializing appModule Handler
DEBUG - addonHandler.Addon.addToPackagePath (10:16:59.310) - MainThread
(9456):
Addon wintenApps added to appModules package path
DEBUG - core.main (10:16:59.315) - MainThread (9456):
Initializing NVDAHelper
DEBUG - core.main (10:16:59.440) - MainThread (9456):
Initializing tones
DEBUG - core.main (10:16:59.460) - MainThread (9456):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (10:16:59.460) - MainThread
(9456):
Loading speech dictionary
'C:\Users\Owner\AppData\Roaming\nvda\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (10:16:59.460) - MainThread
(9456):
file 'C:\Users\Owner\AppData\Roaming\nvda\speechDicts\default.dic' not
found.
DEBUG - speechDictHandler.SpeechDict.load (10:16:59.460) - MainThread
(9456):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (10:16:59.470) - MainThread
(9456):
3 loaded records.
DEBUG - core.main (10:16:59.470) - MainThread (9456):
Initializing speech
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(10:16:59.480) - MainThread (9456):
registering pre_configSave action: <class
'synthDrivers.oneCore.SynthDriver'>
DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid
(10:16:59.765) - MainThread (9456):
Could not open registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_GeorgeM,

FileNotFoundError(2, 'The system cannot find the file specified', None,
2, None)
DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid
(10:16:59.765) - MainThread (9456):
Could not open registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_SusanM,

FileNotFoundError(2, 'The system cannot find the file specified', None,
2, None)
DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid
(10:16:59.765) - MainThread (9456):
Could not open registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_HazelM,

FileNotFoundError(2, 'The system cannot find the file specified', None,
2, None)
DEBUG - speechDictHandler.SpeechDict.load (10:16:59.790) - MainThread
(9456):
Loading speech dictionary
'C:\Users\Owner\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\oneCore\oneCore-Microsoft

David.dic'...
DEBUG - speechDictHandler.SpeechDict.load (10:16:59.790) - MainThread
(9456):
file
'C:\Users\Owner\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\oneCore\oneCore-Microsoft

David.dic' not found.
DEBUG - synthDriverHandler.SynthDriver.loadSettings (10:16:59.790) -
MainThread (9456):
Loaded settings for SynthDriver oneCore
INFO - synthDriverHandler.setSynth (10:16:59.790) - MainThread (9456):
Loaded synthDriver oneCore
INFO - core.main (10:16:59.790) - MainThread (9456):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version
1.12.0
DEBUG - core.main (10:16:59.801) - MainThread (9456):
Initializing braille input
INFO - brailleInput.initialize (10:16:59.801) - MainThread (9456):
Braille input initialized
DEBUG - core.main (10:16:59.801) - MainThread (9456):
Initializing braille
INFO - braille.initialize (10:16:59.801) - MainThread (9456):
Using liblouis version 3.10.0
INFO - braille.initialize (10:16:59.803) - MainThread (9456):
Using pySerial version 3.4
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(10:16:59.811) - MainThread (9456):
registering pre_configSave action: <class
'brailleDisplayDrivers.noBraille.BrailleDisplayDriver'>
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(10:16:59.822) - MainThread (9456):
loading braille noBraille
INFO - braille.BrailleHandler.setDisplayByName (10:16:59.824) -
MainThread (9456):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (10:16:59.824) - MainThread (9456):
Initializing vision
DEBUG - core.main (10:16:59.824) - MainThread (9456):
Initializing displayModel
DEBUG - core.main (10:16:59.824) - MainThread (9456):
Initializing GUI
DEBUG - windowUtils._rawWindowProc (10:16:59.860) - MainThread (9456):
CustomWindow rawWindowProc called for unknown window 328168
DEBUG - windowUtils._rawWindowProc (10:16:59.860) - MainThread (9456):
CustomWindow rawWindowProc called for unknown window 328168
DEBUG - windowUtils._rawWindowProc (10:16:59.860) - MainThread (9456):
CustomWindow rawWindowProc called for unknown window 328168
DEBUG - windowUtils._rawWindowProc (10:16:59.860) - MainThread (9456):
CustomWindow rawWindowProc called for unknown window 328168
DEBUG - core.main (10:16:59.880) - MainThread (9456):
initializing Java Access Bridge support
INFO - core.main (10:17:00.204) - MainThread (9456):
Java Access Bridge support initialized
DEBUG - core.main (10:17:00.204) - MainThread (9456):
Initializing legacy winConsole support
DEBUG - core.main (10:17:00.204) - MainThread (9456):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (10:17:00.242) -
_UIAHandler.UIAHandler.MTAThread (9084):
UIAutomation: IUIAutomation6
DEBUG - core.main (10:17:00.358) - MainThread (9456):
Initializing IAccessible support
DEBUG - core.main (10:17:00.358) - MainThread (9456):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap
(10:17:00.374) - MainThread (9456):
No locale gesture map for language en
DEBUG - core.main (10:17:00.374) - MainThread (9456):
Initializing keyboard handler
DEBUG - core.main (10:17:00.374) - MainThread (9456):
initializing mouse handler
DEBUG - core.main (10:17:00.458) - MainThread (9456):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (10:17:00.458) - MainThread
(9456):
No touch devices found
DEBUG - core.main (10:17:00.458) - MainThread (9456):
Initializing global plugin handler
DEBUG - addonHandler.Addon.addToPackagePath (10:17:00.458) - MainThread
(9456):
Addon addonUpdater added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:17:00.458) - MainThread
(9456):
Addon clipspeak added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:17:00.458) - MainThread
(9456):
Addon remote added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:17:00.458) - MainThread
(9456):
Addon resourceMonitor added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:17:00.458) - MainThread
(9456):
Addon systrayList added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:17:00.458) - MainThread
(9456):
Addon wintenApps added to globalPlugins package path
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:17:00.458) - MainThread (9456):
W10: adding additional events
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:17:00.474) - MainThread (9456):
W10: added event ID 20026, assigned to UIA_dragStart
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:17:00.474) - MainThread (9456):
W10: added event ID 20027, assigned to UIA_dragCancel
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:17:00.474) - MainThread (9456):
W10: added event ID 20028, assigned to UIA_dragComplete
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:17:00.474) - MainThread (9456):
W10: added event ID 20029, assigned to UIA_dragEnter
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:17:00.474) - MainThread (9456):
W10: added event ID 20030, assigned to UIA_dragLeave
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:17:00.490) - MainThread (9456):
W10: added event ID 20031, assigned to UIA_dragDropped
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:17:00.490) - MainThread (9456):
W10: adding class name Popup to known dialog class names
DEBUG - windowUtils._rawWindowProc (10:17:00.559) - MainThread (9456):
CustomWindow rawWindowProc called for unknown window 918472
DEBUG - windowUtils._rawWindowProc (10:17:00.559) - MainThread (9456):
CustomWindow rawWindowProc called for unknown window 918472
DEBUG - windowUtils._rawWindowProc (10:17:00.559) - MainThread (9456):
CustomWindow rawWindowProc called for unknown window 918472
DEBUG - windowUtils._rawWindowProc (10:17:00.559) - MainThread (9456):
CustomWindow rawWindowProc called for unknown window 918472
DEBUG -
external:globalPlugins.clipspeak.clipboard_monitor.clipboard_monitor.__init__

(10:17:00.574) - MainThread (9456):
Initialising clipboard monitor.
DEBUG -
external:globalPlugins.clipspeak.clipboard_monitor.clipboard_monitor.get_clipboard

(10:17:00.574) - MainThread (9456):
Enumerating clipboard data...
DEBUG -
external:globalPlugins.clipspeak.clipboard_monitor.clipboard_monitor.enumerate_clipboard

(10:17:00.574) - MainThread (9456):
Opening the clipboard for enumeration.
DEBUG -
external:globalPlugins.clipspeak.clipboard_monitor.clipboard_monitor.enumerate_clipboard

(10:17:00.574) - MainThread (9456):
Retrieving clipboard format: 0
DEBUG -
external:globalPlugins.clipspeak.clipboard_monitor.clipboard_monitor.enumerate_clipboard

(10:17:00.574) - MainThread (9456):
Closing clipboard.
DEBUG - core.main (10:17:00.590) - MainThread (9456):
Initializing core pump
DEBUG - core.main (10:17:00.590) - MainThread (9456):
Initializing watchdog
DEBUG - core.main (10:17:00.606) - MainThread (9456):
initializing updateCheck
INFO - core.main (10:17:00.606) - MainThread (9456):
NVDA initialized
DEBUG - core.main (10:17:00.606) - MainThread (9456):
entering wx application main loop
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(10:17:00.606) - MainThread (9456):
registering pre_configSave action: <class
'visionEnhancementProviders.NVDAHighlighter.NVDAHighlighterSettings'>
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(10:17:00.621) - MainThread (9456):
loading vision NVDAHighlighter
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(10:17:00.621) - MainThread (9456):
Loaded settings for NVDAHighlighterSettings
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(10:17:00.637) - MainThread (9456):
registering pre_configSave action: <class
'visionEnhancementProviders.screenCurtain.ScreenCurtainSettings'>
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(10:17:00.643) - MainThread (9456):
loading vision screenCurtain
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(10:17:00.643) - MainThread (9456):
Loaded settings for ScreenCurtainSettings
IO - speech.speak (10:17:00.706) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Desktop', 'list']
DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale
(10:17:00.706) - MainThread (9456):
No CLDR data for locale en_US
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:00.991) -
MainThread (9456):
Begin processing speech
IO - speech.speak (10:17:01.060) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'This PC', '2 of 15']
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:01.779) -
Dummy-1 (2796):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:01.779) -
Dummy-1 (2796):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:01.899) -
Dummy-1 (2796):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:03.019) -
Dummy-1 (2796):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:03.019) -
Dummy-1 (2796):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:03.144) -
Dummy-1 (2796):
Queue empty, done processing
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:17:42.596) -
MainThread (9456):
Cancelling
IO - inputCore.InputManager.executeGesture (10:17:44.461) - winInputHook
(6892):
Input: kb(desktop):NVDA+n
IO - speech.speak (10:17:44.608) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'NVDA', 'menu']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:44.624) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:45.430) -
Dummy-2 (10664):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:45.430) -
Dummy-2 (10664):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:45.555) -
Dummy-2 (10664):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:17:47.543) - winInputHook
(6892):
Input: kb(desktop):upArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:17:47.558) -
MainThread (9456):
Cancelling
IO - speech.speak (10:17:47.583) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Exit', 'x']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:47.596) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:48.125) -
Dummy-2 (10664):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:48.125) -
Dummy-2 (10664):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:48.245) -
Dummy-2 (10664):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:17:48.365) - winInputHook
(6892):
Input: kb(desktop):upArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:17:48.394) -
MainThread (9456):
Cancelling
IO - speech.speak (10:17:48.405) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Donate', 'd']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:48.424) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:48.895) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:48.895) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:49.025) -
Dummy-3 (10456):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:17:49.195) - winInputHook
(6892):
Input: kb(desktop):upArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:17:49.230) -
MainThread (9456):
Cancelling
IO - speech.speak (10:17:49.235) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Save configuration', 's']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:49.254) -
MainThread (9456):
Begin processing speech
IO - inputCore.InputManager.executeGesture (10:17:50.165) - winInputHook
(6892):
Input: kb(desktop):upArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:17:50.190) -
MainThread (9456):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:50.194) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:50.194) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:50.194) -
Dummy-3 (10456):
Queue empty, done processing
IO - speech.speak (10:17:50.205) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Reset configuration to factory
defaults', 'r']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:50.225) -
MainThread (9456):
Begin processing speech
IO - inputCore.InputManager.executeGesture (10:17:51.235) - winInputHook
(6892):
Input: kb(desktop):upArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:17:51.255) -
MainThread (9456):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:51.274) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:51.274) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:51.274) -
Dummy-3 (10456):
Queue empty, done processing
IO - speech.speak (10:17:51.289) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Revert to saved configuration',
'r']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:51.305) -
MainThread (9456):
Begin processing speech
IO - inputCore.InputManager.executeGesture (10:17:52.225) - winInputHook
(6892):
Input: kb(desktop):upArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:17:52.260) -
MainThread (9456):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:52.275) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:52.275) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:52.275) -
Dummy-3 (10456):
Queue empty, done processing
IO - speech.speak (10:17:52.290) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Configuration profiles...', 'c']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:52.304) -
MainThread (9456):
Begin processing speech
IO - inputCore.InputManager.executeGesture (10:17:54.005) - winInputHook
(6892):
Input: kb(desktop):upArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:17:54.044) -
MainThread (9456):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:54.054) -
Dummy-4 (1616):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:54.054) -
Dummy-4 (1616):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:54.054) -
Dummy-4 (1616):
Queue empty, done processing
IO - speech.speak (10:17:54.054) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Help', 'subMenu', 'h']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:54.074) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:54.904) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:54.904) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:55.035) -
Dummy-3 (10456):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:17:58.119) - winInputHook
(6892):
Input: kb(desktop):enter
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:17:58.141) -
MainThread (9456):
Cancelling
IO - speech.speak (10:17:58.156) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'User Guide', 'u']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:58.172) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:17:58.855) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:58.855) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:58.975) -
Dummy-3 (10456):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:17:59.442) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:17:59.461) -
MainThread (9456):
Cancelling
IO - speech.speak (10:17:59.461) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Commands Quick Reference', 'q']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:17:59.476) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:00.487) -
Dummy-4 (1616):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:00.487) -
Dummy-4 (1616):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:00.612) -
Dummy-4 (1616):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:00.738) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:00.762) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:00.777) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), "What's new", 'n']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:00.787) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:01.397) -
Dummy-4 (1616):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:01.397) -
Dummy-4 (1616):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:01.537) -
Dummy-4 (1616):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:01.707) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:01.742) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:01.747) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'NVDA web site', 'w']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:01.767) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:02.957) -
Dummy-4 (1616):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:02.957) -
Dummy-4 (1616):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:03.077) -
Dummy-4 (1616):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:03.702) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:03.718) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:03.733) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'License', 'i']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:03.749) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:04.250) -
Dummy-5 (10900):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:04.250) -
Dummy-5 (10900):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:04.370) -
Dummy-5 (10900):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:04.590) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:04.610) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:04.620) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Contributors', 'o']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:04.639) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:05.329) -
Dummy-5 (10900):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:05.329) -
Dummy-5 (10900):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:05.460) -
Dummy-5 (10900):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:05.520) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:05.545) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:05.559) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Welcome dialog...', 'l']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:05.580) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:07.080) -
Dummy-5 (10900):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:07.080) -
Dummy-5 (10900):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:07.219) -
Dummy-5 (10900):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:07.490) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:07.514) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:07.519) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Check for update...', 'c']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:07.549) -
MainThread (9456):
Begin processing speech
IO - inputCore.InputManager.executeGesture (10:18:08.910) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:08.935) -
MainThread (9456):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:08.950) -
Dummy-5 (10900):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:08.950) -
Dummy-5 (10900):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:08.950) -
Dummy-5 (10900):
Queue empty, done processing
IO - speech.speak (10:18:08.964) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'About...', 'a']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:08.984) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:10.000) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:10.000) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:10.129) -
Dummy-3 (10456):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:11.532) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:11.548) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:11.563) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'User Guide', 'u']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:11.587) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:12.265) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:12.265) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:12.384) -
Dummy-3 (10456):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:12.624) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:12.642) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:12.653) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Commands Quick Reference', 'q']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:12.673) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:13.684) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:13.684) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:13.804) -
Dummy-3 (10456):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:17.739) - winInputHook
(6892):
Input: kb(desktop):leftArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:17.768) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:17.782) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Help', 'subMenu', 'h']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:17.796) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:18.627) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:18.627) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:18.747) -
Dummy-3 (10456):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:19.077) - winInputHook
(6892):
Input: kb(desktop):upArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:19.104) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:19.117) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Tools', 'subMenu', 't']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:19.127) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:19.929) -
Dummy-4 (1616):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:19.929) -
Dummy-4 (1616):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:20.049) -
Dummy-4 (1616):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:22.391) - winInputHook
(6892):
Input: kb(desktop):enter
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:22.440) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:22.440) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'View log', 'v']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:22.456) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:23.024) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:23.024) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:23.145) -
Dummy-3 (10456):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:24.833) - winInputHook
(6892):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:24.856) -
MainThread (9456):
Cancelling
IO - speech.speak (10:18:24.856) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'Speech viewer', 's']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:24.887) -
MainThread (9456):
Begin processing speech
IO - inputCore.InputManager.executeGesture (10:18:25.668) - winInputHook
(6892):
Input: kb(desktop):upArrow
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:25.683) -
Dummy-3 (10456):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:25.683) -
Dummy-3 (10456):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:18:25.688) -
MainThread (9456):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:25.698) -
Dummy-3 (10456):
Queue empty, done processing
DEBUG - speech.manager.SpeechManager._handleIndex (10:18:25.698) -
MainThread (9456):
Unknown index 25, speech probably cancelled from main thread.
IO - speech.speak (10:18:25.708) - MainThread (9456):
Speaking [LangChangeCommand ('en_US'), 'View log', 'v']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:25.723) -
MainThread (9456):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:18:26.268) -
Dummy-4 (1616):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:26.268) -
Dummy-4 (1616):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:18:26.408) -
Dummy-4 (1616):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (10:18:31.693) - winInputHook
(6892):
Input: kb(desktop):enter







--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brighter-vision.com & www.mysitesbeenhacked.com