How this works depends on the hardware and the drivers I seem to remember. Dell machines use several different ways in different models, unfortunately. The most annoying one for me is when sightees use the machines and use all manner of ways to turn off the sound, including the screenreader which means first going through all the ways they may have used from simply turning off the speakers and pulling out the  jack to tray icons turning the volume right down or worse messing with lots of settings till nothing works correctly!
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Brian Vogel" <britechguy@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, May 25, 2018 8:40 PM
Subject: Re: [nvda] sounds ?


Danni,

If it turns out that your Windows sound output has been muted, be certain to ask your computer guy if there is a key or key sequence on your keyboard you can hit to unmute it (or to try to unmute it).

On my HP laptop, where I've turned off the "Quick Function Keys" feature so that I have access to the F keys "as God intended," the F6 key is the mute/unmute toggle. F7 is decrease volume and F8 is increase volume. All of these only serve those functions if I'm holding down the Fn key plus the previously noted key together. What's nice is even if the sound is muted, if you attempt to either increase or decrease volume it will unmute the sound as part of that.

--

*Brian* *-* Windows 10 Home, 64-Bit, Version 1803, Build 17134

After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

~ Paul Noeldner, May 16, 2007

Hi Marcia,
Ah, something I have experienced before. This dialog usually means that NVDA
cannot work well with certain applications or might not behave correctly
under some circumstances. Usually restarting your computer fixes this
problem.
Technical: somehow, NVDA Helper is unable to hook into deeper event
processing routines. I think numerous issues were raised on GitHub regarding
this problem.
Cheers,
Joseph


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Marcia Yale
Sent: Friday, May 25, 2018 6:57 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A recurring error with the latest master snapshot

Okay, here's the log with the control set to debug. I still have no clue
what I'm reading so I hope someone out there can figure out what is
happening.


INFO - __main__ (09:54:32.895):
Starting NVDA
INFO - core.main (09:54:33.145):
Config dir: C:\Users\Marcia\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (09:54:33.145):
Loading config: C:\Users\Marcia\AppData\Roaming\nvda\nvda.ini
INFO - config.ConfigManager._loadConfig (09:54:33.161):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{u'schemaVersion': u'2', u'upgrade': {}, u'update': {u'autoCheck': u'True',
u'startupNotification': u'True'}, u'general': {u'language': u'en',
u'saveConfigurationOnExit': u'True', u'askToExit': u'False',
u'playStartAndExitSounds': u'True', u'loggingLevel': u'DEBUG',
u'showWelcomeDialogAtStartup': u'False'}, u'speech': {u'synth': u'espeak',
u'autoLanguageSwitching': u'False', u'outputDevice': u'Microsoft Sound
Mapper', u'symbolLevel': u'300', u'espeak': {u'voice': u'en-gb-x-rp',
u'variant': u'max', u'rate': u'80', u'pitch': u'43', u'inflection': u'75',
u'volume': u'100', u'beepForCapitals': u'True', u'sayCapForCapitals':
u'False'}}, u'braille': {u'display': u'noBraille', u'translationTable':
u'en-us-g2.ctb', u'inputTable': u'en-us-g2.ctb', u'expandAtCursor':
u'False', u'showCursor': u'False', u'messageTimeout': u'2', u'noBraille':
{u'port': u''}, u'freedomScientific': {u'port': u'auto'}}, u'keyboard':
{u'useCapsLockAsNVDAModifierKey': u'True', u'speakTypedCharacters':
u'False'}, u'documentFormatting': {u'reportRevisions': u'False',
u'reportSpellingErrors': u'False', u'reportTableHeaders': u'False',
u'reportTableCellCoords': u'True', u'reportLists': u'False',
u'reportBlockQuotes': u'False', u'reportFrames': u'False',
u'autoLanguageSwitching': u'False', u'reportClickable': u'False'}} DEBUG -
core.main (09:54:33.239):
setting language to en
INFO - core.main (09:54:33.239):
NVDA version master-15137,1cd171de
INFO - core.main (09:54:33.239):
Using Windows version 6.1.7601 service pack 1 workstation INFO - core.main
(09:54:33.239):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC
v.1500 32 bit (Intel)]
INFO - core.main (09:54:33.239):
Using comtypes version 1.1.3
DEBUG - core.main (09:54:33.239):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (09:54:33.255):
Listing add-ons from C:\Users\Marcia\AppData\Roaming\nvda\addons
DEBUGWARNING - touchHandler.touchSupported (09:54:33.282):
Touch only supported on Windows 8 and higher DEBUG - core.main
(09:54:33.371):
Initializing appModule Handler
DEBUG - core.main (09:54:33.371):
Initializing NVDAHelper
ERROR - RPC process 60284 (nvda.exe) (09:54:33.381):
Thread 59768, build\x86\remote\injection.cpp, inprocMgrThreadFunc, 168:
SetWinEventHook failed

