-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--tts-stop-command runs at beginning of tts, not end #92
Comments
Actually, it is fired when response finished being sent from server, not necessarily being played. I have the exact same use case as you and that's why I implemented it. :) |
I've played around with the new DEBUG:root:Wake word detected
DEBUG:root:Running ['/data/satellite/commands/detection']
DEBUG:root:Muting microphone for 0.5381859410430839 second(s)
DEBUG:root:Connected to snd service
Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono # awake wav
DEBUG:root:Unmuted microphone
DEBUG:root:Running ['/data/satellite/commands/tts_played'] # wrong trigger
DEBUG:root:Running ['/data/satellite/commands/stt_stop']
DEBUG:root:Event(type='transcript', data={'text': 'test'}, payload=None)
DEBUG:root:Running ['/data/satellite/commands/transcript']
INFO:root:Streaming audio
DEBUG:root:Connected to snd service
Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono # tts wav
DEBUG:root:Event(type='synthesize', data={'text': 'test', 'voice': {'name': 'de_DE-thorsten-low'}}, payload=None)
DEBUG:root:Running ['/data/satellite/commands/tts_start']
DEBUG:root:Running ['/data/satellite/commands/detect']
DEBUG:root:Running ['/data/satellite/commands/tts_played'] # wrong trigger
DEBUG:root:Connected to snd service
Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono # done wav
DEBUG:root:Running ['/data/satellite/commands/tts_played'] |
I'm looking at it. Can you please post your |
My |
Yeah, I confirm the bug... Trying to find a solution without modifying the wyoming events... |
I submitted the correction, shall be merged soon by synesthesiam. The played event won't be fired anymore for the wav plays. Thanks for pointing this out. |
Great, I will test and report when it is puplished. Thanks you! |
I'm having the same problem, every time a wav played on the satellite system the tts-played-command is fired. config:
logs:
|
ok this fixes it: |
The
--tts-stop-command
implies that it won't run until the TTS response from the server is returned and fully spoken, but that is not what I am seeing. I have aduck
script that runs from--detection-command
that mutes two Snapcast clients I have in the same room on different Pis, and anunduck
script that runs on--tts-stop-command
and--error-command
. What I am seeing is that when detection starts, the audio on the other snapcast clients properly mute, but as soon as it's done listening to me, it immediately calls theunduck
script and unmutes the snapcast clients, and then begins speaking so the TTS reponse is playing while the music is also playing.Shouldn't
--tts-stop-command
only run after the response is finished playing?Here's my
ExecStart=
from thewyoming-satellite.service
file.and my
duck
andunduck
acripts.The text was updated successfully, but these errors were encountered: