Date   
Re: NVDA and older synthesizers question

Roger Stewart
 

There were add ons for the external DecTalk Express as well as DoubleTalk. They were both buggy, but they did talk. However, the person who did them has just gone away and I know of no one who is working on these anymore. If you like, I can send them to you and you can play with them but they are full of bugs in that not everything is spoken correctly.
Roger

On 12/11/2019 11:23 AM, Howard Traxler wrote:
I have an older computer that I need to make talk.  It has no sound card nor sound drivers to my knowledge.  I'd like to start a portable copy of NVDA using a USB thumb drive or a floppy and an external synthersizer.  I haven't found anything in the users' guide about legacy synthesizers.  I have several, dectalks, echos liteTalks, etc.  Once I get it talking, I can install and set up whatever is necessary.

Thanks for your ideas.

Howard


NVDA and older synthesizers question

Howard Traxler
 

I have an older computer that I need to make talk.  It has no sound card nor sound drivers to my knowledge.  I'd like to start a portable copy of NVDA using a USB thumb drive or a floppy and an external synthersizer.  I haven't found anything in the users' guide about legacy synthesizers.  I have several, dectalks, echos liteTalks, etc.  Once I get it talking, I can install and set up whatever is necessary.

Thanks for your ideas.

Howard

Re: NVDA 2019.3Beta1 and devices's manager

bering.p
 

Oups !!!
Thanks Joseph.
I forgot to check this parameter in the NVDA.exe sortcut's properties
An idea: perhaps, it will be usefull to suggest that during the creation of the NVDA copy.
Best regards.
Paul.

Le 11/12/2019 17:19, Joseph Lee a écrit :
Hi,
You say you are using portable copy of NVDA? This is the reason: you need to run NVDA with admin rights before you can access Device Manager.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of bering.p
Sent: Wednesday, December 11, 2019 6:49 AM
To: nvda courrier <nvda@nvda.groups.io>
Subject: [nvda] NVDA 2019.3Beta1 and devices's manager

Hi,
Today, I found that I could not read the items of the devices's manager.
I am running W10 1909 french system, NVDA 2019.3Beta1 portable copy.
Do you have the same problem on your PC ?
The NVDA log is below.
Thanks.
Best regards.
Paul.


The log:
INFO - __main__ (15:21:39.178) - MainThread (6780):
Starting NVDA version 2019.3beta1
INFO - core.main (15:21:39.475) - MainThread (6780):
Config dir: F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig INFO - config.ConfigManager._loadConfig (15:21:39.475) - MainThread (6780):
Loading config: .\userConfig\nvda.ini
INFO - config.ConfigManager._loadConfig (15:21:39.537) - MainThread (6780):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{'schemaVersion': '3', 'development': {}, 'general': {'language':
'Windows', 'saveConfigurationOnExit': 'False', 'askToExit': 'True',
'playStartAndExitSounds': 'True', 'loggingLevel': 'DEBUG',
'showWelcomeDialogAtStartup': 'False'}, 'update': {'autoCheck': 'True',
'startupNotification': 'True', 'allowUsageStats': 'False',
'askedAllowUsageStats': 'True'}, 'upgrade': {}, 'speech': {'synth':
'oneCore', 'outputDevice': 'Mappeur de sons Microsoft', 'oneCore':
{'voice':
'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech_OneCore\\Voices\\Tokens\\MSTTS_V110_frFR_HortenseM',
'volume': '90', 'rateBoost': 'True', 'rate': '19', 'pitch': '50'},
'sapi5': {'voice':
'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\TTS_MS_EN-US_ZIRA_11.0',
'volume': '88', 'capPitchChange': '55'}}, 'braille': {'noBraille': {}},
'vision': {'NVDAHighlighter': {'highlightFocus': 'False',
'highlightNavigator': 'False', 'highlightBrowseMode': 'False'},
'screenCurtain': {}}, 'keyboard': {'useCapsLockAsNVDAModifierKey':
'True'}, 'NVDAExtensionGlobalPlugin': {'voiceProfileSwitching':
{'configVersion': '2', 'lastSelector': '2', '2': {'activate': 'True',
'voiceProfileName': 'sapi5 Microsoft Zira Desktop - English (United
States) ', 'defaultVoiceProfileName': 'sapi5 Microsoft Zira Desktop - English (United States) ', 'synthName': 'sapi5', 'speech':
{'outputDevice': 'Mappeur de sons Microsoft', 'synth': 'sapi5',
'autoLanguageSwitching': 'True', 'autoDialectSwitching': 'False',
'trustVoiceLanguage': 'True', 'symbolLevel': '100', 'includeCLDR':
'True', 'beepSpeechModePitch': '10000', 'sapi5': {'voice':
'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\TTS_MS_EN-US_ZIRA_11.0',
'rate': '50', 'pitch': '50', 'volume': '88', 'capPitchChange': '55',
'sayCapForCapitals': 'False', 'beepForCapitals': 'False',
'useSpellingFunctionality': 'True'}, '__many__': {'capPitchChange':
'30', 'sayCapForCapitals': 'False', 'beepForCapitals': 'False',
'useSpellingFunctionality': 'True'}}, 'synthDisplayInfos': {'1':
['Voix', 'Microsoft Zira Desktop - English (United States)'], '2':
['Débit', '50'], '3': ['Hauteur', '50'], '4': ['Volume', '88']}}}}} DEBUG - core.main (15:21:39.709) - MainThread (6780):
setting language to Windows
INFO - core.main (15:21:39.709) - MainThread (6780):
Using Windows version 10.0.18363 workstation INFO - core.main (15:21:39.709) - MainThread (6780):
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 (15:21:39.709) - MainThread (6780):
Using comtypes version 1.1.7
INFO - core.main (15:21:39.709) - MainThread (6780):
Using configobj version 5.1.0 with validate version 1.0.1 DEBUG - core.main (15:21:39.730) - MainThread (6780):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.739) - MainThread (6780):
Listing add-ons from F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig\addons DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.739) - MainThread (6780):
Loading add-on from F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig\addons\NVDAExtensionGlobalPlugin
DEBUG - addonHandler.Addon.__init__ (15:21:39.739) - MainThread (6780):
Using manifest translation from F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig\addons\NVDAExtensionGlobalPlugin\locale\fr\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.744) - MainThread (6780):
Found add-on NVDAExtensionGlobalPlugin - 9.0-beta1. Requires API: (2019, 1, 0). Last-tested API: (2019, 3, 0) DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.744) - MainThread (6780):
Disabling add-on NVDAExtensionGlobalPlugin DEBUGWARNING - touchHandler.touchSupported (15:21:40.178) - MainThread
(6780):
Touch only supported on installed copies DEBUG - core.main (15:21:40.359) - MainThread (6780):
Initializing appModule Handler
DEBUG - core.main (15:21:40.359) - MainThread (6780):
Initializing NVDAHelper
DEBUG - core.main (15:21:40.438) - MainThread (6780):
Initializing tones
DEBUG - core.main (15:21:40.468) - MainThread (6780):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.468) - MainThread
(6780):
Loading speech dictionary '.\userConfig\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.468) - MainThread
(6780):
file '.\userConfig\speechDicts\default.dic' not found.
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.468) - MainThread
(6780):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.473) - MainThread
(6780):
3 loaded records.
DEBUG - core.main (15:21:40.473) - MainThread (6780):
Initializing speech
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(15:21:40.483) - MainThread (6780):
registering pre_configSave action: <class 'synthDrivers.oneCore.SynthDriver'>
DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid
(15:21:40.738) - MainThread (6780):
Could not open registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_frCA_CarolineM,
FileNotFoundError(2, 'Le fichier spécifié est introuvable', None, 2, None) DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid
(15:21:40.748) - MainThread (6780):
Could not open registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_frCA_ClaudeM,
FileNotFoundError(2, 'Le fichier spécifié est introuvable', None, 2, None) DEBUG - speechDictHandler.SpeechDict.load (15:21:40.779) - MainThread
(6780):
Loading speech dictionary
'.\userConfig\speechDicts\voiceDicts.v1\oneCore\oneCore-Microsoft
Hortense.dic'...
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.779) - MainThread
(6780):
file '.\userConfig\speechDicts\voiceDicts.v1\oneCore\oneCore-Microsoft
Hortense.dic' not found.
DEBUG - synthDriverHandler.SynthDriver.loadSettings (15:21:40.779) - MainThread (6780):
Loaded settings for SynthDriver oneCore
INFO - synthDriverHandler.setSynth (15:21:40.779) - MainThread (6780):
Loaded synthDriver oneCore
INFO - core.main (15:21:40.779) - MainThread (6780):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0 DEBUG - core.main (15:21:40.783) - MainThread (6780):
Initializing braille input
INFO - brailleInput.initialize (15:21:40.783) - MainThread (6780):
Braille input initialized
DEBUG - core.main (15:21:40.788) - MainThread (6780):
Initializing braille
INFO - braille.initialize (15:21:40.788) - MainThread (6780):
Using liblouis version 3.10.0
INFO - braille.initialize (15:21:40.798) - MainThread (6780):
Using pySerial version 3.4
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(15:21:40.798) - MainThread (6780):
registering pre_configSave action: <class 'brailleDisplayDrivers.noBraille.BrailleDisplayDriver'>
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(15:21:40.808) - MainThread (6780):
loading braille noBraille
INFO - braille.BrailleHandler.setDisplayByName (15:21:40.808) - MainThread (6780):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (15:21:40.808) - MainThread (6780):
Initializing vision
DEBUG - core.main (15:21:40.808) - MainThread (6780):
Initializing displayModel
DEBUG - core.main (15:21:40.808) - MainThread (6780):
Initializing GUI
DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552 DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552 DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552 DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552 DEBUG - core.main (15:21:40.908) - MainThread (6780):
initializing Java Access Bridge support
INFO - core.main (15:21:41.474) - MainThread (6780):
Java Access Bridge support initialized
DEBUG - core.main (15:21:41.480) - MainThread (6780):
Initializing legacy winConsole support
DEBUG - core.main (15:21:41.480) - MainThread (6780):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:21:41.527) - _UIAHandler.UIAHandler.MTAThread (7016):
UIAutomation: IUIAutomation6
DEBUG - core.main (15:21:41.728) - MainThread (6780):
Initializing IAccessible support
DEBUG - core.main (15:21:41.728) - MainThread (6780):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (15:21:41.743)
- MainThread (6780):
No user gesture map
DEBUG - core.main (15:21:41.743) - MainThread (6780):
Initializing keyboard handler
DEBUG - core.main (15:21:41.743) - MainThread (6780):
initializing mouse handler
DEBUG - core.main (15:21:41.859) - MainThread (6780):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (15:21:41.859) - MainThread
(6780):
Touch only supported on installed copies DEBUG - core.main (15:21:41.859) - MainThread (6780):
Initializing global plugin handler
DEBUG - core.main (15:21:41.875) - MainThread (6780):
Initializing core pump
DEBUG - core.main (15:21:41.875) - MainThread (6780):
Initializing watchdog
DEBUG - core.main (15:21:41.875) - MainThread (6780):
initializing updateCheck
INFO - core.main (15:21:41.875) - MainThread (6780):
NVDA initialized
DEBUG - core.main (15:21:41.875) - MainThread (6780):
entering wx application main loop
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(15:21:41.897) - MainThread (6780):
registering pre_configSave action: <class 'visionEnhancementProviders.NVDAHighlighter.NVDAHighlighterSettings'>
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(15:21:41.913) - MainThread (6780):
loading vision NVDAHighlighter
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(15:21:41.913) - MainThread (6780):
Loaded settings for NVDAHighlighterSettings DEBUG - autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(15:21:41.913) - MainThread (6780):
registering pre_configSave action: <class 'visionEnhancementProviders.screenCurtain.ScreenCurtainSettings'>
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(15:21:41.928) - MainThread (6780):
loading vision screenCurtain
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(15:21:41.928) - MainThread (6780):
Loaded settings for ScreenCurtainSettings IO - speech.speak (15:21:41.982) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Bureau', 'liste'] DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale
(15:21:41.982) - MainThread (6780):
No CLDR data for locale fr_FR
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:42.519) - MainThread (6780):
Begin processing speech
IO - speech.speak (15:21:42.637) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Documents Paulo', '19 sur 64'] DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:43.340) -
Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:43.340) -
Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:43.489) -
Dummy-1 (4592):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:45.519) -
Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:45.519) -
Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:21:45.539) - MainThread (6780):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:45.549) -
Dummy-1 (4592):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (15:21:45.670) - winInputHook
(7252):
Input: kb(desktop):alt+tab
IO - speech.speak (15:21:45.889) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Gestionnaire de périphériques', 'ligne 1', 'colonne 1'] DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:45.919) - MainThread (6780):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:47.635) -
Dummy-2 (5972):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:47.635) -
Dummy-2 (5972):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:21:47.635) - MainThread (6780):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:47.644) -
Dummy-2 (5972):
Queue empty, done processing
IO - speech.speak (15:21:47.644) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Gestionnaire de périphériques'] DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:47.675) - MainThread (6780):
Begin processing speech
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(15:21:47.700) - MainThread (6780):
accRole failed: (-2147024809, 'Paramètre incorrect.', (None, None, None, 0, None)) ERROR - eventHandler.executeEvent (15:21:47.734) - MainThread (6780):
error executing event: gainFocus on
<NVDAObjects.IAccessible.sysTreeView32.BrokenCommctrl5Item object at
0x03B4C2B0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 150, in executeEvent
File "eventHandler.pyc", line 163, in doPreGainFocus
File "api.pyc", line 109, in setFocusObject
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\__init__.pyc", line 536, in _get_container
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\IAccessible\sysTreeView32.pyc", line 261, in _get_parent
AttributeError: 'IAccessible' object has no attribute 'UIAElement'
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:48.835) -
Dummy-2 (5972):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:48.835) -
Dummy-2 (5972):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:48.998) -
Dummy-2 (5972):
Queue empty, done processing
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(15:21:49.417) - MainThread (6780):
accRole failed: (-2147024809, 'Paramètre incorrect.', (None, None, None, 0, None)) ERROR - eventHandler.executeEvent (15:21:49.432) - MainThread (6780):
error executing event: gainFocus on
<NVDAObjects.IAccessible.sysTreeView32.BrokenCommctrl5Item object at
0x03755EF0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 150, in executeEvent
File "eventHandler.pyc", line 163, in doPreGainFocus
File "api.pyc", line 109, in setFocusObject
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\__init__.pyc", line 536, in _get_container
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\IAccessible\sysTreeView32.pyc", line 261, in _get_parent
AttributeError: 'IAccessible' object has no attribute 'UIAElement'
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:21:54.209) - MainThread (6780):
Cancelling
IO - speech.speak (15:21:54.209) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Bureau', 'liste'] DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:54.240) - MainThread (6780):
Begin processing speech
IO - speech.speak (15:21:54.240) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Documents Paulo', '19 sur 64'] DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:54.922) -
Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:54.922) -
Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:55.076) -
Dummy-1 (4592):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:57.102) -
Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:57.102) -
Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:57.252) -
Dummy-1 (4592):
Queue empty, done processing
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:22:04.049) - MainThread (6780):
Cancelling
IO - inputCore.InputManager.executeGesture (15:22:04.265) - winInputHook
(7252):
Input: kb(desktop):NVDA+f1
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(15:22:04.535) - MainThread (6780):





Re: NVDA 2019.3Beta1 and devices's manager

 

Hi,
You say you are using portable copy of NVDA? This is the reason: you need to run NVDA with admin rights before you can access Device Manager.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of bering.p
Sent: Wednesday, December 11, 2019 6:49 AM
To: nvda courrier <nvda@nvda.groups.io>
Subject: [nvda] NVDA 2019.3Beta1 and devices's manager

Hi,
Today, I found that I could not read the items of the devices's manager.
I am running W10 1909 french system, NVDA 2019.3Beta1 portable copy.
Do you have the same problem on your PC ?
The NVDA log is below.
Thanks.
Best regards.
Paul.


The log:
INFO - __main__ (15:21:39.178) - MainThread (6780):
Starting NVDA version 2019.3beta1
INFO - core.main (15:21:39.475) - MainThread (6780):
Config dir: F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig INFO - config.ConfigManager._loadConfig (15:21:39.475) - MainThread (6780):
Loading config: .\userConfig\nvda.ini
INFO - config.ConfigManager._loadConfig (15:21:39.537) - MainThread (6780):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{'schemaVersion': '3', 'development': {}, 'general': {'language':
'Windows', 'saveConfigurationOnExit': 'False', 'askToExit': 'True',
'playStartAndExitSounds': 'True', 'loggingLevel': 'DEBUG',
'showWelcomeDialogAtStartup': 'False'}, 'update': {'autoCheck': 'True',
'startupNotification': 'True', 'allowUsageStats': 'False',
'askedAllowUsageStats': 'True'}, 'upgrade': {}, 'speech': {'synth':
'oneCore', 'outputDevice': 'Mappeur de sons Microsoft', 'oneCore':
{'voice':
'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech_OneCore\\Voices\\Tokens\\MSTTS_V110_frFR_HortenseM',
'volume': '90', 'rateBoost': 'True', 'rate': '19', 'pitch': '50'},
'sapi5': {'voice':
'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\TTS_MS_EN-US_ZIRA_11.0',
'volume': '88', 'capPitchChange': '55'}}, 'braille': {'noBraille': {}},
'vision': {'NVDAHighlighter': {'highlightFocus': 'False',
'highlightNavigator': 'False', 'highlightBrowseMode': 'False'},
'screenCurtain': {}}, 'keyboard': {'useCapsLockAsNVDAModifierKey':
'True'}, 'NVDAExtensionGlobalPlugin': {'voiceProfileSwitching':
{'configVersion': '2', 'lastSelector': '2', '2': {'activate': 'True',
'voiceProfileName': 'sapi5 Microsoft Zira Desktop - English (United
States) ', 'defaultVoiceProfileName': 'sapi5 Microsoft Zira Desktop - English (United States) ', 'synthName': 'sapi5', 'speech':
{'outputDevice': 'Mappeur de sons Microsoft', 'synth': 'sapi5',
'autoLanguageSwitching': 'True', 'autoDialectSwitching': 'False',
'trustVoiceLanguage': 'True', 'symbolLevel': '100', 'includeCLDR':
'True', 'beepSpeechModePitch': '10000', 'sapi5': {'voice':
'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\TTS_MS_EN-US_ZIRA_11.0',
'rate': '50', 'pitch': '50', 'volume': '88', 'capPitchChange': '55',
'sayCapForCapitals': 'False', 'beepForCapitals': 'False',
'useSpellingFunctionality': 'True'}, '__many__': {'capPitchChange':
'30', 'sayCapForCapitals': 'False', 'beepForCapitals': 'False',
'useSpellingFunctionality': 'True'}}, 'synthDisplayInfos': {'1':
['Voix', 'Microsoft Zira Desktop - English (United States)'], '2':
['Débit', '50'], '3': ['Hauteur', '50'], '4': ['Volume', '88']}}}}} DEBUG - core.main (15:21:39.709) - MainThread (6780):
setting language to Windows
INFO - core.main (15:21:39.709) - MainThread (6780):
Using Windows version 10.0.18363 workstation INFO - core.main (15:21:39.709) - MainThread (6780):
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 (15:21:39.709) - MainThread (6780):
Using comtypes version 1.1.7
INFO - core.main (15:21:39.709) - MainThread (6780):
Using configobj version 5.1.0 with validate version 1.0.1 DEBUG - core.main (15:21:39.730) - MainThread (6780):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.739) - MainThread (6780):
Listing add-ons from F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig\addons DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.739) - MainThread (6780):
Loading add-on from F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig\addons\NVDAExtensionGlobalPlugin
DEBUG - addonHandler.Addon.__init__ (15:21:39.739) - MainThread (6780):
Using manifest translation from F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig\addons\NVDAExtensionGlobalPlugin\locale\fr\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.744) - MainThread (6780):
Found add-on NVDAExtensionGlobalPlugin - 9.0-beta1. Requires API: (2019, 1, 0). Last-tested API: (2019, 3, 0) DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.744) - MainThread (6780):
Disabling add-on NVDAExtensionGlobalPlugin DEBUGWARNING - touchHandler.touchSupported (15:21:40.178) - MainThread
(6780):
Touch only supported on installed copies DEBUG - core.main (15:21:40.359) - MainThread (6780):
Initializing appModule Handler
DEBUG - core.main (15:21:40.359) - MainThread (6780):
Initializing NVDAHelper
DEBUG - core.main (15:21:40.438) - MainThread (6780):
Initializing tones
DEBUG - core.main (15:21:40.468) - MainThread (6780):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.468) - MainThread
(6780):
Loading speech dictionary '.\userConfig\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.468) - MainThread
(6780):
file '.\userConfig\speechDicts\default.dic' not found.
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.468) - MainThread
(6780):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.473) - MainThread
(6780):
3 loaded records.
DEBUG - core.main (15:21:40.473) - MainThread (6780):
Initializing speech
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(15:21:40.483) - MainThread (6780):
registering pre_configSave action: <class 'synthDrivers.oneCore.SynthDriver'>
DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid
(15:21:40.738) - MainThread (6780):
Could not open registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_frCA_CarolineM,
FileNotFoundError(2, 'Le fichier spécifié est introuvable', None, 2, None) DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid
(15:21:40.748) - MainThread (6780):
Could not open registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_frCA_ClaudeM,
FileNotFoundError(2, 'Le fichier spécifié est introuvable', None, 2, None) DEBUG - speechDictHandler.SpeechDict.load (15:21:40.779) - MainThread
(6780):
Loading speech dictionary
'.\userConfig\speechDicts\voiceDicts.v1\oneCore\oneCore-Microsoft
Hortense.dic'...
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.779) - MainThread
(6780):
file '.\userConfig\speechDicts\voiceDicts.v1\oneCore\oneCore-Microsoft
Hortense.dic' not found.
DEBUG - synthDriverHandler.SynthDriver.loadSettings (15:21:40.779) - MainThread (6780):
Loaded settings for SynthDriver oneCore
INFO - synthDriverHandler.setSynth (15:21:40.779) - MainThread (6780):
Loaded synthDriver oneCore
INFO - core.main (15:21:40.779) - MainThread (6780):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0 DEBUG - core.main (15:21:40.783) - MainThread (6780):
Initializing braille input
INFO - brailleInput.initialize (15:21:40.783) - MainThread (6780):
Braille input initialized
DEBUG - core.main (15:21:40.788) - MainThread (6780):
Initializing braille
INFO - braille.initialize (15:21:40.788) - MainThread (6780):
Using liblouis version 3.10.0
INFO - braille.initialize (15:21:40.798) - MainThread (6780):
Using pySerial version 3.4
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(15:21:40.798) - MainThread (6780):
registering pre_configSave action: <class 'brailleDisplayDrivers.noBraille.BrailleDisplayDriver'>
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(15:21:40.808) - MainThread (6780):
loading braille noBraille
INFO - braille.BrailleHandler.setDisplayByName (15:21:40.808) - MainThread (6780):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (15:21:40.808) - MainThread (6780):
Initializing vision
DEBUG - core.main (15:21:40.808) - MainThread (6780):
Initializing displayModel
DEBUG - core.main (15:21:40.808) - MainThread (6780):
Initializing GUI
DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552 DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552 DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552 DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552 DEBUG - core.main (15:21:40.908) - MainThread (6780):
initializing Java Access Bridge support
INFO - core.main (15:21:41.474) - MainThread (6780):
Java Access Bridge support initialized
DEBUG - core.main (15:21:41.480) - MainThread (6780):
Initializing legacy winConsole support
DEBUG - core.main (15:21:41.480) - MainThread (6780):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:21:41.527) - _UIAHandler.UIAHandler.MTAThread (7016):
UIAutomation: IUIAutomation6
DEBUG - core.main (15:21:41.728) - MainThread (6780):
Initializing IAccessible support
DEBUG - core.main (15:21:41.728) - MainThread (6780):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (15:21:41.743)
- MainThread (6780):
No user gesture map
DEBUG - core.main (15:21:41.743) - MainThread (6780):
Initializing keyboard handler
DEBUG - core.main (15:21:41.743) - MainThread (6780):
initializing mouse handler
DEBUG - core.main (15:21:41.859) - MainThread (6780):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (15:21:41.859) - MainThread
(6780):
Touch only supported on installed copies DEBUG - core.main (15:21:41.859) - MainThread (6780):
Initializing global plugin handler
DEBUG - core.main (15:21:41.875) - MainThread (6780):
Initializing core pump
DEBUG - core.main (15:21:41.875) - MainThread (6780):
Initializing watchdog
DEBUG - core.main (15:21:41.875) - MainThread (6780):
initializing updateCheck
INFO - core.main (15:21:41.875) - MainThread (6780):
NVDA initialized
DEBUG - core.main (15:21:41.875) - MainThread (6780):
entering wx application main loop
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(15:21:41.897) - MainThread (6780):
registering pre_configSave action: <class 'visionEnhancementProviders.NVDAHighlighter.NVDAHighlighterSettings'>
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(15:21:41.913) - MainThread (6780):
loading vision NVDAHighlighter
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(15:21:41.913) - MainThread (6780):
Loaded settings for NVDAHighlighterSettings DEBUG - autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction
(15:21:41.913) - MainThread (6780):
registering pre_configSave action: <class 'visionEnhancementProviders.screenCurtain.ScreenCurtainSettings'>
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(15:21:41.928) - MainThread (6780):
loading vision screenCurtain
DEBUG -
autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings
(15:21:41.928) - MainThread (6780):
Loaded settings for ScreenCurtainSettings IO - speech.speak (15:21:41.982) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Bureau', 'liste'] DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale
(15:21:41.982) - MainThread (6780):
No CLDR data for locale fr_FR
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:42.519) - MainThread (6780):
Begin processing speech
IO - speech.speak (15:21:42.637) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Documents Paulo', '19 sur 64'] DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:43.340) -
Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:43.340) -
Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:43.489) -
Dummy-1 (4592):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:45.519) -
Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:45.519) -
Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:21:45.539) - MainThread (6780):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:45.549) -
Dummy-1 (4592):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (15:21:45.670) - winInputHook
(7252):
Input: kb(desktop):alt+tab
IO - speech.speak (15:21:45.889) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Gestionnaire de périphériques', 'ligne 1', 'colonne 1'] DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:45.919) - MainThread (6780):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:47.635) -
Dummy-2 (5972):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:47.635) -
Dummy-2 (5972):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:21:47.635) - MainThread (6780):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:47.644) -
Dummy-2 (5972):
Queue empty, done processing
IO - speech.speak (15:21:47.644) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Gestionnaire de périphériques'] DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:47.675) - MainThread (6780):
Begin processing speech
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(15:21:47.700) - MainThread (6780):
accRole failed: (-2147024809, 'Paramètre incorrect.', (None, None, None, 0, None)) ERROR - eventHandler.executeEvent (15:21:47.734) - MainThread (6780):
error executing event: gainFocus on
<NVDAObjects.IAccessible.sysTreeView32.BrokenCommctrl5Item object at
0x03B4C2B0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 150, in executeEvent
File "eventHandler.pyc", line 163, in doPreGainFocus
File "api.pyc", line 109, in setFocusObject
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\__init__.pyc", line 536, in _get_container
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\IAccessible\sysTreeView32.pyc", line 261, in _get_parent
AttributeError: 'IAccessible' object has no attribute 'UIAElement'
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:48.835) -
Dummy-2 (5972):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:48.835) -
Dummy-2 (5972):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:48.998) -
Dummy-2 (5972):
Queue empty, done processing
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(15:21:49.417) - MainThread (6780):
accRole failed: (-2147024809, 'Paramètre incorrect.', (None, None, None, 0, None)) ERROR - eventHandler.executeEvent (15:21:49.432) - MainThread (6780):
error executing event: gainFocus on
<NVDAObjects.IAccessible.sysTreeView32.BrokenCommctrl5Item object at
0x03755EF0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 150, in executeEvent
File "eventHandler.pyc", line 163, in doPreGainFocus
File "api.pyc", line 109, in setFocusObject
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\__init__.pyc", line 536, in _get_container
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\IAccessible\sysTreeView32.pyc", line 261, in _get_parent
AttributeError: 'IAccessible' object has no attribute 'UIAElement'
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:21:54.209) - MainThread (6780):
Cancelling
IO - speech.speak (15:21:54.209) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Bureau', 'liste'] DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:54.240) - MainThread (6780):
Begin processing speech
IO - speech.speak (15:21:54.240) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Documents Paulo', '19 sur 64'] DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:54.922) -
Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:54.922) -
Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:55.076) -
Dummy-1 (4592):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:57.102) -
Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:57.102) -
Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:57.252) -
Dummy-1 (4592):
Queue empty, done processing
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:22:04.049) - MainThread (6780):
Cancelling
IO - inputCore.InputManager.executeGesture (15:22:04.265) - winInputHook
(7252):
Input: kb(desktop):NVDA+f1
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(15:22:04.535) - MainThread (6780):

