Andrea: I got the driver, but I can't get any of the voices to work. Is
there a new link for them as well?

On 3/11/2020 4:29 PM, Andrea Sherry wrote:

This is a direct link to the new driver:
https://www.tiflotecnia.net/Instal/vocalizer_expressive_driver-3.1.1.nvda-addon

Cheers
Andrea

Are those new orbit displays have new features? Where can I purchase it? Is the Orbit Reader 40 more powerfull than the 20? How is the 20 plus different than the regular 20? Is the reader 40 more featured than the 20?
I know, beginner questions for someone who doesn't have a braille display, so yeah...
Josh Kennedy wrote:

Hi,
Will nvda2019.3 work with the new orbit displays including. Orbit reader20 plus, and orbit reader40? And will NVDA work fully with the orbit writer braille keyboard for inputting grade2 braille?
The orbit reader20plus is $700. The orbit reader40 is on pre-order for $1400. And the orbit writer braille keyboard is $99.

Josh

Sent from my iPod

Hi,
Will nvda2019.3 work with the new orbit displays including. Orbit reader20 plus, and orbit reader40? And will NVDA work fully with the orbit writer braille keyboard for inputting grade2 braille?
The orbit reader20plus is $700. The orbit reader40 is on pre-order for $1400. And the orbit writer braille keyboard is $99.

Josh


Sent from my iPod

This is a direct link to the new driver:
https://www.tiflotecnia.net/Instal/vocalizer_expressive_driver-3.1.1.nvda-addon

Cheers
Andrea

Dear all,

I am currently looking at all the ESpeak-NG variant files in
C:\Program Files (x86)\NVDA\synthDrivers\espeak-ng-data\voices\!v. I
was hoping to dip my feet in editing and improving ESpeak-NG variants
in the coming days, and see what I might be able to come up with.
* The variant files don't seem to have any extension. Which editor
should I open them with? Currently viewing a lot of numbers when
opening one of the variant files using Notepad.
* I would assume that if these numbers are meaningful, they depict
different parameters of a voice. Is there some reference on what these
different properties of speech are, so that I know what aspect of the
speech I am tweakingg when changing any number?
* Any other tips or thoughts on creating new ESpeak-NG variants and
refining existing one would also be useful.

I would greatly appreciate any assistance.

Best Regards,
Bhavya

Hi,

I would like to know, are there visually impaired people using wordpress for your site?

Are you using any free webhosting, and any of them are accessible using NVDA?

Thanks,

William

Hi
I’m having a problem reading a Libra office Calc spreadsheet. On opening
the file I press Control+home to start at the top but as soon as I try and
use the arrow keys to move between cells, silence ensues. Please find the
log file image below.

Cheers
Chris