DEBUG - core.main (09:54:33.421):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
Loading speech dictionary
'C:\Users\Marcia\AppData\Roaming\nvda\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
1 loaded records.
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
3 loaded records.
DEBUG - core.main (09:54:33.421):
Initializing speech
INFO - synthDrivers.espeak.SynthDriver.__init__ (09:54:33.441):
Using eSpeak NG version 1.49.1 dev
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.482):
Loading speech dictionary
'C:\Users\Marcia\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\espeak\espea
k-English (Received Pronunciation).dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.482):
file
'C:\Users\Marcia\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\espeak\espea
k-English (Received Pronunciation).dic' not found.
INFO - synthDriverHandler.setSynth (09:54:33.482):
Loaded synthDriver espeak
INFO - core.main (09:54:33.482):
Using wx version 3.0.2.0 msw (classic)
DEBUG - core.main (09:54:33.482):
Initializing braille input
INFO - brailleInput.initialize (09:54:33.482):
Braille input initialized
DEBUG - core.main (09:54:33.482):
Initializing braille
INFO - braille.initialize (09:54:33.482):
Using liblouis version 3.5.0
INFO - braille.BrailleHandler.setDisplayByName (09:54:33.492):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (09:54:33.492):
Initializing displayModel
DEBUG - core.main (09:54:33.492):
Initializing GUI
DEBUG - core.main (09:54:33.502):
initializing Java Access Bridge support
DEBUG - core.main (09:54:33.552):
Initializing winConsole support
DEBUG - core.main (09:54:33.552):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (09:54:33.552):
UIAutomation: IUIAutomation
DEBUG - core.main (09:54:34.151):
Initializing IAccessible support
DEBUG - core.main (09:54:34.151):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (09:54:34.151):
No locale gesture map for language en
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (09:54:34.151):
No user gesture map
DEBUG - core.main (09:54:34.151):
Initializing keyboard handler
DEBUG - core.main (09:54:34.151):
initializing mouse handler
DEBUG - core.main (09:54:34.161):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (09:54:34.161):
Touch only supported on Windows 8 and higher DEBUG - core.main
(09:54:34.161):
Initializing global plugin handler
DEBUG - core.main (09:54:34.161):
Initializing core pump
DEBUG - core.main (09:54:34.161):
Initializing watchdog
DEBUG - core.main (09:54:34.161):
initializing updateCheck
INFO - core.main (09:54:34.161):
NVDA initialized
DEBUG - core.main (09:54:34.161):
entering wx application main loop
IO - speech.speak (09:54:34.181):
Speaking [u'nvdaHelperRemote (outprocMgrThreadFunc) dialog Error
registering focus winEvent hook'] IO - speech.speak (09:54:34.191):
Speaking [u'OK button']
IO - inputCore.InputManager.executeGesture (09:54:40.007):
Input: kb(desktop):space
IO - speech.speak (09:54:40.028):
Speaking [u'pressed']
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (09:54:40.197):
oleacc.AccessibleObjectFromEvent with window 16452220, objectID -4 and
childID 0: [Error -2147467259] Unspecified error DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(09:54:40.237):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None,
None, 0, None)) IO - speech.speak (09:54:40.257):
Speaking [u'Taskbar']
IO - inputCore.InputManager.executeGesture (09:54:42.266):
Input: kb(desktop):NVDA+n
IO - speech.speak (09:54:42.336):
Speaking [u'NVDA menu']
IO - inputCore.InputManager.executeGesture (09:54:43.677):
Input: kb(desktop):downArrow
IO - speech.speak (09:54:43.697):
Speaking [u'Preferences subMenu p']
IO - inputCore.InputManager.executeGesture (09:54:45.049):
Input: kb(desktop):downArrow
IO - speech.speak (09:54:45.078):
Speaking [u'Tools subMenu t']
IO - inputCore.InputManager.executeGesture (09:54:45.532):
Input: kb(desktop):rightArrow
IO - speech.speak (09:54:45.582):
Speaking [u'View log v']
IO - inputCore.InputManager.executeGesture (09:54:46.229):
Input: kb(desktop):enter
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian's
Mail list account via Groups.Io
Sent: Friday, May 25, 2018 3:16 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A recurring error with the latest master snapshot

