Date   
Re: Tifflotechnia's Vocalizer voices

Quentin Christensen
 

Yes, it is ready, although I'm not sure if it is the current version available from  https://vocalizer-nvda.com/ or whether they were waiting to upload it.  Rui from Tiflotecnia is fairly active on the group, so I am sure he will see this and reply in due course.

Kind regards

Quentin.

On Thu, Dec 12, 2019 at 1:14 PM Supanut Leepaisomboon <supanut2000@...> wrote:
Hi,
Is the Vocalizer voices from Tifflotechnia ready for NVDA 2019.3?
Many thanks



--
Quentin Christensen
Training and Support Manager

Re: error in beta1 instalation

Quentin Christensen
 

Hi Alexandre,

The log should be in your %temp% folder, and should be called nvda.log for the most recent run (or the currently running version if NVDA is currently running), and nvda-old.log for the previous instance.

You can send it to me at info@...

Another thing to try is restarting the computer if you haven't since you uninstalled the old version (you actually didn't need to do that, you could have installed it over the top which would have updated your copy).  Also, if you have an anti-virus program running (aside from Windows Defender) try disabling it before installing NVDA.  Finally if you have controlled folder access enabled in Windows 10, try turning that off while installing NVDA (the installation still works, except it can't create a desktop shortcut).

Regards

Quentin.

On Wed, Dec 11, 2019 at 11:40 PM Alexandre Alves Toco <alexandretoco@...> wrote:

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

 



--
Quentin Christensen
Training and Support Manager

Re: to Tyler Spivey

Ralf Kefferpuetz
 

Speaking of passwords in 2019.3 only covers the speaking of passwords in a console window...
For other password speaking you still have to use a addon.

Cheers,
Ralf

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Luke Davis
Sent: Donnerstag, 12. Dezember 2019 02:07
To: nvda@nvda.groups.io
Subject: Re: [nvda] to Tyler Spivey

On Wed, 11 Dec 2019, Cohn, Jonathan wrote:

I thought speaking of passwords was included as a standard feature in 2019.3. Did I read wrong or perhaps this add-on
has additional function?

Only in consoles. Not in general. A bit incomplete perhaps, but that's how it is.

In-Process 12th December

Quentin Christensen
 

Hi everyone,

The final In-Process for the year is out!  Lots of info on NVDA 2019.3 Beta 1, how to run it, and a walk-through of new and existing track changes features in Word: https://www.nvaccess.org/post/in-process-12th-december/

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager

Re: Does anybody use a telnet BBS?

John Isige
 

Hi. Yep, I can put it up no problem. It's small so I figure one person's interest is enough to make it worth it. I want to see if I can get another client working too, and I have to figure out what the whole process is for submitting an addon, so it might be a bit, but I'll try to get it done as soon as I can.


I should add that if you've got a telnet client that works, you can telnet to the BBS I'm on.


bbs.iscabbs.com


The client provides some extra features and at least the one I use provides an editor, which telnet doesn't, that works like a normal editor for the most part, so you can arrow up through your whole post and edit before submitting, stuff like that. But in case anybody wants to check it out before I get the addon(s) up, depending on whether I get the other client working or not, you can have a look.

On 12/11/2019 0:36, Angelo Sonnesso wrote:
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.







Re: NVDA with Zoom

Surendra JUJJAVARAPU
 

 I am using head phones but it is speaking. there is any way to stop it.

Re: NVDA sometimes loses control and needs to be restarted

Mário Navarro
 

hi


The same thing happens on my laptop.

windows 10 latest.

intel 7 kabilake, 16 RAM,.

cheers.

Às 10:55 de 10/12/2019, Vincent Le Goff escreveu:

Hi everyone,


This has been happening for some time, on so many computers and with so many different NVDA versions I can't believe I would be the only one to see this, and it's not a huge inconvenience, but it's strange and might be worth looking into.  Regardless of the activity sometimes NVDA "loses control".  The key hooks (the NVDA key and all the shortcuts associated with it) stop working.  Using the numeric keypad works as would without NVDA.  Pressing Caplocks, which is a NVDA key for me, triggers the CapLock function.  NVDA still works somewhat and tries to report information, but one can't open the NVDA menu, read the time, look at the window title or indeed do lots of things controlled directly by NVDA.


When does it happen?  I've tried to reproduce the issue and it's tricky.  It never seems to happen at a given time or in any given application.  All I know is that it seems to "lose control" when a lot of memory is required by other applications, which creates some kind of lag.  So this happens in a browser when the site has a lot of scripts for instance.  This can happen in Word if the document is long.  This can happen while the Windows CLI is opened and a "demanding" task is running.  This can happen when lots of update information is sent to NVDA (the message queue gets long). It happens more frequently if the machine on which NVDA runs doesn't have a lot of memory.  It sounds like a Windows lock, not NVDA's fault, but is there a workaround?  Restarting NVDA and the delay it causes isn't really annoying, but it's definitely strange.


Most important question though: has anyone noticed this problem? Or am I the only lucky one?  Does happen!


Thanks,


Vincent


--
A acção pode nem sempre ser felicidade, mas não há felicidade sem acção...

Re: Tifflotechnia's Vocalizer voices

Don H
 

I currently am running the trial of the vocalizer voices from ATGuys with the 2019.3 beta and the same is available from Code Factory.

On 12/11/2019 8:14 PM, Supanut Leepaisomboon wrote:
Hi,
Is the Vocalizer voices from Tifflotechnia ready for NVDA 2019.3?
Many thanks

Tifflotechnia's Vocalizer voices

 

Hi,
Is the Vocalizer voices from Tifflotechnia ready for NVDA 2019.3?
Many thanks

Re: Vocalizer expressive voices

Gene
 

Try the following:
Open the speech dialog with control, NVDA key, v.
Type the letter e and see if you recognize the word English.  If not, type e repeatedly and see.  If you do, or think you do, press enter. 
 

Gene
----- Original Message -----
From: Don H
Sent: Wednesday, December 11, 2019 7:06 PM
Subject: Re: [nvda] vocalizer expressive voices

As I said the whole NVDA UI was displayed in a non english language that
I could not read.

On 12/11/2019 6:51 PM, Abbie Taylor wrote:
> Wow, did you try changing the language in NVDA's general preferences first?
> --
> Abbie Johnson Taylor, Author
> http://www.abbiejohnsontaylor.com
> http://abbiescorner.wordpress.com
> abbietaylor945@...
>



Vocalizer expressive voices

Don H
 

Does it make any difference where you purchase the vocalizer addon for nvda? Do you buy it from ATGuys or dirrectly from Code Factory? Any difference in support? I am in the United States.

Re: to Tyler Spivey

Luke Davis
 

On Wed, 11 Dec 2019, Cohn, Jonathan wrote:

I thought speaking of passwords was included as a standard feature in 2019.3. Did I read wrong or perhaps this add-on has additional function?
Only in consoles. Not in general. A bit incomplete perhaps, but that's how it is.

Re: Vocalizer expressive voices

Don H
 

As I said the whole NVDA UI was displayed in a non english language that I could not read.

On 12/11/2019 6:51 PM, Abbie Taylor wrote:
Wow, did you try changing the language in NVDA's general preferences first?
--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...

Re: Vocalizer expressive voices

Abbie Taylor <abbietaylor945@...>
 

Wow, did you try changing the language in NVDA's general preferences first?
--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...

Re: Vocalizer expressive voices

Abbie Taylor <abbietaylor945@...>
 

I'm experiencing the same issue with Code Factory Vocalizer. I wasn't aware it was necessary to deactivate a license before upgrading my Windows 10 version. Now, I'm out of activation keys. I just emailed Code Factory through their contact form. So, will see what happens.
--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...

Re: NVDA 2019.3Beta1 and devices's manager

Kevin Cussick
 

well I think you need an installed copy and it will read fine.

On 11/12/2019 14:49, bering.p wrote:
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: to Tyler Spivey

Jonathan COHN
 

I thought speaking of passwords was included as a standard feature in 2019.3. Did I read wrong or perhaps this add-on has additional function?

Re: to Tyler Spivey

Ralf Kefferpuetz
 

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Mittwoch, 11. Dezember 2019 19:57
To: nvda@nvda.groups.io
Subject: Re: [nvda] to Tyler Spivey

This link doesn't get me to any speak addon addon to try

On 12/11/2019 12:44 PM, Ralf Kefferpuetz wrote:
Please try this one, it is python 3 ready:
https://github.com/nvdaes/reportPasswords/releases/download/1.5-de


cheers,
Ralf-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Mittwoch, 11. Dezember 2019 18:54
To: nvda@nvda.groups.io
Subject: [nvda] to Tyler Spivey

I believe you are the author of the NVDA addon speak passwords.
I hope you are going to update the addon to work with python 3 soon as it seems my typing skills go down when typing in a password.
Thanks for your efforts.








Re: NVDA and older synthesizers question

Gene
 

You can buy a USB sound card for less than ten American dollars.  You should be able to just plug in the sound card and use it.  I believe there are a small number of plugins, but I don't know if any are officially supported, that allow you to use NVDA with specific external synthesizers.  But which one or ones do you want to use?  NVDA itself doesn't support external synthesizers.
 
Gene

----- Original Message ------
Gene
----- Original Message -----
Sent: Wednesday, December 11, 2019 11:23 AM
To: NVDA
Subject: [nvda] NVDA and older synthesizers question

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: Vocalizer expressive voices

David Griffith
 

I don't know about Vocaliser Voices but I have been assured that, unlike in the past, the latest version of the Code Factory Eloquence setup has been amended so that you do not have to de-activate for a new version of Windows upgrade. From memory this worked, I think when I went to Windows 19.03.
I think if you are doing a complete fresh install it may be a different matter.
I can DropBox the Eloquence setup which I use if that would help.

David Griffith


If you

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Orlando Enrique Fiol via Groups.Io
Sent: 11 December 2019 18:26
To: nvda@nvda.groups.io
Subject: Re: [nvda] Vocalizer expressive voices

At 10:21 AM 12/11/2019, Don H wrote:
>Are you talking about sapi 5 voices? Where do you purchase these voices?


I purchased mine from the Tech Guys website. However, I truly don't recommend anyone purchase these SAPI5 voices if they routinely reinstall Windows. With each reinstallation, you lose one of the three activations Code Factory provides. They recommend deactivating before reinstalling Windows, so that an activation is not lost.
However, there are times when one doesn't know one will reinstall until their machine won't boot, which is what happened to me a few times.
At this point, I have no remaining activations for my desktop or laptop. Contacting Eduard Sanchez, one of Code Factory's founders, has been frustrating, as he does not return my emails. I now have a completely useless set of SAPI5 voices through no fault of my own .
If Dropbox provides a device deactivation dialogue, Code Factory can and should as well. It's ridiculous for a product's legal owner not to be able to deactivate devices at will.
Orlando Enrique Fiol