|
Re: NV access site does not open
Sarah k Alawami
Makes sence, like when a weapon jams, or did back in the 1800s. I’ll have to consult my oxford dictionary then. Anyway I’ll shove off now. Looks like the jam is fixed though, which is good.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Louise Pfau Sent: Wednesday, December 1, 2021 12:02 PM To: nvda@nvda.groups.io Subject: Re: [nvda] NV access site does not open Hi. The expression "Hang fire" can also mean that something isn't working. The NVDA sight hung fire while they were working on it.
Louise
|
|
|
Sometimes there is :) And there are different levels of logging. The default "info" level gives information particularly about errors which occur, and there are higher levels which record more information (which we only recommend setting when testing or capturing information - eg if you could give me the same log but at "debug" level, it would show what keystrokes you had pressed during that time, and what NVDA had spoken, which would possibly be enough to work out what you were doing.
If sending particularly a debug level log, do send it to me offlist, just because of the risk of it capturing anything sensitive.
Kind regards
Quentin.
On Thu, Dec 2, 2021 at 12:15 PM Chris Smart < ve3rwj@...> wrote: Oh sorry. I assumed wrongly that there would be enough information in the log. I can’t get them to happen right now but if they do, I’ll do a better job explaining what I was doing at the time. Ok well that's something :) If you can pinpoint something which causes the errors to happen, please let me know so we can investigate further. On Thu, Dec 2, 2021 at 8:08 AM Chris Smart <ve3rwj@...> wrote: HI. No, nothing beyond the descending error sounder. I didn’t notice any anomalous behaviour. Aside from the errors in the log, did you notice anything when they happened? On Thu, Dec 2, 2021 at 2:16 AM Chris Smart <ve3rwj@...> wrote: There are a couple errors below the usual initialization messages. Log follows: INFO - __main__ (10:11:56.663) - MainThread (12244): Starting NVDA version 2021.3rc1 INFO - core.main (10:11:56.898) - MainThread (12244): Config dir: C:\Users\Chris\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (10:11:56.898) - MainThread (12244): Loading config: C:\Users\Chris\AppData\Roaming\nvda\nvda.ini INFO - core.main (10:11:57.041) - MainThread (12244): Windows version: Windows 10 21H2 (10.0.19044) workstation INFO - core.main (10:11:57.041) - MainThread (12244): Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)] INFO - core.main (10:11:57.041) - MainThread (12244): Using comtypes version 1.1.8 INFO - core.main (10:11:57.041) - MainThread (12244): Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (10:11:57.681) - MainThread (12244): Loaded synthDriver eloquence INFO - core.main (10:11:57.681) - MainThread (12244): Using wx version 4.1.1 msw (phoenix) wxWidgets 3.1.5 with six version 1.16.0 INFO - brailleInput.initialize (10:11:57.681) - MainThread (12244): Braille input initialized INFO - braille.initialize (10:11:57.681) - MainThread (12244): Using liblouis version 3.19.0 INFO - braille.initialize (10:11:57.681) - MainThread (12244): Using pySerial version 3.5 INFO - braille.BrailleHandler.setDisplayByName (10:11:57.691) - MainThread (12244): Loaded braille display driver noBraille, current display has 0 cells. INFO - core.main (10:11:57.811) - MainThread (12244): Java Access Bridge support initialized INFO - _UIAHandler.UIAHandler.MTAThreadFunc (10:11:57.871) - _UIAHandler.UIAHandler.MTAThread (12912): UIAutomation: IUIAutomation6 INFO - core.main (10:11:58.066) - MainThread (12244): NVDA initialized ERROR - eventHandler.executeEvent (10:12:28.205) - MainThread (12244): error executing event: UIA_controllerFor on <NVDAObjects.Dynamic_StartMenuSearchFieldSearchFieldEditableTextWithAutoSelectDetectionUIA object at 0x03B517B0> with extra args of {} Traceback (most recent call last): File "eventHandler.pyc", line 284, in executeEvent File "eventHandler.pyc", line 98, in __init__ File "eventHandler.pyc", line 107, in next File "NVDAObjects\UIA\__init__.pyc", line 2157, in event_UIA_controllerFor File "baseObject.pyc", line 42, in __get__ File "baseObject.pyc", line 146, in _getPropertyViaCache File "NVDAObjects\UIA\__init__.pyc", line 1935, in _get_controllerFor File "NVDAObjects\__init__.pyc", line 92, in __call__ File "NVDAObjects\UIA\__init__.pyc", line 1017, in findOverlayClasses AttributeError: module 'NVDAObjects.UIA.spartanEdge' has no attribute 'EdgeHTMLRootContainer' ERROR - scriptHandler.executeScript (10:13:16.177) - MainThread (12244): error executing script: <bound method WordDocument.script_toggleAlignment of <NVDAObjects.Dynamic_OutlookUIAWordDocumentWordDocumentEditableTextWithAutoSelectDetectionUIAWindowNVDAObject object at 0x075DFE30>> with gesture 'ctrl+r' Traceback (most recent call last): File "scriptHandler.pyc", line 208, in executeScript File "NVDAObjects\window\winword.pyc", line 1295, in script_toggleAlignment File "NVDAObjects\window\winword.pyc", line 1240, in _WaitForValueChangeForAction File "NVDAObjects\window\winword.pyc", line 1295, in <lambda> File "monkeyPatches\comtypesMonkeyPatches.pyc", line 86, in new__getattr__ File "comtypes\client\lazybind.pyc", line 168, in __getattr__ File "comtypes\automation.pyc", line 729, in _invoke File "monkeyPatches\comtypesMonkeyPatches.pyc", line 30, in __call__ _ctypes.COMError: (-2146822463, None, ('Object has been deleted.', 'Microsoft Word', 'wdmain11.chm', 25305, None))
-- Quentin Christensen
Training and Support Manager
-- Quentin Christensen
Training and Support Manager
-- Quentin Christensen
Training and Support Manager
|
|
|
Re: NVDA 2021.3 RC 1 is available
Hi Quentin, My copy is working great.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen Sent: Wednesday, December 1, 2021 7:45 PM To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA 2021.3 RC 1 is available Eduardo (and Rosemarie, and everyone else who has checked in reporting that it is all working as expected), Thank you so much, that is great to hear! everything is working fine, and quentin, i went to check the new options, and they are already translated! and my preview was right! Em qua., 1 de dez. de 2021 às 14:07, Rosemarie Chavarria <knitqueen2007@...> escreveu: Hi, Quentin, I just downloaded the new RC version of NVDA and so-far it’s working great for me. Rosemarie Sent from Mail for Windows Hi everyone, The Release Candidate (RC) of NVDA 2021.3 is now available for download and testing. We encourage all users to download this RC and provide feedback. Unless any critical bugs are found, this will be identical to the final 2021.3 release. Highlights
This release introduces support for the new HID Braille specification. This specification aims to standardize support for Braille Displays without needing individual drivers. There are updates to eSpeak-NG and LibLouis, including new Russian and Tshivenda tables. Error sounds can be enabled in stable builds of NVDA via a new advanced settings option. Say all in Word now scrolls the view to keep the current position visible. There are lots of improvements when using Office with UIA. One UIA fix is that Outlook now ignores more types of layout tables in messages.
Changes from Beta 2:
- Restored reporting of backspaced characters in Visual Studio editor
- Updates to translations. Quentin. -- Quentin Christensen
Training and Support Manager
-- Quentin Christensen
Training and Support Manager
|
|
|
Chris Smart
Oh sorry. I assumed wrongly that there would be enough information in the log. I can’t get them to happen right now but if they do, I’ll do a better job explaining what I was doing at the time.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: December 1, 2021 7:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] errors with RC Ok well that's something :) If you can pinpoint something which causes the errors to happen, please let me know so we can investigate further. On Thu, Dec 2, 2021 at 8:08 AM Chris Smart <ve3rwj@...> wrote: HI. No, nothing beyond the descending error sounder. I didn’t notice any anomalous behaviour. Aside from the errors in the log, did you notice anything when they happened? On Thu, Dec 2, 2021 at 2:16 AM Chris Smart <ve3rwj@...> wrote: There are a couple errors below the usual initialization messages. Log follows: INFO - __main__ (10:11:56.663) - MainThread (12244): Starting NVDA version 2021.3rc1 INFO - core.main (10:11:56.898) - MainThread (12244): Config dir: C:\Users\Chris\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (10:11:56.898) - MainThread (12244): Loading config: C:\Users\Chris\AppData\Roaming\nvda\nvda.ini INFO - core.main (10:11:57.041) - MainThread (12244): Windows version: Windows 10 21H2 (10.0.19044) workstation INFO - core.main (10:11:57.041) - MainThread (12244): Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)] INFO - core.main (10:11:57.041) - MainThread (12244): Using comtypes version 1.1.8 INFO - core.main (10:11:57.041) - MainThread (12244): Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (10:11:57.681) - MainThread (12244): Loaded synthDriver eloquence INFO - core.main (10:11:57.681) - MainThread (12244): Using wx version 4.1.1 msw (phoenix) wxWidgets 3.1.5 with six version 1.16.0 INFO - brailleInput.initialize (10:11:57.681) - MainThread (12244): Braille input initialized INFO - braille.initialize (10:11:57.681) - MainThread (12244): Using liblouis version 3.19.0 INFO - braille.initialize (10:11:57.681) - MainThread (12244): Using pySerial version 3.5 INFO - braille.BrailleHandler.setDisplayByName (10:11:57.691) - MainThread (12244): Loaded braille display driver noBraille, current display has 0 cells. INFO - core.main (10:11:57.811) - MainThread (12244): Java Access Bridge support initialized INFO - _UIAHandler.UIAHandler.MTAThreadFunc (10:11:57.871) - _UIAHandler.UIAHandler.MTAThread (12912): UIAutomation: IUIAutomation6 INFO - core.main (10:11:58.066) - MainThread (12244): NVDA initialized ERROR - eventHandler.executeEvent (10:12:28.205) - MainThread (12244): error executing event: UIA_controllerFor on <NVDAObjects.Dynamic_StartMenuSearchFieldSearchFieldEditableTextWithAutoSelectDetectionUIA object at 0x03B517B0> with extra args of {} Traceback (most recent call last): File "eventHandler.pyc", line 284, in executeEvent File "eventHandler.pyc", line 98, in __init__ File "eventHandler.pyc", line 107, in next File "NVDAObjects\UIA\__init__.pyc", line 2157, in event_UIA_controllerFor File "baseObject.pyc", line 42, in __get__ File "baseObject.pyc", line 146, in _getPropertyViaCache File "NVDAObjects\UIA\__init__.pyc", line 1935, in _get_controllerFor File "NVDAObjects\__init__.pyc", line 92, in __call__ File "NVDAObjects\UIA\__init__.pyc", line 1017, in findOverlayClasses AttributeError: module 'NVDAObjects.UIA.spartanEdge' has no attribute 'EdgeHTMLRootContainer' ERROR - scriptHandler.executeScript (10:13:16.177) - MainThread (12244): error executing script: <bound method WordDocument.script_toggleAlignment of <NVDAObjects.Dynamic_OutlookUIAWordDocumentWordDocumentEditableTextWithAutoSelectDetectionUIAWindowNVDAObject object at 0x075DFE30>> with gesture 'ctrl+r' Traceback (most recent call last): File "scriptHandler.pyc", line 208, in executeScript File "NVDAObjects\window\winword.pyc", line 1295, in script_toggleAlignment File "NVDAObjects\window\winword.pyc", line 1240, in _WaitForValueChangeForAction File "NVDAObjects\window\winword.pyc", line 1295, in <lambda> File "monkeyPatches\comtypesMonkeyPatches.pyc", line 86, in new__getattr__ File "comtypes\client\lazybind.pyc", line 168, in __getattr__ File "comtypes\automation.pyc", line 729, in _invoke File "monkeyPatches\comtypesMonkeyPatches.pyc", line 30, in __call__ _ctypes.COMError: (-2146822463, None, ('Object has been deleted.', 'Microsoft Word', 'wdmain11.chm', 25305, None))
-- Quentin Christensen
Training and Support Manager
-- Quentin Christensen
Training and Support Manager
|
|
|
Re: NVDA 2021.3 RC 1 is available
Eduardo (and Rosemarie, and everyone else who has checked in reporting that it is all working as expected),
Thank you so much, that is great to hear!
Kind regards
Quentin.
everything is working fine, and quentin, i went to check the new options, and they are already translated! and my preview was right!
Em qua., 1 de dez. de 2021 às 14:07, Rosemarie Chavarria < knitqueen2007@...> escreveu: Hi, Quentin, I just downloaded the new RC version of NVDA and so-far it’s working great for me. Rosemarie Sent from Mail for Windows Hi everyone, The Release Candidate (RC) of NVDA 2021.3 is now available for download and testing. We encourage all users to download this RC and provide feedback. Unless any critical bugs are found, this will be identical to the final 2021.3 release. Highlights
This release introduces support for the new HID Braille specification. This specification aims to standardize support for Braille Displays without needing individual drivers. There are updates to eSpeak-NG and LibLouis, including new Russian and Tshivenda tables. Error sounds can be enabled in stable builds of NVDA via a new advanced settings option. Say all in Word now scrolls the view to keep the current position visible. There are lots of improvements when using Office with UIA. One UIA fix is that Outlook now ignores more types of layout tables in messages.
Changes from Beta 2:
- Restored reporting of backspaced characters in Visual Studio editor
- Updates to translations. Quentin. -- Quentin Christensen
Training and Support Manager
-- Quentin Christensen
Training and Support Manager
|
|
|
Ok well that's something :) If you can pinpoint something which causes the errors to happen, please let me know so we can investigate further.
Kind regards
Quentin.
On Thu, Dec 2, 2021 at 8:08 AM Chris Smart < ve3rwj@...> wrote: HI. No, nothing beyond the descending error sounder. I didn’t notice any anomalous behaviour. Aside from the errors in the log, did you notice anything when they happened? On Thu, Dec 2, 2021 at 2:16 AM Chris Smart <ve3rwj@...> wrote: There are a couple errors below the usual initialization messages. Log follows: INFO - __main__ (10:11:56.663) - MainThread (12244): Starting NVDA version 2021.3rc1 INFO - core.main (10:11:56.898) - MainThread (12244): Config dir: C:\Users\Chris\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (10:11:56.898) - MainThread (12244): Loading config: C:\Users\Chris\AppData\Roaming\nvda\nvda.ini INFO - core.main (10:11:57.041) - MainThread (12244): Windows version: Windows 10 21H2 (10.0.19044) workstation INFO - core.main (10:11:57.041) - MainThread (12244): Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)] INFO - core.main (10:11:57.041) - MainThread (12244): Using comtypes version 1.1.8 INFO - core.main (10:11:57.041) - MainThread (12244): Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (10:11:57.681) - MainThread (12244): Loaded synthDriver eloquence INFO - core.main (10:11:57.681) - MainThread (12244): Using wx version 4.1.1 msw (phoenix) wxWidgets 3.1.5 with six version 1.16.0 INFO - brailleInput.initialize (10:11:57.681) - MainThread (12244): Braille input initialized INFO - braille.initialize (10:11:57.681) - MainThread (12244): Using liblouis version 3.19.0 INFO - braille.initialize (10:11:57.681) - MainThread (12244): Using pySerial version 3.5 INFO - braille.BrailleHandler.setDisplayByName (10:11:57.691) - MainThread (12244): Loaded braille display driver noBraille, current display has 0 cells. INFO - core.main (10:11:57.811) - MainThread (12244): Java Access Bridge support initialized INFO - _UIAHandler.UIAHandler.MTAThreadFunc (10:11:57.871) - _UIAHandler.UIAHandler.MTAThread (12912): UIAutomation: IUIAutomation6 INFO - core.main (10:11:58.066) - MainThread (12244): NVDA initialized ERROR - eventHandler.executeEvent (10:12:28.205) - MainThread (12244): error executing event: UIA_controllerFor on <NVDAObjects.Dynamic_StartMenuSearchFieldSearchFieldEditableTextWithAutoSelectDetectionUIA object at 0x03B517B0> with extra args of {} Traceback (most recent call last): File "eventHandler.pyc", line 284, in executeEvent File "eventHandler.pyc", line 98, in __init__ File "eventHandler.pyc", line 107, in next File "NVDAObjects\UIA\__init__.pyc", line 2157, in event_UIA_controllerFor File "baseObject.pyc", line 42, in __get__ File "baseObject.pyc", line 146, in _getPropertyViaCache File "NVDAObjects\UIA\__init__.pyc", line 1935, in _get_controllerFor File "NVDAObjects\__init__.pyc", line 92, in __call__ File "NVDAObjects\UIA\__init__.pyc", line 1017, in findOverlayClasses AttributeError: module 'NVDAObjects.UIA.spartanEdge' has no attribute 'EdgeHTMLRootContainer' ERROR - scriptHandler.executeScript (10:13:16.177) - MainThread (12244): error executing script: <bound method WordDocument.script_toggleAlignment of <NVDAObjects.Dynamic_OutlookUIAWordDocumentWordDocumentEditableTextWithAutoSelectDetectionUIAWindowNVDAObject object at 0x075DFE30>> with gesture 'ctrl+r' Traceback (most recent call last): File "scriptHandler.pyc", line 208, in executeScript File "NVDAObjects\window\winword.pyc", line 1295, in script_toggleAlignment File "NVDAObjects\window\winword.pyc", line 1240, in _WaitForValueChangeForAction File "NVDAObjects\window\winword.pyc", line 1295, in <lambda> File "monkeyPatches\comtypesMonkeyPatches.pyc", line 86, in new__getattr__ File "comtypes\client\lazybind.pyc", line 168, in __getattr__ File "comtypes\automation.pyc", line 729, in _invoke File "monkeyPatches\comtypesMonkeyPatches.pyc", line 30, in __call__ _ctypes.COMError: (-2146822463, None, ('Object has been deleted.', 'Microsoft Word', 'wdmain11.chm', 25305, None))
-- Quentin Christensen
Training and Support Manager
-- Quentin Christensen
Training and Support Manager
|
|
|
Re: Recommendations for NVDA voice
If you haven’t, you might want to try the default English voice as
well. I haven’t used most of the variants and dialects in E-Speak because
I don’t like the voice. But I wanted to discuss it because I didn’t know
if you had tried it and it might be worth trying.
toggle quoted messageShow quoted text
-----Original Message-----
Sent: Wednesday, December 01, 2021 5:10 PM
Subject: Re: [nvda] Recommendations for NVDA voice
Gene,
I agree the speak voices lack the body and do sound harsh, although I have
to admit I did not seriously give all the English American voices a spin.
I will do that soon.
Thanks,
Mani
One voice that hasn’t been discussed, though it may have been mentioned,
is E-Speak. It comes with NVDA, but you have to switch to it if you are
using Windows 10 and 11. While I find it harsh and lacking in body, you
may find that it is easier to understand than some or many others.
Not knowing about the nature of your hearing loss, I’m not recommending
it, just pointing out that it may be more understandable and that it is a part
of NVDA.
If you don’t know how to switch to it and try different e-Speak
voices, list members will tell you.
Gene
-----Original Message-----
Sent: Wednesday, December 01, 2021 11:09 AM
Subject: Re: [nvda] Recommendations for NVDA
voice
On
Wed, Dec 1, 2021 at 10:50 AM, Mani Iyer wrote:
Do you have any recommendation for a ‘clear’ voice under which
which speech synthesizer would possibly help me. ? - Actually,
I don't. The reason for that being
tha
|
|
|
Hi. Need to fill out a reference work for a job interview, and the
form came as a fillable pdf. What's the most accessible way to handle
these? Adobe Reader DC seems to do ok, but doesn't seem to highlight
or focus fields properly. Any thoughts or recommendations? Edge and
Chrome both just open the file without giving me options to edit it,
obviously. thanks.
|
|
|
Re: NV access site does not open
Oh, okay, okay! The only time I heard that Hangfire was from the Rock group The Rolling stones. I never to this day knew what it was. Sent from Mail for Windows
From: JackieSent: December 1, 2021 6:14 AM To: nvda@nvda.groups.ioSubject: Re: [nvda] NV access site does not open Lol, I'm sorry, Eduardo--I'm usually sensitive to non-English speakers. It was late, I was tired, & I messed up. & I am so sorry & embarrassed. Hang fire is just a slang phrase that means wait awhile. So now you learned an English slang! On 12/1/21, Eduardo Fermiano Luccas <25102008luccas@...> wrote: > chaw, the problem seems to be solved now > > Em qua., 1 de dez. de 2021 às 04:33, Shaun Everiss <sm.everiss@...> > escreveu: > >> Hmmm its fine here. >> >> >> On 1/12/2021 6:34 pm, Jackie wrote: >> > It's not you, bro. Just hang fire till tomorrow, & it'll likely be back >> up. >> > >> > On 11/30/21, Eduardo Fermiano Luccas <25102008luccas@...> wrote: >> >> hi friends, i tried to check for updates, and NVDA gave an error, and >> >> i >> am >> >> using NVDA2021.3beta2, and when i opened nv access.org site, it >> failed! can >> >> you help me? >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> > > > > > > -- Subscribe to a WordPress for Newbies Mailing List by sending a message to: wp4newbs-request@... with 'subscribe' in the Subject field OR by visiting the list page at http://www.freelists.org/list/wp4newbs & check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com
|
|
|
Re: Recommendations for NVDA voice
Gene, I agree the speak voices lack the body and do sound harsh, although I have to admit I did not seriously give all the English American voices a spin. I will do that soon.
Thanks, Mani
One voice that hasn’t been discussed, though it may have been mentioned, is
E-Speak. It comes with NVDA, but you have to switch to it if you are using
Windows 10 and 11. While I find it harsh and lacking in body, you may find
that it is easier to understand than some or many others.
Not knowing about the nature of your hearing loss, I’m not recommending it,
just pointing out that it may be more understandable and that it is a part of
NVDA.
If you don’t know how to switch to it and try different e-Speak
voices, list members will tell you.
Gene
-----Original Message-----
Sent: Wednesday, December 01, 2021 11:09 AM
Subject: Re: [nvda] Recommendations for NVDA voice
On
Wed, Dec 1, 2021 at 10:50 AM, Mani Iyer wrote:
Do you have any recommendation for a ‘clear’ voice under which
which speech synthesizer would possibly help me. ? - Actually, I
don't. The reason for that being tha
|
|
|
Re: Recommendations for NVDA voice
I would suggest OneCore mainly because you have the option of achieving higher speech rates with it, if that matters to you. Otherwise, it's personal preference.
Hello Jujube, I did try the Zira voice and I actually like her. But tell me which synthesizer should I be using: Microsoft 5 API or Windows Core Voices? I see a noticeable difference in Zira between the two. And besides, mark is missing from the Microsoft synthesizer. Right now I am using Microsoft’s Zira.
Thanks, Mani On Dec 1, 2021, at 1:22 PM, Jujube < ellaxyu@...> wrote:
Microsoft Mark does sound a little high pitched, you can try pitching it down a few notches to see if it's any better. You could also try the Canadian English voices, but if you don't have Canadian English installed, you'll need to go into windows speech settings to install it. On Wed, Dec 1, 2021 at 10:12 AM Monte Single < mrsingle@...> wrote: Yes, Zira is my voice of choice. Hi, My favorite one-core voice is Zira. She sounds really good at a fast rate. Sent from Mail for Windows From: Jujube
Sent: Wednesday, December 1, 2021 8:48 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Recommendations for NVDA voice Hi, Have you tried some of the other OneCore voices including Zira or mark? They may or may not sound better to you. Otherwise, you could try the Eloquence/Vocalizer addon and see if any of that stuff suits you better. It costs money though, but you can trial it for a weekb before buying. Also, how fast is your speech rate? If you use faster speech rates, most of the other OneCore voices sound significantly better at high speech rates than David, as well as Eloquence and possibly some of the Vocalizer voices. Hope this helps. > On Dec 1, 2021, at 7:51 AM, Mani Iyer via groups.io <mani.g.iyer@...> wrote: > > Hello all, > I am profoundly deaf and wear hearing aids. I am currently using Microsoft’s David's voice. But this voice lacks clarity of certain consonants for my hearing and I find myself resorting to phonetic spelling a lot. Do you have any recommendation for a ‘clear’ voice under which which speech synthesizer would possibly help me. ? > > Thanks. > > Warmly, > Mani > > > > > >
|
|
|
Re: Recommendations for NVDA voice
Hello Jujube, I did try the Zira voice and I actually like her. But tell me which synthesizer should I be using: Microsoft 5 API or Windows Core Voices? I see a noticeable difference in Zira between the two. And besides, mark is missing from the Microsoft synthesizer. Right now I am using Microsoft’s Zira.
Thanks, Mani
On Dec 1, 2021, at 1:22 PM, Jujube < ellaxyu@...> wrote:
Microsoft Mark does sound a little high pitched, you can try pitching it down a few notches to see if it's any better. You could also try the Canadian English voices, but if you don't have Canadian English installed, you'll need to go into windows speech settings to install it. On Wed, Dec 1, 2021 at 10:12 AM Monte Single < mrsingle@...> wrote: Yes, Zira is my voice of choice. Hi, My favorite one-core voice is Zira. She sounds really good at a fast rate. Sent from Mail for Windows From: Jujube
Sent: Wednesday, December 1, 2021 8:48 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Recommendations for NVDA voice Hi, Have you tried some of the other OneCore voices including Zira or mark? They may or may not sound better to you. Otherwise, you could try the Eloquence/Vocalizer addon and see if any of that stuff suits you better. It costs money though, but you can trial it for a weekb before buying. Also, how fast is your speech rate? If you use faster speech rates, most of the other OneCore voices sound significantly better at high speech rates than David, as well as Eloquence and possibly some of the Vocalizer voices. Hope this helps. > On Dec 1, 2021, at 7:51 AM, Mani Iyer via groups.io <mani.g.iyer@...> wrote: > > Hello all, > I am profoundly deaf and wear hearing aids. I am currently using Microsoft’s David's voice. But this voice lacks clarity of certain consonants for my hearing and I find myself resorting to phonetic spelling a lot. Do you have any recommendation for a ‘clear’ voice under which which speech synthesizer would possibly help me. ? > > Thanks. > > Warmly, > Mani > > > > > >
|
|
|
Re: Sometimes NVDA only reads first line of an email in Outlook 2019
It seems that NVDA reads an entire email the first time but when the same email is selected again only the first line is read out.
Windows 10 Version 10.0.19044 Build 19044 (21h2)
NVDA 2021.2
Outlook 2019
|
|
|
Re: Recommendations for NVDA voice
Microsoft James is an Australian accented voice so if you're not used to that accent, it's probably not for you.
the voice I thought was cool was microsoft james, but i don't recommend it to you, she still doesn't have a very clear pronunciation
Em qua., 1 de dez. de 2021 às 16:39, Louise Pfau < louise.pfau@...> escreveu: Hi. I use "Microsoft Richard" from the "English (Canada)" pack, but I don't know if he has the clarity you require.
Louise
|
|
|
Re: problem in using zoom with nvda
Carlos Esteban Martínez Macías
Hi all!
When you have Bluetooth Headphones connected, Windows created an extra device of headphones with microphone and a name that depend on the device. Zoom Tray select the correct device for listen and talk but choose this without take the option system default by default. The problem of this new device is that when an application uses it, the rest of the audio send to another device (Bluetooth Stereo) is mute.
You can open Zoom, go to the settings and in the list of categories select audio. Press tab after of select audio, change input, and output device to system default.
Other solutions are change the output device of NVDA (NVDA + control + s, press tab and select Headphones with Microphone), but you only can listen NVDA and the meeting in this case and with low quality like a phone call.
Regards.
-- Músico (pianista) y ayuda a usuarios ciegos y con discapacidad visual en el uso de lectores de pantalla y tecnología. Experto certificado en el lector de pantalla NVDA. Musician (pianist) and help to the blind people and with visual disability in use of screen readers and technology. Certified expert in the screen reader NVDA.
|
|
|
Re: Recommendations for NVDA voice
the voice I thought was cool was microsoft james, but i don't recommend it to you, she still doesn't have a very clear pronunciation Em qua., 1 de dez. de 2021 às 16:39, Louise Pfau < louise.pfau@...> escreveu:
Hi. I use "Microsoft Richard" from the "English (Canada)" pack, but I don't know if he has the clarity you require.
Louise
|
|
|
Re: NVDA 2021.3 RC 1 is available
everything is working fine, and quentin, i went to check the new options, and they are already translated! and my preview was right!
Em qua., 1 de dez. de 2021 às 14:07, Rosemarie Chavarria < knitqueen2007@...> escreveu:
Hi, Quentin, I just downloaded the new RC version of NVDA and so-far it’s working great for me. Rosemarie Sent from Mail for Windows Hi everyone, The Release Candidate (RC) of NVDA 2021.3 is now available for download and testing. We encourage all users to download this RC and provide feedback. Unless any critical bugs are found, this will be identical to the final 2021.3 release. Highlights
This release introduces support for the new HID Braille specification. This specification aims to standardize support for Braille Displays without needing individual drivers. There are updates to eSpeak-NG and LibLouis, including new Russian and Tshivenda tables. Error sounds can be enabled in stable builds of NVDA via a new advanced settings option. Say all in Word now scrolls the view to keep the current position visible. There are lots of improvements when using Office with UIA. One UIA fix is that Outlook now ignores more types of layout tables in messages.
Changes from Beta 2:
- Restored reporting of backspaced characters in Visual Studio editor
- Updates to translations. Quentin. -- Quentin Christensen
Training and Support Manager
|
|
|
Chris Smart
HI. No, nothing beyond the descending error sounder. I didn’t notice any anomalous behaviour.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: December 1, 2021 3:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] errors with RC Aside from the errors in the log, did you notice anything when they happened? On Thu, Dec 2, 2021 at 2:16 AM Chris Smart <ve3rwj@...> wrote: There are a couple errors below the usual initialization messages. Log follows: INFO - __main__ (10:11:56.663) - MainThread (12244): Starting NVDA version 2021.3rc1 INFO - core.main (10:11:56.898) - MainThread (12244): Config dir: C:\Users\Chris\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (10:11:56.898) - MainThread (12244): Loading config: C:\Users\Chris\AppData\Roaming\nvda\nvda.ini INFO - core.main (10:11:57.041) - MainThread (12244): Windows version: Windows 10 21H2 (10.0.19044) workstation INFO - core.main (10:11:57.041) - MainThread (12244): Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)] INFO - core.main (10:11:57.041) - MainThread (12244): Using comtypes version 1.1.8 INFO - core.main (10:11:57.041) - MainThread (12244): Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (10:11:57.681) - MainThread (12244): Loaded synthDriver eloquence INFO - core.main (10:11:57.681) - MainThread (12244): Using wx version 4.1.1 msw (phoenix) wxWidgets 3.1.5 with six version 1.16.0 INFO - brailleInput.initialize (10:11:57.681) - MainThread (12244): Braille input initialized INFO - braille.initialize (10:11:57.681) - MainThread (12244): Using liblouis version 3.19.0 INFO - braille.initialize (10:11:57.681) - MainThread (12244): Using pySerial version 3.5 INFO - braille.BrailleHandler.setDisplayByName (10:11:57.691) - MainThread (12244): Loaded braille display driver noBraille, current display has 0 cells. INFO - core.main (10:11:57.811) - MainThread (12244): Java Access Bridge support initialized INFO - _UIAHandler.UIAHandler.MTAThreadFunc (10:11:57.871) - _UIAHandler.UIAHandler.MTAThread (12912): UIAutomation: IUIAutomation6 INFO - core.main (10:11:58.066) - MainThread (12244): NVDA initialized ERROR - eventHandler.executeEvent (10:12:28.205) - MainThread (12244): error executing event: UIA_controllerFor on <NVDAObjects.Dynamic_StartMenuSearchFieldSearchFieldEditableTextWithAutoSelectDetectionUIA object at 0x03B517B0> with extra args of {} Traceback (most recent call last): File "eventHandler.pyc", line 284, in executeEvent File "eventHandler.pyc", line 98, in __init__ File "eventHandler.pyc", line 107, in next File "NVDAObjects\UIA\__init__.pyc", line 2157, in event_UIA_controllerFor File "baseObject.pyc", line 42, in __get__ File "baseObject.pyc", line 146, in _getPropertyViaCache File "NVDAObjects\UIA\__init__.pyc", line 1935, in _get_controllerFor File "NVDAObjects\__init__.pyc", line 92, in __call__ File "NVDAObjects\UIA\__init__.pyc", line 1017, in findOverlayClasses AttributeError: module 'NVDAObjects.UIA.spartanEdge' has no attribute 'EdgeHTMLRootContainer' ERROR - scriptHandler.executeScript (10:13:16.177) - MainThread (12244): error executing script: <bound method WordDocument.script_toggleAlignment of <NVDAObjects.Dynamic_OutlookUIAWordDocumentWordDocumentEditableTextWithAutoSelectDetectionUIAWindowNVDAObject object at 0x075DFE30>> with gesture 'ctrl+r' Traceback (most recent call last): File "scriptHandler.pyc", line 208, in executeScript File "NVDAObjects\window\winword.pyc", line 1295, in script_toggleAlignment File "NVDAObjects\window\winword.pyc", line 1240, in _WaitForValueChangeForAction File "NVDAObjects\window\winword.pyc", line 1295, in <lambda> File "monkeyPatches\comtypesMonkeyPatches.pyc", line 86, in new__getattr__ File "comtypes\client\lazybind.pyc", line 168, in __getattr__ File "comtypes\automation.pyc", line 729, in _invoke File "monkeyPatches\comtypesMonkeyPatches.pyc", line 30, in __call__ _ctypes.COMError: (-2146822463, None, ('Object has been deleted.', 'Microsoft Word', 'wdmain11.chm', 25305, None))
-- Quentin Christensen
Training and Support Manager
|
|
|
Re: Sometimes NVDA only reads first line of an email in Outlook 2019
Chris Smart
I either do Say All, or I just arrow up and down as needed.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rosemarie Chavarria
Sent: December 1, 2021 3:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Sometimes NVDA only reads first line of an email in Outlook 2019 When I used to use outlook 2013, I used the say all command to read messages. I don’t know of a way to get NVDA to read out messages automatically. Sent from Mail for Windows Sometimes NVDA only reads the first line of an email in Outlook 2019 desktop but sometimes the same email will be read entirely. I use down arrow to select the email to read and then hit ENTER to bring up the read window.
I seem to be missing something here. Does anyone know how to make NVDA read entire emails after hitting ENTER? I realize that I could use "say all" but would prefer to keep the required inputs to a minimum and to have consistency.
Thanks for this great resource!
NVDA 2021.2
Windows 10 Version 10.0.19042 Build 19042 Microsoft® Outlook® 2019 MSO (Version 2110 Build 16.0.14527.20234) 32-bit desktop version
|
|
|
Aside from the errors in the log, did you notice anything when they happened?
On Thu, Dec 2, 2021 at 2:16 AM Chris Smart < ve3rwj@...> wrote: There are a couple errors below the usual initialization messages. Log follows: INFO - __main__ (10:11:56.663) - MainThread (12244): Starting NVDA version 2021.3rc1 INFO - core.main (10:11:56.898) - MainThread (12244): Config dir: C:\Users\Chris\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (10:11:56.898) - MainThread (12244): Loading config: C:\Users\Chris\AppData\Roaming\nvda\nvda.ini INFO - core.main (10:11:57.041) - MainThread (12244): Windows version: Windows 10 21H2 (10.0.19044) workstation INFO - core.main (10:11:57.041) - MainThread (12244): Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)] INFO - core.main (10:11:57.041) - MainThread (12244): Using comtypes version 1.1.8 INFO - core.main (10:11:57.041) - MainThread (12244): Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (10:11:57.681) - MainThread (12244): Loaded synthDriver eloquence INFO - core.main (10:11:57.681) - MainThread (12244): Using wx version 4.1.1 msw (phoenix) wxWidgets 3.1.5 with six version 1.16.0 INFO - brailleInput.initialize (10:11:57.681) - MainThread (12244): Braille input initialized INFO - braille.initialize (10:11:57.681) - MainThread (12244): Using liblouis version 3.19.0 INFO - braille.initialize (10:11:57.681) - MainThread (12244): Using pySerial version 3.5 INFO - braille.BrailleHandler.setDisplayByName (10:11:57.691) - MainThread (12244): Loaded braille display driver noBraille, current display has 0 cells. INFO - core.main (10:11:57.811) - MainThread (12244): Java Access Bridge support initialized INFO - _UIAHandler.UIAHandler.MTAThreadFunc (10:11:57.871) - _UIAHandler.UIAHandler.MTAThread (12912): UIAutomation: IUIAutomation6 INFO - core.main (10:11:58.066) - MainThread (12244): NVDA initialized ERROR - eventHandler.executeEvent (10:12:28.205) - MainThread (12244): error executing event: UIA_controllerFor on <NVDAObjects.Dynamic_StartMenuSearchFieldSearchFieldEditableTextWithAutoSelectDetectionUIA object at 0x03B517B0> with extra args of {} Traceback (most recent call last): File "eventHandler.pyc", line 284, in executeEvent File "eventHandler.pyc", line 98, in __init__ File "eventHandler.pyc", line 107, in next File "NVDAObjects\UIA\__init__.pyc", line 2157, in event_UIA_controllerFor File "baseObject.pyc", line 42, in __get__ File "baseObject.pyc", line 146, in _getPropertyViaCache File "NVDAObjects\UIA\__init__.pyc", line 1935, in _get_controllerFor File "NVDAObjects\__init__.pyc", line 92, in __call__ File "NVDAObjects\UIA\__init__.pyc", line 1017, in findOverlayClasses AttributeError: module 'NVDAObjects.UIA.spartanEdge' has no attribute 'EdgeHTMLRootContainer' ERROR - scriptHandler.executeScript (10:13:16.177) - MainThread (12244): error executing script: <bound method WordDocument.script_toggleAlignment of <NVDAObjects.Dynamic_OutlookUIAWordDocumentWordDocumentEditableTextWithAutoSelectDetectionUIAWindowNVDAObject object at 0x075DFE30>> with gesture 'ctrl+r' Traceback (most recent call last): File "scriptHandler.pyc", line 208, in executeScript File "NVDAObjects\window\winword.pyc", line 1295, in script_toggleAlignment File "NVDAObjects\window\winword.pyc", line 1240, in _WaitForValueChangeForAction File "NVDAObjects\window\winword.pyc", line 1295, in <lambda> File "monkeyPatches\comtypesMonkeyPatches.pyc", line 86, in new__getattr__ File "comtypes\client\lazybind.pyc", line 168, in __getattr__ File "comtypes\automation.pyc", line 729, in _invoke File "monkeyPatches\comtypesMonkeyPatches.pyc", line 30, in __call__ _ctypes.COMError: (-2146822463, None, ('Object has been deleted.', 'Microsoft Word', 'wdmain11.chm', 25305, None))
-- Quentin Christensen
Training and Support Manager
|
|
|