Firstly have a look at it with the logging level set to debug, as this may
well show up more detail. I certainly get no such error here on the latest
master installed copy The windows internal number is correct though, as
this is just an internal designation.

If you are bored easily stop reading now as I'm pasting my debug log with no
errors and the add ons listed for comparison.


INFO - __main__ (08:06:41.973):
Starting NVDA
INFO - core.main (08:06:42.223):
Config dir: C:\Users\Brian\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (08:06:42.223):
Loading config: C:\Users\Brian\AppData\Roaming\nvda\nvda.ini
INFO - config.ConfigManager._loadConfig (08:06:42.255):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{u'schemaVersion': u'2', u'upgrade': {}, u'update': {u'autoCheck': u'True',
u'startupNotification': u'True'}, u'general':
{u'showWelcomeDialogAtStartup': u'False', u'language': u'Windows',
u'saveConfigurationOnExit': u'True', u'askToExit': u'True',
u'playStartAndExitSounds': u'True', u'loggingLevel': u'DEBUG'}, u'speech':
{u'synth': u'speechPlayerInEspeak', u'outputDevice': u'Speakers (3-
BEHRINGER USB WDM ', u'symbolLevel': u'100', u'espeak': {u'voice': u'en',
u'variant': u'quincy', u'rate': u'40', u'pitch': u'40', u'inflection':
u'75', u'volume': u'86'}, u'sapi5': {u'voice':
u'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\ScanSoftD
aniel_Full_22kHz',
u'volume': u'100', u'rate': u'90'}, u'mssp': {u'voice':
u'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech
Server\\v11.0\\Voices\\Tokens\\TTS_MS_en-GB_Hazel_11.0', u'volume': u'90',
u'rate': u'60'}, u'silence': {}, u'sapi4': {u'voice':
u'{BF5EAD40-9F65-11CF-8FC8-0020AF14F271}', u'rate': u'38', u'pitch': u'20',
u'volume': u'41'}, u'speechPlayerInEspeak': {u'voice': u'en', u'variant':
u'quincy', u'rate': u'40', u'pitch': u'40', u'inflection': u'75', u'volume':

u'99'}, u'pico': {u'voice': u'en-gb', u'volume': u'80', u'rate': u'55',
u'pitch': u'40'}, u'dectalk': {u'voice': u'Frank', u'rate': u'38', u'pitch':

u'19', u'inflection': u'40'}}, u'braille': {u'noBraille': {u'port': u''}},
u'presentation': {u'reportTooltips': u'True',
u'guessObjectPositionInformationWhenUnavailable': u'True',
u'reportObjectDescriptions': u'True', u'progressBarUpdates':
{u'progressBarOutputMode': u'both'}}, u'virtualBuffers':
{u'autoPassThroughOnCaretMove': u'True'}, u'documentFormatting':
{u'reportRevisions': u'False', u'reportSpellingErrors': u'False',
u'reportLineIndentation': u'True', u'reportBlockQuotes': u'False',
u'autoLanguageSwitching': u'True', u'detectFormatAfterCursor': u'False',
u'reportFontName': u'False', u'reportFontSize': u'False',
u'reportAlignment': u'True', u'reportStyle': u'False',
u'reportFontAttributes': u'False', u'reportEmphasis': u'False',
u'reportLineIndentationWithTones': u'False'}, u'keyboard':
{u'speakTypedCharacters': u'True', u'useCapsLockAsNVDAModifierKey':
u'False', u'keyboardLayout': u'desktop'}} DEBUG - core.main (08:06:42.270):
setting language to Windows
INFO - core.main (08:06:42.270):
NVDA version master-15137,1cd171de
INFO - core.main (08:06:42.270):
Using Windows version 6.1.7601 service pack 1 workstation INFO - core.main
(08:06:42.270):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC

v.1500 32 bit (Intel)]
INFO - core.main (08:06:42.270):
Using comtypes version 1.1.3
DEBUG - core.main (08:06:42.302):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.303):
Listing add-ons from C:\Users\Brian\AppData\Roaming\nvda\addons
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.303):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\DECTalk
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.305):
Found add-on DECTalk
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.305):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\dropbox
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.306):
Found add-on dropbox
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.306):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\extendedWinamp
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.308):
Found add-on extendedWinamp
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.308):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\fakeClipboardAnouncement
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.309):
Found add-on fakeClipboardAnouncement
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.309):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\focusHighlight
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.312):
Found add-on focusHighlight
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.312):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\goldenCursor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.315):
Found add-on goldenCursor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.315):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\goldwave
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.316):
Found add-on goldwave
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.316):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\mp3DirectCut
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.318):
Found add-on mp3DirectCut
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.318):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\OpenLinkWith
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Found add-on OpenLinkWith
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\pico
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Found add-on pico
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\readFeeds
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.321):
Found add-on readFeeds
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.321):
Disabling add-on readFeeds
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.321):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\resourceMonitor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.322):
Found add-on resourceMonitor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.322):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\SentenceNav
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.325):
Found add-on SentenceNav
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.325):
Disabling add-on SentenceNav
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.325):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\speechPlayerInEspeak
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.326):
Found add-on speechPlayerInEspeak
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.326):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\virtualRevision
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.329):
Found add-on virtualRevision
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.329):
Disabling add-on virtualRevision
DEBUGWARNING - touchHandler.touchSupported (08:06:42.565):
Touch only supported on Windows 8 and higher DEBUG - core.main
(08:06:42.651):
Initializing appModule Handler
DEBUG - addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon dropbox added to appModules package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon extendedWinamp added to appModules package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon goldwave added to appModules package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon mp3DirectCut added to appModules package path DEBUG - core.main
(08:06:42.653):
Initializing NVDAHelper
DEBUG - core.main (08:06:42.710):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.711):
Loading speech dictionary
'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.711):
file 'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\default.dic' not
found.
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.711):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.717):
3 loaded records.
DEBUG - core.main (08:06:42.717):
Initializing speech
DEBUG - addonHandler.Addon.addToPackagePath (08:06:42.717):
Addon DECTalk added to synthDrivers package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.717):
Addon pico added to synthDrivers package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.717):
Addon speechPlayerInEspeak added to synthDrivers package path INFO -
external:synthDrivers.speechPlayerInEspeak.SynthDriver.__init__
(08:06:42.782):
Using eSpeak NG version 1.49.1 dev
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.976):
Loading speech dictionary
'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\speechPlayerI
nEspeak\speechPlayerInEspeak-english.dic'...
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.977):
6 loaded records.
INFO - synthDriverHandler.setSynth (08:06:42.979):
Loaded synthDriver speechPlayerInEspeak
INFO - core.main (08:06:42.979):
Using wx version 3.0.2.0 msw (classic)
DEBUG - core.main (08:06:42.980):
Initializing braille input
INFO - brailleInput.initialize (08:06:42.980):
Braille input initialized
DEBUG - core.main (08:06:42.980):
Initializing braille
INFO - braille.initialize (08:06:42.980):
Using liblouis version 3.5.0
INFO - braille.BrailleHandler.setDisplayByName (08:06:42.982):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (08:06:42.982):
Initializing displayModel
DEBUG - core.main (08:06:42.982):
Initializing GUI
DEBUG - core.main (08:06:42.994):
initializing Java Access Bridge support
WARNING - core.main (08:06:42.994):
Java Access Bridge not available
DEBUG - core.main (08:06:42.996):
Initializing winConsole support
DEBUG - core.main (08:06:42.996):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (08:06:42.997):
UIAutomation: IUIAutomation
DEBUG - core.main (08:06:43.260):
Initializing IAccessible support
DEBUG - core.main (08:06:43.262):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (08:06:43.262):
No locale gesture map for language en
DEBUG - core.main (08:06:43.263):
Initializing keyboard handler
DEBUG - core.main (08:06:43.265):
initializing mouse handler
DEBUG - core.main (08:06:43.282):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (08:06:43.282):
Touch only supported on Windows 8 and higher DEBUG - core.main
(08:06:43.282):
Initializing global plugin handler
DEBUG - addonHandler.Addon.addToPackagePath (08:06:43.282):
Addon dropbox added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.282):
Addon fakeClipboardAnouncement added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.282):
Addon focusHighlight added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon goldenCursor added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon mp3DirectCut added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon OpenLinkWith added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon resourceMonitor added to globalPlugins package path DEBUG - core.main
(08:06:43.494):
Initializing core pump
DEBUG - core.main (08:06:43.494):
Initializing watchdog
DEBUG - core.main (08:06:43.496):
initializing updateCheck
INFO - core.main (08:06:43.497):
NVDA initialized
DEBUG - core.main (08:06:43.499):
entering wx application main loop
DEBUG - external:globalPlugins.focusHighlight.startThread (08:06:43.499):
focusHighlight started
IO - speech.speak (08:06:43.523):
Speaking [LangChangeCommand ('en_GB'), u'Taskbar'] IO -
inputCore.InputManager.executeGesture (08:06:50.809):
Input: kb(desktop):control+alt+r
IO - speech.speak (08:06:50.900):
Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log terminal'] IO
- speech.speak (08:06:50.903):
Speaking [LangChangeCommand ('en_GB'), u'80 space', u'blank'] INFO -
core.main (08:06:50.970):
Exiting


bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Marcia Yale" <dragoncatmc@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, May 25, 2018 3:13 AM
Subject: [nvda] A recurring error with the latest master snapshot

I will paste my log below, but the issue here is that every time NVDA is
started it gives an error and an "ok" dialog comes up with a corresponding
sound. Not sure what the error means. It's strange that it shows me using
Windows 6.1--I'm using 7. Didn't know there was even such a thing as
Windows
6!


Starting NVDA
INFO - core.main (22:08:35.072):
Config dir: C:\Users\Marcia\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (22:08:35.072):
Loading config: C:\Users\Marcia\AppData\Roaming\nvda\nvda.ini
INFO - core.main (22:08:35.181):
NVDA version master-15137,1cd171de
INFO - core.main (22:08:35.181):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (22:08:35.181):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17)
[MSC
v.1500 32 bit (Intel)]
INFO - core.main (22:08:35.181):
Using comtypes version 1.1.3
ERROR - RPC process 57604 (nvda.exe) (22:08:35.329):
Thread 48112, build\x86\remote\injection.cpp, inprocMgrThreadFunc, 168:
SetWinEventHook failed

INFO - synthDrivers.espeak.SynthDriver.__init__ (22:08:35.380):
Using eSpeak NG version 1.49.1 dev
INFO - synthDriverHandler.setSynth (22:08:35.420):
Loaded synthDriver espeak
INFO - core.main (22:08:35.420):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (22:08:35.420):
Braille input initialized
INFO - braille.initialize (22:08:35.420):
Using liblouis version 3.5.0
INFO - braille.BrailleHandler.setDisplayByName (22:08:35.430):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (22:08:35.490):
UIAutomation: IUIAutomation
INFO - core.main (22:08:36.089):
NVDA initialized
Marcia Yale
It is not our differences that divide us. It is our inability to
recognize,
accept, and celebrate those differences.
Audre Lorde