Re: Vocalizer expressive voices

Don H
 

Are you talking about sapi 5 voices? Where do you purchase these voices?

On 12/10/2019 9:07 PM, Shaun Everiss wrote:
To be honest, I'd probably buy for sapi and not nvda because I would never need to update them as such.
On 11/12/2019 1:31 pm, Don H wrote:
Before I put down my $69 to purchase the Code Factory vocalizer voices for NVDA are there any issues that make this a bad purchase?  Using a trail version now for 2019.3 beta.



Re: soundcard confusion problem when re-starting NVDA

Giles Turnbull
 

thanks for the explanation and solution, Tyler :) Much appreciated :)

Giles

NVDA 2019.3Beta1 and devices's manager

bering.p
 

Hi,
Today, I found that I could not read the items of the devices's manager.
I am running W10 1909 french system, NVDA 2019.3Beta1 portable copy.
Do you have the same problem on your PC ?
The NVDA log is below.
Thanks.
Best regards.
Paul.


The log:
INFO - __main__ (15:21:39.178) - MainThread (6780):
Starting NVDA version 2019.3beta1
INFO - core.main (15:21:39.475) - MainThread (6780):
Config dir: F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig
INFO - config.ConfigManager._loadConfig (15:21:39.475) - MainThread (6780):
Loading config: .\userConfig\nvda.ini
INFO - config.ConfigManager._loadConfig (15:21:39.537) - MainThread (6780):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{'schemaVersion': '3', 'development': {}, 'general': {'language': 'Windows', 'saveConfigurationOnExit': 'False', 'askToExit': 'True', 'playStartAndExitSounds': 'True', 'loggingLevel': 'DEBUG', 'showWelcomeDialogAtStartup': 'False'}, 'update': {'autoCheck': 'True', 'startupNotification': 'True', 'allowUsageStats': 'False', 'askedAllowUsageStats': 'True'}, 'upgrade': {}, 'speech': {'synth': 'oneCore', 'outputDevice': 'Mappeur de sons Microsoft', 'oneCore': {'voice': 'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech_OneCore\\Voices\\Tokens\\MSTTS_V110_frFR_HortenseM', 'volume': '90', 'rateBoost': 'True', 'rate': '19', 'pitch': '50'}, 'sapi5': {'voice': 'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\TTS_MS_EN-US_ZIRA_11.0', 'volume': '88', 'capPitchChange': '55'}}, 'braille': {'noBraille': {}}, 'vision': {'NVDAHighlighter': {'highlightFocus': 'False', 'highlightNavigator': 'False', 'highlightBrowseMode': 'False'}, 'screenCurtain': {}}, 'keyboard': {'useCapsLockAsNVDAModifierKey': 'True'}, 'NVDAExtensionGlobalPlugin': {'voiceProfileSwitching': {'configVersion': '2', 'lastSelector': '2', '2': {'activate': 'True', 'voiceProfileName': 'sapi5 Microsoft Zira Desktop - English (United States) ', 'defaultVoiceProfileName': 'sapi5 Microsoft Zira Desktop - English (United States) ', 'synthName': 'sapi5', 'speech': {'outputDevice': 'Mappeur de sons Microsoft', 'synth': 'sapi5', 'autoLanguageSwitching': 'True', 'autoDialectSwitching': 'False', 'trustVoiceLanguage': 'True', 'symbolLevel': '100', 'includeCLDR': 'True', 'beepSpeechModePitch': '10000', 'sapi5': {'voice': 'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\TTS_MS_EN-US_ZIRA_11.0', 'rate': '50', 'pitch': '50', 'volume': '88', 'capPitchChange': '55', 'sayCapForCapitals': 'False', 'beepForCapitals': 'False', 'useSpellingFunctionality': 'True'}, '__many__': {'capPitchChange': '30', 'sayCapForCapitals': 'False', 'beepForCapitals': 'False', 'useSpellingFunctionality': 'True'}}, 'synthDisplayInfos': {'1': ['Voix', 'Microsoft Zira Desktop - English (United States)'], '2': ['Débit', '50'], '3': ['Hauteur', '50'], '4': ['Volume', '88']}}}}}
DEBUG - core.main (15:21:39.709) - MainThread (6780):
setting language to Windows
INFO - core.main (15:21:39.709) - MainThread (6780):
Using Windows version 10.0.18363 workstation
INFO - core.main (15:21:39.709) - MainThread (6780):
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 (15:21:39.709) - MainThread (6780):
Using comtypes version 1.1.7
INFO - core.main (15:21:39.709) - MainThread (6780):
Using configobj version 5.1.0 with validate version 1.0.1
DEBUG - core.main (15:21:39.730) - MainThread (6780):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.739) - MainThread (6780):
Listing add-ons from F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig\addons
DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.739) - MainThread (6780):
Loading add-on from F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig\addons\NVDAExtensionGlobalPlugin
DEBUG - addonHandler.Addon.__init__ (15:21:39.739) - MainThread (6780):
Using manifest translation from F:\documents\Paulo\temp\nvda 2019.3 béta\userConfig\addons\NVDAExtensionGlobalPlugin\locale\fr\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.744) - MainThread (6780):
Found add-on NVDAExtensionGlobalPlugin - 9.0-beta1. Requires API: (2019, 1, 0). Last-tested API: (2019, 3, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (15:21:39.744) - MainThread (6780):
Disabling add-on NVDAExtensionGlobalPlugin
DEBUGWARNING - touchHandler.touchSupported (15:21:40.178) - MainThread (6780):
Touch only supported on installed copies
DEBUG - core.main (15:21:40.359) - MainThread (6780):
Initializing appModule Handler
DEBUG - core.main (15:21:40.359) - MainThread (6780):
Initializing NVDAHelper
DEBUG - core.main (15:21:40.438) - MainThread (6780):
Initializing tones
DEBUG - core.main (15:21:40.468) - MainThread (6780):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.468) - MainThread (6780):
Loading speech dictionary '.\userConfig\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.468) - MainThread (6780):
file '.\userConfig\speechDicts\default.dic' not found.
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.468) - MainThread (6780):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.473) - MainThread (6780):
3 loaded records.
DEBUG - core.main (15:21:40.473) - MainThread (6780):
Initializing speech
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction (15:21:40.483) - MainThread (6780):
registering pre_configSave action: <class 'synthDrivers.oneCore.SynthDriver'>
DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:21:40.738) - MainThread (6780):
Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_frCA_CarolineM, FileNotFoundError(2, 'Le fichier spécifié est introuvable', None, 2, None)
DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:21:40.748) - MainThread (6780):
Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_frCA_ClaudeM, FileNotFoundError(2, 'Le fichier spécifié est introuvable', None, 2, None)
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.779) - MainThread (6780):
Loading speech dictionary '.\userConfig\speechDicts\voiceDicts.v1\oneCore\oneCore-Microsoft Hortense.dic'...
DEBUG - speechDictHandler.SpeechDict.load (15:21:40.779) - MainThread (6780):
file '.\userConfig\speechDicts\voiceDicts.v1\oneCore\oneCore-Microsoft Hortense.dic' not found.
DEBUG - synthDriverHandler.SynthDriver.loadSettings (15:21:40.779) - MainThread (6780):
Loaded settings for SynthDriver oneCore
INFO - synthDriverHandler.setSynth (15:21:40.779) - MainThread (6780):
Loaded synthDriver oneCore
INFO - core.main (15:21:40.779) - MainThread (6780):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0
DEBUG - core.main (15:21:40.783) - MainThread (6780):
Initializing braille input
INFO - brailleInput.initialize (15:21:40.783) - MainThread (6780):
Braille input initialized
DEBUG - core.main (15:21:40.788) - MainThread (6780):
Initializing braille
INFO - braille.initialize (15:21:40.788) - MainThread (6780):
Using liblouis version 3.10.0
INFO - braille.initialize (15:21:40.798) - MainThread (6780):
Using pySerial version 3.4
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction (15:21:40.798) - MainThread (6780):
registering pre_configSave action: <class 'brailleDisplayDrivers.noBraille.BrailleDisplayDriver'>
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings (15:21:40.808) - MainThread (6780):
loading braille noBraille
INFO - braille.BrailleHandler.setDisplayByName (15:21:40.808) - MainThread (6780):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (15:21:40.808) - MainThread (6780):
Initializing vision
DEBUG - core.main (15:21:40.808) - MainThread (6780):
Initializing displayModel
DEBUG - core.main (15:21:40.808) - MainThread (6780):
Initializing GUI
DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552
DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552
DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552
DEBUG - windowUtils._rawWindowProc (15:21:40.858) - MainThread (6780):
CustomWindow rawWindowProc called for unknown window 263552
DEBUG - core.main (15:21:40.908) - MainThread (6780):
initializing Java Access Bridge support
INFO - core.main (15:21:41.474) - MainThread (6780):
Java Access Bridge support initialized
DEBUG - core.main (15:21:41.480) - MainThread (6780):
Initializing legacy winConsole support
DEBUG - core.main (15:21:41.480) - MainThread (6780):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:21:41.527) - _UIAHandler.UIAHandler.MTAThread (7016):
UIAutomation: IUIAutomation6
DEBUG - core.main (15:21:41.728) - MainThread (6780):
Initializing IAccessible support
DEBUG - core.main (15:21:41.728) - MainThread (6780):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (15:21:41.743) - MainThread (6780):
No user gesture map
DEBUG - core.main (15:21:41.743) - MainThread (6780):
Initializing keyboard handler
DEBUG - core.main (15:21:41.743) - MainThread (6780):
initializing mouse handler
DEBUG - core.main (15:21:41.859) - MainThread (6780):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (15:21:41.859) - MainThread (6780):
Touch only supported on installed copies
DEBUG - core.main (15:21:41.859) - MainThread (6780):
Initializing global plugin handler
DEBUG - core.main (15:21:41.875) - MainThread (6780):
Initializing core pump
DEBUG - core.main (15:21:41.875) - MainThread (6780):
Initializing watchdog
DEBUG - core.main (15:21:41.875) - MainThread (6780):
initializing updateCheck
INFO - core.main (15:21:41.875) - MainThread (6780):
NVDA initialized
DEBUG - core.main (15:21:41.875) - MainThread (6780):
entering wx application main loop
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction (15:21:41.897) - MainThread (6780):
registering pre_configSave action: <class 'visionEnhancementProviders.NVDAHighlighter.NVDAHighlighterSettings'>
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings (15:21:41.913) - MainThread (6780):
loading vision NVDAHighlighter
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings (15:21:41.913) - MainThread (6780):
Loaded settings for NVDAHighlighterSettings
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction (15:21:41.913) - MainThread (6780):
registering pre_configSave action: <class 'visionEnhancementProviders.screenCurtain.ScreenCurtainSettings'>
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings (15:21:41.928) - MainThread (6780):
loading vision screenCurtain
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._loadSpecificSettings (15:21:41.928) - MainThread (6780):
Loaded settings for ScreenCurtainSettings
IO - speech.speak (15:21:41.982) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Bureau', 'liste']
DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (15:21:41.982) - MainThread (6780):
No CLDR data for locale fr_FR
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:42.519) - MainThread (6780):
Begin processing speech
IO - speech.speak (15:21:42.637) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Documents Paulo', '19 sur 64']
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:43.340) - Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:43.340) - Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:43.489) - Dummy-1 (4592):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:45.519) - Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:45.519) - Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:21:45.539) - MainThread (6780):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:45.549) - Dummy-1 (4592):
Queue empty, done processing
IO - inputCore.InputManager.executeGesture (15:21:45.670) - winInputHook (7252):
Input: kb(desktop):alt+tab
IO - speech.speak (15:21:45.889) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Gestionnaire de périphériques', 'ligne 1', 'colonne 1']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:45.919) - MainThread (6780):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:47.635) - Dummy-2 (5972):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:47.635) - Dummy-2 (5972):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:21:47.635) - MainThread (6780):
Cancelling
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:47.644) - Dummy-2 (5972):
Queue empty, done processing
IO - speech.speak (15:21:47.644) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Gestionnaire de périphériques']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:47.675) - MainThread (6780):
Begin processing speech
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (15:21:47.700) - MainThread (6780):
accRole failed: (-2147024809, 'Paramètre incorrect.', (None, None, None, 0, None))
ERROR - eventHandler.executeEvent (15:21:47.734) - MainThread (6780):
error executing event: gainFocus on <NVDAObjects.IAccessible.sysTreeView32.BrokenCommctrl5Item object at 0x03B4C2B0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 150, in executeEvent
File "eventHandler.pyc", line 163, in doPreGainFocus
File "api.pyc", line 109, in setFocusObject
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\__init__.pyc", line 536, in _get_container
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\IAccessible\sysTreeView32.pyc", line 261, in _get_parent
AttributeError: 'IAccessible' object has no attribute 'UIAElement'
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:48.835) - Dummy-2 (5972):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:48.835) - Dummy-2 (5972):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:48.998) - Dummy-2 (5972):
Queue empty, done processing
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (15:21:49.417) - MainThread (6780):
accRole failed: (-2147024809, 'Paramètre incorrect.', (None, None, None, 0, None))
ERROR - eventHandler.executeEvent (15:21:49.432) - MainThread (6780):
error executing event: gainFocus on <NVDAObjects.IAccessible.sysTreeView32.BrokenCommctrl5Item object at 0x03755EF0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 150, in executeEvent
File "eventHandler.pyc", line 163, in doPreGainFocus
File "api.pyc", line 109, in setFocusObject
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\__init__.pyc", line 536, in _get_container
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 145, in _getPropertyViaCache
File "NVDAObjects\IAccessible\sysTreeView32.pyc", line 261, in _get_parent
AttributeError: 'IAccessible' object has no attribute 'UIAElement'
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:21:54.209) - MainThread (6780):
Cancelling
IO - speech.speak (15:21:54.209) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Bureau', 'liste']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:54.240) - MainThread (6780):
Begin processing speech
IO - speech.speak (15:21:54.240) - MainThread (6780):
Speaking [LangChangeCommand ('fr_FR'), 'Documents Paulo', '19 sur 64']
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:54.922) - Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:54.922) - Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:55.076) - Dummy-1 (4592):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (15:21:57.102) - Dummy-1 (4592):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:57.102) - Dummy-1 (4592):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (15:21:57.252) - Dummy-1 (4592):
Queue empty, done processing
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (15:22:04.049) - MainThread (6780):
Cancelling
IO - inputCore.InputManager.executeGesture (15:22:04.265) - winInputHook (7252):
Input: kb(desktop):NVDA+f1
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (15:22:04.535) - MainThread (6780):

