nvda2speechd, let Windows programs talk through Speech dispatcher
Linux for blind general discussion
blinux-list at redhat.com
Wed Jun 8 18:37:43 UTC 2022
while I get this up and running, a part of the nvda2speechd is an
application called testclient.
You can compile it using cargo build --release -q, or use this binary:
this application works as a terminal client to the server. You launch
it, and type command "speakText some text".
If you hear the server speak, the connection works.
You can quit using the quit command.
This should tell you, whether nvda2speechd server is working correctly.
If no, we need to search the problem there, if yes, there is a problem
with the library or application.
Whether SAPI installation is needed or not depends largely on how is the
app programmed. Honestly, I didn't test out with a clear wine
installation, so I can't tell which variant is to be expected, it's also
possible that the app crashes exactly because of missing SAPI, since
usually programmers expect it to be at least present, even if not used.
Dňa 8. 6. 2022 o 16:09 Linux for blind general discussion napísal(a):
> Boot the ISO and hit down once then enter, it should come up talking
> If not, systemctl enable --startnow espeakup
> I'm trying to work out why I'm getting a lot of things about SAPI, and
> if I need voices installed because I am going from a completely standard
> wine installation on a 64bit machine, yet it's flooding my terminal with
> a ton of voice list things about SAPI however so I'm unsure.
> Do I need to install under wine the speechsdk and things or should
> nvda2speechd take care of that. It's establishing a connection, but...no
> On 6/8/22 13:44, Linux for blind general discussion wrote:
>> I saw your issue on Github, will be getting to it soon.
>> Right now, I'm trying to figure out how to boot up Archlinux into the
>> accessible mode in quickemu, so I can get at least a similar environment.
>> Best regards
>> Dňa 7. 6. 2022 o 15:02 Linux for blind general discussion napísal(a):
>>> As said on the Github page. I'm running this under Arch and get no
>>> output at all.
>>> what I do
>>> 1. Download Windows exe and extract it
>>> 2. Grab the server/client and rename/replace nvdaControllerxx.dll
>>> where xx is 32 or 64
>>> 3. start the server with ./nvda2speechd in its folder
>>> 4. wine windowsexe.exe
>>> I get a connection has been established on the tab with the
>>> nvda2speechd running, and no speech from the program at all however,
>>> and a boatload of WINE Sapi errors, it seems* to me like it's looking
>>> for the SAPI stuff
>>> Am I missing someething super super obvious here or?
>>> On 05/06/2022, Linux for blind general discussion
>>> <blinux-list at redhat.com> wrote:
>>>> I avoid GUI apps in general and I think the last time I used Wine
>>>> might have been years before I went blind, but this still sounds like
>>>> a significant step forward for the accessibility of non-native
>>>> software, and surprisingly elegant to boot.
>>>> Blinux-list mailing list
>>>> Blinux-list at redhat.com
>>> Blinux-list mailing list
>>> Blinux-list at redhat.com
>> Blinux-list mailing list
>> Blinux-list at redhat.com
> Blinux-list mailing list
> Blinux-list at redhat.com
More information about the Blinux-list