On May 24, 2018, at 3:36 PM, Laurie Mehta via Groups.Io <lauriemehta=yahoo.com@groups.io> wrote:

Hi all,

I enjoy reading news via Google's news page news dot google dot com.
But for a while now that page had been changed to appear less accessibly in Firefox. I shared my feedback with Google and they promised an update was coming. Well it apparently has!

I have Windows 7 on this laptop and Firefox 59.02, and am using NVDA 18.1.

The page that loaded when I typed news.google.com is laid out very nicely with headings marking all section titles and links placed on each story and news source listed under each heading. The placement of a link saying more (with section title following) might be better placed under the list of news stories (in my opinion) but it is also fine as it is.
I wanted to share with you NVDA users in case you, like me, had switched to Chrome for viewing the news page back when the less accessible news page launched. It's nice to know that we can use either Firefox or Chrome for Google's news page, and that Google fixed the problem.

Here is the url copied from my viewing, since others' preferences might display something else:

https://news.google.com/?hl=en-US&;gl=US&ceid=US:en

-LM

If discussion of the illegal add on continues, I'll lock the topic.  I don't want to do that, but this discussion isn't allowed on list.

 

I realize that some people may respond to messages about the Dectalk add on before they see my first message and if I block the topic, it won't be for punative reasons.  it will be to stop further improper discussion in the thread.

 

Gene

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

From: Casey

Sent: Thursday, May 24, 2018 10:32 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Best Synthesizer

Hi can you please pass along where to get this dektalk add on.

I found I page using google but it has two different versions on it so I would like to get the correct one.

So if you could provide that it would be A big help.

On 5/24/2018 8:12 AM, erik burggraaf wrote:

Synthesizers are all very preferencial.  I really like the espeak american varients though that makes me a bit of an oddball.  If you only want english language support the dektalk access add-on is outrageously good.  Much better than the phonix distrobution and in my experience, it's extremely fast and stable.  Pronounciation is good.  Inflection is fine especially if you used dektalk a lot and liked it.  If not, inflection does some funny things that may take getting used to.

Anyhow, google it up and see if you like it.  I think it's on a third party add-on site.

Best,

Erik

On May 24, 2018 8:24:03 AM "Dr. J. michael jones" <j.michaeljones@...> wrote:

Thank you very much of course are use eloquence with jaws but I’m trying to put together an affordable machine for people in Africa NVDA the only way to go and I’m just trying to create a better speech output then what comes with a regular Windows platform.  I observe what you were saying about sluggishness also speed pitch and tone are affected as well again thanks

On May 24, 2018, at 3:11 PM, Gene <gsasner@...> wrote:

There is wide disagreement of what the best is.  it's a matter of preference and taste.  it's like asking what is the best frozen pizza.  Do you like older synthesizers such as Eloquence or do you like newer ones, with more human sounding voices but slower responsiveness and, in my opinion, significantly degraded speech accuracy in most of them?  I don't recall the names of any of the newer ones because I dislike most of them and don't use them.  There are a lot of synthesizers you can try or get information about on the NVDA page devoted to this topic:

https://github.com/nvaccess/nvda/wiki/ExtraVoices

Also, on this page, the Eloquence add on that offers other voices as well is discussed.  There is a SAPI five Eloquence available for sale which is far superior, if you are interested in Eloquence.  Others can tell you more about it if you are interested.  And a lot of voices available for purchase have demos. 

 