Re: Letter from a community add-ons reviewer: how you can help make NVDA add-ons compatible with NVDA 2019.3

anthony borg
 

Thank you for the info joseph.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: 11 December 2019 04:42
To: nvda@nvda.groups.io
Subject: [nvda] Letter from a community add-ons reviewer: how you can help make NVDA add-ons compatible with NVDA 2019.3

 

Hi all,

 

Please circulate this letter to the wider community:

 

Dear NVDA users and the wider NVDA community,

 

I’m Joseph Lee, one of the NVDA code contributors and a community add-ons reviewer. On behalf of NVDA core and add-ons developers, I would like to thank you for your continued support for NVDA. And as the developer responsible for leading the much anticipated Python 3 transition research, I would like to personally thank you for continued encouragements, feedback, and guidance in making this transition work as smooth as possible.

 

One of the frequently asked questions for the past few months has been, “are my favorite add-ons compatible with future NVDA releases?” Until a few months ago, the answer was “not many”; today, a vast majority of add-ons are compatible with NVDA 2019.3, or will require this version to work. Since the release of NVDA 2019.3 beta on December 9, 2019, more add-ons are coming onboard the compatibility train, especially speech synthesizers such as Code Factory’s Vocalizer and Eloquence package, Vocalizer Direct and Expressive voices, and others.

 

