uezo / aiavatarkit Goto Github PK

Thanks for your awesome work.

I meet a mismatch of wave file input when I use Google API to do TTS. I don't know what kind of format do I need to tansfer TTS in to asyncio.create_task()

Could you please give me a hand on that?

アバターと日本語だけではなく、英語での会話も行ってみたいと考えているのですが、コードで使用しているVOICEVOXは英語が話せないと知りました。例えば、GoogleやAzureのText-to-Speechを使用するなどして組んだプログラムはお作りになっていませんか？

I can't configure voice detection threshold to VoiceRequestListener because constructor of AIAvatar doesn't take volume_threshold.

0.x is outdated😔

• Expected: neutral after duration (3.0). in this case, 15:23:33,522.
• Actual: still fun after duration

[INFO] 2023-06-04 15:23:24,887 : face: (^o^) (joy)
[INFO] 2023-06-04 15:23:26,530 : 
 腹が立ってきました。
[INFO] 2023-06-04 15:23:26,550 : face: (#｀Д´) (angry)
[INFO] 2023-06-04 15:23:28,263 : 
 悲しい出来事がありました。
[INFO] 2023-06-04 15:23:28,280 : face: (; ;) (sorrow)
[INFO] 2023-06-04 15:23:30,498 : 
 とても楽しい体験をしました。
[INFO] 2023-06-04 15:23:30,522 : face: (*^_^*) (fun)
[INFO] 2023-06-04 15:23:32,974 : Listening... (VoiceRequestListener)
[INFO] 2023-06-04 15:23:43,190 : Voice detection timeout: 10.0
[INFO] 2023-06-04 15:23:43,323 : Stopped listening (VoiceRequestListener)

Maybe this line is not executed because the task that invokes set_face ends.
https://github.com/uezo/aiavatarkit/blob/main/aiavatar/face/__init__.py#LL29C30-L29C30

There is a recurring issue where the AzureWakewordListener stops responding permanently after network disruptions, such as changing the connected network or disconnecting and reconnecting the network hardware. This issue can be consistently reproduced on macOS by changing the WiFi network or unplugging and replugging the LAN cable while the WakewordListener is active. On Windows, the listener sometimes recovers and becomes operational again after reconnection, but the behavior is not consistent.

Steps to reproduce:

1. Start the WakewordListener on a PC.
2. Change the WiFi network or disconnect and then reconnect the LAN cable.
3. Observe that the WakewordListener fails to respond on macOS and behaves inconsistently on Windows.

Expected behavior:
The WakewordListener should consistently reconnect and resume its operations across all platforms after any network change.

This issue affects the reliability of the voice assistant's responsiveness in environments with unstable or changing network conditions.