INFO - __main__ (11:20:22.891) - MainThread (3444):
Starting NVDA version 2019.3.1
INFO - core.main (11:20:23.094) - MainThread (3444):
Config dir: C:\Users\Chris\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (11:20:23.094) - MainThread (3444):
Loading config: C:\Users\Chris\AppData\Roaming\nvda\nvda.ini
INFO - core.main (11:20:23.235) - MainThread (3444):
Using Windows version 10.0.18363 workstation
INFO - core.main (11:20:23.241) - MainThread (3444):
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 (11:20:23.241) - MainThread (3444):
Using comtypes version 1.1.7
INFO - core.main (11:20:23.241) - MainThread (3444):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (11:20:23.889) - MainThread (3444):
Loaded synthDriver oneCore
INFO - core.main (11:20:23.889) - MainThread (3444):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version
1.12.0
INFO - brailleInput.initialize (11:20:23.894) - MainThread (3444):
Braille input initialized
INFO - braille.initialize (11:20:23.894) - MainThread (3444):
Using liblouis version 3.10.0
INFO - braille.initialize (11:20:23.899) - MainThread (3444):
Using pySerial version 3.4
INFO - braille.BrailleHandler.setDisplayByName (11:20:23.909) - MainThread
(3444):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - core.main (11:20:24.178) - MainThread (3444):
Java Access Bridge support initialized
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (11:20:24.204) -
_UIAHandler.UIAHandler.MTAThread (8756):
UIAutomation: IUIAutomation6
INFO - core.main (11:20:25.370) - MainThread (3444):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(11:22:07.383) - MainThread (3444):
Developer info for navigator object:
name: None
role: ROLE_TABLECELL
roleText: None
states:
isFocusable: False
hasFocus: False
Python object:
<NVDAObjects.Dynamic_SymphonyTableCellEditableTextWithAutoSelectDetectionIAccessible
object at 0x07DCF390>
Python class mro: (<class
'NVDAObjects.Dynamic_SymphonyTableCellEditableTextWithAutoSelectDetectionIAccessible'>,
<class 'appModules.soffice.SymphonyTableCell'>, <class
'NVDAObjects.behaviors.EditableTextWithAutoSelectDetection'>, <class
'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>,
<class 'NVDAObjects.behaviors.EditableText'>, <class
'editableText.EditableText'>, <class 'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>,
<class 'baseObject.AutoPropertyObject'>, <class 'object'>)
description: None
location: RectLTWH(left=0, top=0, width=0, height=0)
value: None
appModule: <'soffice' (appName 'soffice', process ID 5132) at address
87733f0>
appModule.productName: 'LibreOffice'
appModule.productVersion: '6.3.4.2'
TextInfo: <class 'appModules.soffice.SymphonyTextInfo'>
windowHandle: 394264
windowClassName: 'SALFRAME'
windowControlID: 0
windowStyle: 365887488
extendedWindowStyle: 256
windowThreadID: 3652
windowText: 'Phase2_Drawdown.ods - LibreOffice Calc'
displayText: ''
IAccessibleObject: <POINTER(IAccessible2) ptr=0x746781c at 8672b20>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=394264, objectID=-4,
childID=-1037
IAccessible accName: None
IAccessible accRole: None
IAccessible accState: exception: unsupported operand type(s) for &:
'NoneType' and 'int'
IAccessible accDescription: None
IAccessible accValue: None
IAccessible2 windowHandle: 0
IAccessible2 uniqueID: 0
IAccessible2 role: ROLE_SYSTEM_CELL
IAccessible2 states: (0)
IAccessible2 attributes: None

Hello. There has been some Chromium update wich makes nvda non reads properly some sites. one of those sites is https://play.pokemonshowdown.com

This site shows dynamic text wich NVDA reads line by line. But since one or two weeks each time a new line is printed NVDA reads all lines making it imposible to use the chat section  or battle for example.

This problem probably is happening for other sites with dynamic content.

the problem run when using Chrome and Edge chromium, not with firefox. Also using NVDA and JAWS, but windows narrator still works fine.

Could I get someone to send me the link to Tiflotecnia Vocalizer 3.0 Expressive that works on NVDA 2019.3.1? I mistakenly thought the manage add-ons page would take me there, but it says that the 3.0.14 version is incompatible when I open the download link from that page. https://vocalizer-nvda.com/downloads

On 3/11/2020 5:06 PM, Gerardo Corripio wrote:

OK and now? What’s the next step? It’s been several years since I did this, thus any tips to activate?

 

                                                                                              Enviado desde Correo para Windows 10

 

De: Rui Fontes
Enviado: miércoles, 11 de marzo de 2020 03:59 p. m.
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] NVDA's Tiflotecnia Vocalizer stopoped working again

 

Hello!

 

Go to %appdata%\vocalizer-for-nvda and delete both files.

 

I have already increased your remaining activations counter.

 

Regards,

 

Rui Fontes

Tiflotecnia, Lda.

 

 

 

Às 21:50 de 11/03/2020, Gerardo Corripio escreveu:

sSame thing; I get the error that the license is not valid due to the activation file being damaged? But why or how? I just turned off and on my Laptop like usual! And again with the newest version of Vocalizer, whose log file says; I’ll post it in another message; this thing isn’t letting me paste in this one. BE on the lookout!

 

 

 

                                                                                              Enviado desde Correo para Windows 10

 

De: Rui Fontes
Enviado: miércoles, 11 de marzo de 2020 03:41 p. m.
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] NVDA's Tiflotecnia Vocalizer stopoped working again

 

Try using the new driver that Andrea gaves the link...

 

Regards,

 

Rui Fontes

 

Às 21:19 de 11/03/2020, Gerardo Corripio escreveu:

Any hints what might have happened between yesterday and today that today when I turned on my Windows10, it came up talking via the Windows10 1Core voice? Aside from the error of Vocalizer, I’d get another one, that said that the license wasn’t valid etc., aside from the error that over at Tiflotecnia is trying to be fixed.