As many of you may know, part of what makes NVDA great is a variety of community add-ons. Since late 2018, several community add-on authors were testing Python 3 version of NVDA internally to make sure their add-ons were ready in time for NVDA 2019.3. Since August 2019, add-on authors were encouraged to make their add-ons compatible, and a page listing compatible add-ons has been created to track the progress of this work, which can be found as an announcement in community add-ons website (addons.nvda-project.org).

 

As a community project, NVDA relies on community participation to shape its destiny. As part of this, you can make NVDA 2019.3 stable and even better by helping to make add-ons compatible on day 1 of NVDA 2019.3 era. As part of this effort, please take note of the following suggestions:

 

  1. Hold off on feature requests for a while: I know that many of you would like to see a cool thing or two included in add-ons. But as I noted above, NVDA 2019.3 is a huge release, with changes such as Python 3 that will affect many add-ons. So until NVDA 2019.3 stable version is released for everyone, please hold off on suggesting new features for add-ons so add-on authors can focus on making their add-ons compatible and stable.
  2. Provide feedback in a timely manner: although add-on authors will try their best to make sure their add-ons are ready for NVDA 2019.3, they cannot cover all bugs. If you do run into problems with add-ons that are specific to NVDA 2019.3 changes, please send feedback to add-on authors as soon as possible. On the compatible add-ons page, you’ll find not only compatibility information for add-ons, but also contact information such as email addresses of people who made add-ons possible.
  3. Encourage add-on authors: add-on authors are not superheroes – they are humans. Encourage them while giving feedback about their add-ons.

 