I'll add that some people use a responsive voice for work, such as word processing and other tasks, but use one of the newer more natural voices for listening, such as when reading a book. 

Gene

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

From: Dr. J. michael jones

Sent: Thursday, May 24, 2018 6:59 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Best Synthesizer

Thanks I’m confused.   My question was what is the best? And I believe there is always a better maybe someone else has an opinion
> On May 24, 2018, at 2:54 PM, Antony Stone <antony.stone@...> wrote:
>
> SAPI is not a speech engine.  It's a definition of a protocol enabling speech
> applications (synthesis or recognition) to interface to other applications
> (such as a browser).
>
> Some synthesisers can only communicate with other applications via SAPI, some
> can do SAPI plus other protocols, some don't do SAPI at all.
>
> As Gene said, whether a synthesiser communicates using SAPI says nothing at
> all about the quality of its voices.
>
> Also, to add another answer to the original question "what is the best
> sounding synthesizer that NVDA supports?", I would say it's the one you like
> best and get on with best.  That may not be the same as what someone else
> likes.  These things are a very personal choice.
>
>
> Antony.
>
>> On Thursday 24 May 2018 at 13:47:29, Jaffar Sidek wrote:
>>
>> Also, Sapi is a speech engine native to windows.  The beauty and
>> flexibility of NVDA is that it allows for installation of Non-windows
>> synthesizer voices.  Cheers!
>>
>>> On 5/24/2018 7:26 PM, Gene wrote:
>>> It should be pointed out that SAPI is a way that voices communicate
>>> with the computer.  it has nothing to do with the kind of voice in
>>> terms of its speech or general quality.  sometimes, a synthesizer may
>>> have a SAPI version and a version that isn't SAPI.  There is no reason
>>> to use or not to use a voice because it is SAPI.
>>> Gene
>>>
>>> *From:* Chris via Groups.Io <mailto:chrismedley@...>
>>> *Sent:* Thursday, May 24, 2018 6:02 AM
>>> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
>>> *Subject:* Re: [nvda] Best Synthesizer
>>>
>>> There is nothing better than sapi voices
>>>
>>> Don’t waste your time or money on anything else. Have a nice day now 😃
>
> --
> The first fifty percent of an engineering project takes ninety percent of the
> time, and the remaining fifty percent takes another ninety percent of the time.
>
>                                                   Please reply to the list;
>                                                         please *don't* CC me.
>
>
>

-- 

Casey

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

From: Gene

To: nvda@nvda.groups.io

Sent: Friday, May 25, 2018 1:01 PM

Subject: Re: [nvda] sounds ?

Do other sounds work?  I think the sound you are describing is one Windows sound, which isn't working.  This sounds to me like the kind of problem that should be solved by running a restore point.  If you don't have one, I'm not sure how you might solve the problem.  In future, please describe the problem in detail as you did in this message.  Based on your current description, most of my previous message appears not to apply.  This isn't that Windows sounds aren't working in general.  One Windows sound may not be and I addressed that in this message.

 

Gene

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

From: Danni

Sent: Friday, May 25, 2018 2:25 PM

To: nvda@nvda.groups.io

Subject: Re: [nvda] sounds ?

NVDA is speaking fine now yesterday it kept double talking so shut it down for a couple hours since a reboot did no good but sounds lost are the ping it makes when am at the top or bottom of a document as well as the sound it makes if  try to do something it doesn't want me to do!

 

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

From: Gene New Zealand

To: nvda@nvda.groups.io

Sent: Friday, May 25, 2018 12:23 PM

Subject: Re: [nvda] sounds ?

Hi

Is there any sounds at all on the computer? or are you getting Window sounds but not having nvda speaking?

Gene nz

On 5/26/2018 6:00 AM, Danni wrote:

 

I had to reboot several times yesterday because NVDA was not reading documents and realized this morning that I lost my sounds where do I find them to turn them back  on?

 

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