When I go into NVDA, Vocalizer does appear in the menu, bugt not within the Synthesizer menu via NVDA+Control+s? Here’s my log in case any of you guys know what might have happened? I’d like to get my vocalizer voices back!

INFO - __main__ (15:09:16.670) - MainThread (9736):

Starting NVDA version 2019.3.1

INFO - core.main (15:09:17.803) - MainThread (9736):

Config dir: C:\Users\gerac\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (15:09:17.803) - MainThread (9736):

Loading config: C:\Users\gerac\AppData\Roaming\nvda\nvda.ini

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Windows version 10.0.18363 workstation

INFO - core.main (15:09:18.076) - MainThread (9736):

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:09:18.076) - MainThread (9736):

Using comtypes version 1.1.7

INFO - core.main (15:09:18.076) - MainThread (9736):

Using configobj version 5.1.0 with validate version 1.0.1

WARNING - external:synthDrivers.vocalizer_expressive.storage._loadLicenseData (15:09:19.017) - MainThread (9736):

Couldn't automatically unpickle 'C:\\Users\\gerac\\AppData\\Roaming\\vocalizer-for-nvda\\activation.dat', trying manual method

ERROR - synthDriverHandler.setSynth (15:09:19.031) - MainThread (9736):

setSynth

Traceback (most recent call last):

  File "synthDriverHandler.pyc", line 103, in setSynth

  File "synthDriverHandler.pyc", line 76, in getSynthInstance

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\__init__.py", line 82, in __init__

    _vocalizer.initialize(self._onIndexReached)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 182, in initialize

    preInitialize()

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 164, in preInitialize

    platformDll.vplatform_GetInterfaces(byref(installResources), byref(platformResources))

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_veTypes.py", line 302, in veCheckForError

    raise VeError(result, "Vocalizer Error: %s: %x" %(func.__name__, result))

synthDrivers.vocalizer_expressive._veTypes.VeError: Vocalizer Error: vplatform_GetInterfaces: f5

INFO - synthDriverHandler.setSynth (15:09:19.236) - MainThread (9736):

Loaded synthDriver oneCore

INFO - core.main (15:09:19.526) - MainThread (9736):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (15:09:19.526) - MainThread (9736):

Braille input initialized

INFO - braille.initialize (15:09:19.526) - MainThread (9736):

Using liblouis version 3.10.0

INFO - braille.initialize (15:09:19.536) - MainThread (9736):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (15:09:19.546) - MainThread (9736):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (15:09:19.901) - MainThread (9736):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:09:19.922) - _UIAHandler.UIAHandler.MTAThread (4260):

UIAutomation: IUIAutomation6

WARNING - external:vlc_settingsHandler.QTInterface._loadRecentFiles (15:09:22.659) - MainThread (9736):

Error: number of recent files  and time count are different

INFO - core.main (15:09:22.959) - MainThread (9736):

NVDA initialized

ERROR - external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer._doRenew (15:09:23.596) - Thread-2 (2352):

Error renewing license.

Traceback (most recent call last):

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py", line 142, in _doRenew

    newData = client.renew(number, token)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 60, in renew

    return self._do_request(url, data)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 32, in _do_request

    response = urllib.request.urlopen(request)

  File "urllib\request.pyc", line 222, in urlopen

  File "urllib\request.pyc", line 531, in open

  File "urllib\request.pyc", line 641, in http_response

  File "urllib\request.pyc", line 569, in error

  File "urllib\request.pyc", line 503, in _call_chain

  File "urllib\request.pyc", line 649, in http_error_default

urllib.error.HTTPError: HTTP Error 404: Not Found

 

                                                                                              Enviado desde Correo para Windows 10

 

 

 

Rui Thanks a lot! Just wanted to let you know that I was able to activate my license again. I went into the NVDA/Vocalizer menu and immediately it prompted me for my Email and password, and away it activated! I thought it was another process like the first time I activated in which I had to go into the site and log-in etc., thus that’s why I asked on the NVDA list, but it’s all working now. What a relief! Thanks for everything! And especially for finally fixing the bug of the activation message found in Vocalizer 3.10! Now with the 3.11 it’s working great! Thanks again for everything! Your company rocks! As they say in English! Keep up the great work!