As a community, we are in this journey together – NVDA 2019.3 is all about preparing for the future and a necessary stepping stone to make sure you (users) can have equal access to technology. You can make NVDA 2019.3 better and truly revolutionary by participating in making sure add-ons are ready for the new year. My personal new year’s resolution for 2020 is to see 100 percent of community add-ons compatible with NVDA 2019.3 on the day it is released for everyone. I am certain that we as a community can make this dream a reality. Keep up the good work, and in the meantime, please test NVDA 2019.3 beta with add-ons and provide feedback to authors.

 

Thank you.

Sincerely,

Joseph

error in beta1 instalation

Alexandre Alves Toco
 

Hello there!

During the process, the instalation shows a message saying there is na error and restart the installation again.

I already removed the current nvda’s installation. But it didn’t work.

So I have 2 question:

  1. The installation program creates any log? If so, where is it?
  2. Where can I send it?

 

 

Enviado do Email para Windows 10

 

Re: NVDA saying new notification window

hurrikennyandopo ...
 

Hi


it was installed as soon as it was released.


It has not been doing it now.


Gene nz


On 11/12/2019 3:51 pm, Quentin Christensen wrote:
Ah glad to hear it Gene.

Had you recently installed the 2019.3 beta by chance?  Installing a new version of NVDA often works smoothly, but occasionally random glitches like this pop up which are fixed with a reboot.

On Wed, Dec 11, 2019 at 8:10 AM hurrikennyandopo ... <hurrikennyandopo@...> wrote:
It seems to have stopped after a reboot but will keep a eye on it.


Gene nz


On 11/12/2019 9:18 am, hurrikennyandopo ... wrote:
> Hi guys
>
>
> has any one else noticed when you close a window say wheather it is a
> browser been closed or the settings in nvda it says new notification
> window.
>
>
> I had a look under object presentation and un checked notifications
> there but still says it.
>
>
> Is there any where else to look to turn it off or is it a bug?
>
>
> I am using windows 10 version 1903 with nvda 2019.3 beta 1
>
>
> Gene nz
>
>
>
>
>
>
>





--
Quentin Christensen
Training and Support Manager

Re: soundcard confusion problem when re-starting NVDA

Tyler Spivey
 

Alright. So here's what's going on.

This is another one of those NVDA bugs that have been there for years without a fix.

What's going on is that when the synthesizer loads, NVDA gets the ID of the sound card. It uses that ID to speak through until you change it or until it restarts.
However, unplugging the sound card and plugging it back in might change its ID, and NVDA doesn't notice.


So to avoid this, just hit alt control n to restart NVDA and it should use the correct card again.

On 12/10/2019 8:03 PM, Giles Turnbull wrote:
Hi all,

I encountered a strange issue tonight while using a USB sound card. I have experienced it once before but didn't know what had happened, but this time I think I realise what has happened and I'm wondering if it is an NVDA bug or an expected situation. If it is expected, I'm wondering if there is a workaround?

This bit of info isn't connected to the problem but it does help in the explanation. When I listen through wifi headphones via the USB soundcard, I hear most audio through the headphones but system sounds still come from the laptop speakers. I've asked about this on this list before so understand what is going on with that and how I could change it if I was sufficiently bothered.

Anyway, what happened tonight was that I was trying to open a book I'd purchased in Adobe Digital Editions. ADE stopped responding and sometimes when programs stop responding (Firefox does this sometimes), closing NVDA and re-opening it allows NVDA to work with the program again.This did not happen this time and here's where the issue really starts.

I understand why NVDA switched back to using the laptop soundcard and speakers rather than the USB soundcard and headphones, but what was strange was that when I went and unplugged the USB soundcard (hoping to restore USB soundcard and headphone sound by unplugging the USB soundcard and plugging it back in again) when I unplugged the USB device I lost all sound. NVDA could only b e heard through the laptop speakers when the USB soundcard was plugged in but, when it was plugged in, no sound came through the headphones.

I'm curious about why unplugging the USB soundcard stopped all audio through the laptop speakers, whilst plugging it back in (which probably should have restored audio through the headphones) didn't restore headphone sound but did restore laptop speaker sound.

The only solution I could think of to get the different soundcards behaving the way they should, was to restart the laptop and unplug the USB soundcard before Windows rebooted. That is how I logged back in and have now re-connected the USB soundcard and am listening through my wifi headphones again.

My question is whether there is any way, other than restarting the laptop, to restart NVDA without causing problems between the soundcards?

I'm using NVDA 2019.2 and Windows 10 Version 1903 (OS Build 18362.476). My USB soundcard is quite an expensive one, an audioquest Dragonfly Red.

Grateful for any suggestions (other than the obvious one of not re-starting NVDA whilst an external soundcard is being used)

Giles



 

Re: Does anybody use a telnet BBS?

Angelo Sonnesso
 

That sounds pretty cool.
Can you share your ad-in?

73 N2DYN Angelo

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of John Isige
Sent: Wednesday, December 11, 2019 1:15 AM
To: nvda@nvda.groups.io
Subject: [nvda] Does anybody use a telnet BBS?

I ask because I'm on ISCA BBS, the only one I know of that's still going,
though there might be others. I have an addon that makes a client for it read
the text automatically as it comes in and let's you review it. It's nothing
fancy, I literally stole it from NVDA's internal code for PuTTY and changed
the window name, so it treats the client window as a terminal. I've been using
it for quite a while now. I've never bothered uploading it to the community
because I didn't think it would be useful to anybody but me, but since I just
made it work with 2019.3beta1, I figured I'd at least ask in case somebody's
been waiting for just such a thing to exist. If so, it does, and sorry I
didn't mention it sooner.


Alternatively, if you're on one of these and you've found a way to use NVDA
without an addon, I'd love to hear about it. You could run a client on a Unix
variant I guess, but this addon let's you do everything right from Windows.
You get a full editor and all, as opposed to single line editing with telnet.
If there's a way to do that on Windows without an addon, I'm really interested
in trying it out.

Does anybody use a telnet BBS?

John Isige
 

I ask because I'm on ISCA BBS, the only one I know of that's still going, though there might be others. I have an addon that makes a client for it read the text automatically as it comes in and let's you review it. It's nothing fancy, I literally stole it from NVDA's internal code for PuTTY and changed the window name, so it treats the client window as a terminal. I've been using it for quite a while now. I've never bothered uploading it to the community because I didn't think it would be useful to anybody but me, but since I just made it work with 2019.3beta1, I figured I'd at least ask in case somebody's been waiting for just such a thing to exist. If so, it does, and sorry I didn't mention it sooner.


Alternatively, if you're on one of these and you've found a way to use NVDA without an addon, I'd love to hear about it. You could run a client on a Unix variant I guess, but this addon let's you do everything right from Windows. You get a full editor and all, as opposed to single line editing with telnet. If there's a way to do that on Windows without an addon, I'm really interested in trying it out.

Moving Focus and Brows Mode Cursors at the same time in editable Browser Elements?

 

Hello,

I am wondering if there is a way to connect the focus mode to the brows mode in rich text editors or editable elements in the browser?

1.       Open:

https://www.tiny.cloud/docs/demo/basic-example/

2.       Press o to get to the "Application" and hit enter.

3.       Press escape until you are placed in the editing area.

4.       Arrow down several lines

5.       Press NVDA+space to go into brows mode.

6.       Arrow up and down to find out your cursor when editing is different than your cursor when in brows mode.

7.       In brows mode, hit h to go to "A simple table to play with" and hit enter.

8.       Press read current line and it will be on the last line you were on in focus mode.

 

I'm sure someone would find this behavior useful sometime, but it is really making using rich text fields annoying in the browser.

Is there some way to connect these two cursors together?

I have both Caret moves review cursor on, and Focus moves navigator object on.

