Larynx voice not working

Help
1

I’m looking to setup a more natural sounding voice for Rhasspy and I’ve read and heard that Larynx is pretty decent.

When I selected Larynx in Rhasspy and hit save I got a request to download which I said ‘yes’ to.
Now after restart I get a Timeout.
In the log I see

[ERROR:2021-11-15 11:25:59,285] rhasspyserver_hermes:
Traceback (most recent call last):
File “/usr/lib/rhasspy/.venv/lib/python3.7/site-packages/quart/app.py”, line 1821, in full_dispatch_request
result = await self.dispatch_request(request_context)
File “/usr/lib/rhasspy/.venv/lib/python3.7/site-packages/quart/app.py”, line 1869, in dispatch_request
return await handler(**request_.view_args)
File “/usr/lib/rhasspy/rhasspy-server-hermes/rhasspyserver_hermes/main.py”, line 1716, in api_tts_voices
voices = await core.get_voices()
File “/usr/lib/rhasspy/rhasspy-server-hermes/rhasspyserver_hermes/init.py”, line 940, in get_voices
handle_finished(), messages, message_types
File “/usr/lib/rhasspy/rhasspy-server-hermes/rhasspyserver_hermes/init.py”, line 995, in publish_wait
result_awaitable, timeout=timeout_seconds
File “/usr/local/lib/python3.7/asyncio/tasks.py”, line 449, in wait_for
raise futures.TimeoutError()
concurrent.futures._base.TimeoutError
[DEBUG:2021-11-15 11:25:29,823] rhasspyserver_hermes: Handling AudioDevices (topic=rhasspy/audioServer/devices, id=1ca17c60-9c16-4804-9402-00f82e2960d0)
[DEBUG:2021-11-15 11:25:29,704] rhasspyserver_hermes: Publishing 102 bytes(s) to rhasspy/audioServer/getDevices
[DEBUG:2021-11-15 11:25:29,703] rhasspyserver_hermes: → AudioGetDevices(modes=[<AudioDeviceMode.INPUT: ‘input’>], site_id=‘default’, id=‘1b2f0553-db6c-4873-ad72-a8c76ce238f8’, test=False)
[DEBUG:2021-11-15 11:25:29,670] rhasspyserver_hermes: Handling AudioDevices (topic=rhasspy/audioServer/devices, id=0299c052-2fac-4a7f-8368-fe6fcc744595)

I am running Rhasspy 2.5.11 on a Pi 3B+ with a ReSpeaker 2 hat.
I can use NanoTTS without any issue.

2

I had similar errors at one point and it was the MQTT setup that was wrong, so try to check that.

3

I’m using websockets for my Rhasspy to Node-Red connection.

4

Hmm, I think I recall something about Larynx requiring AVX extensions on the CPU to work correctly.
I think that was why I chose an old laptop as a server instead of a new RPi4.

5

Looks like you are correct (https://github.com/rhasspy/rhasspy/issues/150)

Guess the warning on the settings page never made it to/or past Rhasspy 2.5.10