From: Brian Vogel

To: nvda@nvda.groups.io

Sent: Friday, May 25, 2018 12:40 PM

Subject: Re: [nvda] sounds ?

Danni,

         If it turns out that your Windows sound output has been muted, be certain to ask your computer guy if there is a key or key sequence on your keyboard you can hit to unmute it (or to try to unmute it).

         On my HP laptop, where I've turned off the "Quick Function Keys" feature so that I have access to the F keys "as God intended," the F6 key is the mute/unmute toggle.  F7 is decrease volume and F8 is increase volume.  All of these only serve those functions if I'm holding down the Fn key plus the previously noted key together.  What's nice is even if the sound is muted, if you attempt to either increase or decrease volume it will unmute the sound as part of that.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 

I am trying to get clear about what's being asked here.

If it's how to get the path to a file you can do a Cortana/Windows search for the file, then when it shows up in the results and you have focus on it hit the menu/applications key or SHIFT+F10 and select "Open File location" from the pop up menu.  You'll open file explorer for the folder in which that file is located, with focus on that file, and can get the full path, including the file name, using the Copy Path button in the Home tab [or just hit ALT+H,CP].  You can then paste this where you need it.  One word of warning, though, it encloses the entire path in quotation marks, an example of which is:

"C:\Users\Public\Documents\BriTechGuy\Toolbox\Carry_With_Programs\Search_Everything\Everything-1.4.1.877.x64-Setup.exe"

You may need to remove those.

If you're trying to find task scheduler using Quentin's windows search method is the fastest way directly to it.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

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

From: Gene New Zealand

To: nvda@nvda.groups.io

Sent: Friday, May 25, 2018 12:23 PM

Subject: Re: [nvda] sounds ?

Hi

Is there any sounds at all on the computer? or are you getting Window sounds but not having nvda speaking?

Gene nz

On 5/26/2018 6:00 AM, Danni wrote:

 

I had to reboot several times yesterday because NVDA was not reading documents and realized this morning that I lost my sounds where do I find them to turn them back  on?

 

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

From: Brian Vogel

To: nvda@nvda.groups.io

Sent: Friday, May 25, 2018 12:17 PM

Subject: Re: [nvda] sounds ?

What generation of Windows are you using.  It may be slightly different on Windows 7 than Windows 10, for instance.

Also, what is the make/model of your computer and did it come with function keys that were mapped to doing things like muting, increasing/decreasing volume, increasing/decreasing screen brightness, etc.  You may be able to exploit those, but you'd have to know which are which for your specific make/model.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 

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

From: Brian Vogel

To: nvda@nvda.groups.io

Sent: Friday, May 25, 2018 12:40 PM

Subject: Re: [nvda] sounds ?

Danni,

         If it turns out that your Windows sound output has been muted, be certain to ask your computer guy if there is a key or key sequence on your keyboard you can hit to unmute it (or to try to unmute it).

         On my HP laptop, where I've turned off the "Quick Function Keys" feature so that I have access to the F keys "as God intended," the F6 key is the mute/unmute toggle.  F7 is decrease volume and F8 is increase volume.  All of these only serve those functions if I'm holding down the Fn key plus the previously noted key together.  What's nice is even if the sound is muted, if you attempt to either increase or decrease volume it will unmute the sound as part of that.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 

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

From: Brian Vogel

To: nvda@nvda.groups.io

Sent: Friday, May 25, 2018 12:33 PM

Subject: Re: [nvda] sounds ?

On Fri, May 25, 2018 at 12:30 pm, Danni wrote:

am guessing with those questions it's not nvda that had the sounds but my computer?

That's the presumption I'm operating on, too.   I have a friend who's an avid NVDA user and who's accidentally muted her Windows sound output in the past.  Luckily the keyboard she has actually has a dedicated button for mute/unmute that toggles the sound on if its off and off if its on.

Many computers can do this via hitting the Fn key along with the correct F key across the top.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007