Thank you,


soundcard confusion problem when re-starting NVDA

Giles Turnbull
 

Hi all,

I encountered a strange issue tonight while using a USB sound card. I have experienced it once before but didn't know what had happened, but this time I think I realise what has happened and I'm wondering if it is an NVDA bug or an expected situation. If it is expected, I'm wondering if there is a workaround?

This bit of info isn't connected to the problem but it does help in the explanation. When I listen through wifi headphones via the USB soundcard, I hear most audio through the headphones but system sounds still come from the laptop speakers. I've asked about this on this list before so understand what is going on with that and how I could change it if I was sufficiently bothered.

Anyway, what happened tonight was that I was trying to open a book I'd purchased in Adobe Digital Editions. ADE stopped responding and sometimes when programs stop responding (Firefox does this sometimes), closing NVDA and re-opening it allows NVDA to work with the program again.This did not happen this time and here's where the issue really starts.

I understand why NVDA switched back to using the laptop soundcard and speakers rather than the USB soundcard and headphones, but what was strange was that when I went and unplugged the USB soundcard (hoping to restore USB soundcard and headphone sound by unplugging the USB soundcard and plugging it back in again) when I unplugged the USB device I lost all sound. NVDA could only b e heard through the laptop speakers when the USB soundcard was plugged in but, when it was plugged in, no sound came through the headphones.

I'm curious about why unplugging the USB soundcard stopped all audio through the laptop speakers, whilst plugging it back in (which probably should have restored audio through the headphones) didn't restore headphone sound but did restore laptop speaker sound.

The only solution I could think of to get the different soundcards behaving the way they should, was to restart the laptop and unplug the USB soundcard before Windows rebooted. That is how I logged back in and have now re-connected the USB soundcard and am listening through my wifi headphones again.

My question is whether there is any way, other than restarting the laptop, to restart NVDA without causing problems between the soundcards?

I'm using NVDA 2019.2 and Windows 10 Version 1903 (OS Build 18362.476). My USB soundcard is quite an expensive one, an audioquest Dragonfly Red.

Grateful for any suggestions (other than the obvious one of not re-starting NVDA whilst an external soundcard is being used)

Giles



 

Letter from a community add-ons reviewer: how you can help make NVDA add-ons compatible with NVDA 2019.3

 

Hi all,

 

Please circulate this letter to the wider community:

 

Dear NVDA users and the wider NVDA community,

 

I’m Joseph Lee, one of the NVDA code contributors and a community add-ons reviewer. On behalf of NVDA core and add-ons developers, I would like to thank you for your continued support for NVDA. And as the developer responsible for leading the much anticipated Python 3 transition research, I would like to personally thank you for continued encouragements, feedback, and guidance in making this transition work as smooth as possible.

 

One of the frequently asked questions for the past few months has been, “are my favorite add-ons compatible with future NVDA releases?” Until a few months ago, the answer was “not many”; today, a vast majority of add-ons are compatible with NVDA 2019.3, or will require this version to work. Since the release of NVDA 2019.3 beta on December 9, 2019, more add-ons are coming onboard the compatibility train, especially speech synthesizers such as Code Factory’s Vocalizer and Eloquence package, Vocalizer Direct and Expressive voices, and others.

 

As many of you may know, part of what makes NVDA great is a variety of community add-ons. Since late 2018, several community add-on authors were testing Python 3 version of NVDA internally to make sure their add-ons were ready in time for NVDA 2019.3. Since August 2019, add-on authors were encouraged to make their add-ons compatible, and a page listing compatible add-ons has been created to track the progress of this work, which can be found as an announcement in community add-ons website (addons.nvda-project.org).

 

As a community project, NVDA relies on community participation to shape its destiny. As part of this, you can make NVDA 2019.3 stable and even better by helping to make add-ons compatible on day 1 of NVDA 2019.3 era. As part of this effort, please take note of the following suggestions:

 

  1. Hold off on feature requests for a while: I know that many of you would like to see a cool thing or two included in add-ons. But as I noted above, NVDA 2019.3 is a huge release, with changes such as Python 3 that will affect many add-ons. So until NVDA 2019.3 stable version is released for everyone, please hold off on suggesting new features for add-ons so add-on authors can focus on making their add-ons compatible and stable.
  2. Provide feedback in a timely manner: although add-on authors will try their best to make sure their add-ons are ready for NVDA 2019.3, they cannot cover all bugs. If you do run into problems with add-ons that are specific to NVDA 2019.3 changes, please send feedback to add-on authors as soon as possible. On the compatible add-ons page, you’ll find not only compatibility information for add-ons, but also contact information such as email addresses of people who made add-ons possible.
  3. Encourage add-on authors: add-on authors are not superheroes – they are humans. Encourage them while giving feedback about their add-ons.

 

As a community, we are in this journey together – NVDA 2019.3 is all about preparing for the future and a necessary stepping stone to make sure you (users) can have equal access to technology. You can make NVDA 2019.3 better and truly revolutionary by participating in making sure add-ons are ready for the new year. My personal new year’s resolution for 2020 is to see 100 percent of community add-ons compatible with NVDA 2019.3 on the day it is released for everyone. I am certain that we as a community can make this dream a reality. Keep up the good work, and in the meantime, please test NVDA 2019.3 beta with add-ons and provide feedback to authors.

 

Thank you.

Sincerely,

Joseph

Re: Vocalizer expressive voices

 

To be honest, I'd probably buy for sapi and not nvda because I would never need to update them as such.

On 11/12/2019 1:31 pm, Don H wrote:
Before I put down my $69 to purchase the Code Factory vocalizer voices for NVDA are there any issues that make this a bad purchase?  Using a trail version now for 2019.3 beta.


Re: Vocalizer expressive voices

Don H
 

Ok here is what I have found so far with the Vocalizer voices and the NVDA 2019.3 beta.
I am finding the voices very responsive and I think much better than the one core voices.
Having said that for some reason and I don't know if this was a NVDA beta issure or a Vocalizer issue. At a point after the voices working very well I had a need to reboot my system. I have american english voices installed and nothing else. For some reason NVDA started speaking in some other language. When I opened the NVDA UI the dialog box was also displaying something other than english. Had to totally remove NVDA and any left over NVDA folders to get back to speaking and showing english.

Re: NVDA saying new notification window

 

Yeah, sometimes a notification comes up and the window just stays up till you reboot.

My theory is its another sync issue it doesn't happen often but if you are in the wrong place it can happen a lot.

Just reboot and it will go away for a while.

On 11/12/2019 9:18 am, hurrikennyandopo ... wrote:
Hi guys


has any one else noticed when you close a window say wheather it is a browser been closed or the settings in nvda it says new notification window.


I had a look under object presentation and un checked notifications there but still says it.


Is there any where else to look to turn it off or is it a bug?


I am using windows 10 version 1903 with nvda 2019.3 beta 1


Gene nz





Re: NVDA saying new notification window

Quentin Christensen
 

Ah glad to hear it Gene.

Had you recently installed the 2019.3 beta by chance?  Installing a new version of NVDA often works smoothly, but occasionally random glitches like this pop up which are fixed with a reboot.

On Wed, Dec 11, 2019 at 8:10 AM hurrikennyandopo ... <hurrikennyandopo@...> wrote:
It seems to have stopped after a reboot but will keep a eye on it.


Gene nz


On 11/12/2019 9:18 am, hurrikennyandopo ... wrote:
> Hi guys
>
>
> has any one else noticed when you close a window say wheather it is a
> browser been closed or the settings in nvda it says new notification
> window.
>
>
> I had a look under object presentation and un checked notifications
> there but still says it.
>
>
> Is there any where else to look to turn it off or is it a bug?
>
>
> I am using windows 10 version 1903 with nvda 2019.3 beta 1
>
>
> Gene nz
>
>
>
>
>
>
>





--
Quentin Christensen
Training and Support Manager