You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice, when TTS / audio actions can play in a sequence.
For example, when you add 2 or more actions from:
Speak label
Speak custom text
Play recorded audio
It will play / say only last one.
Last one in drop down menu maybe? If I put 3 actions: Speak label, Play recorded audio and Speak custom text. Only Play recorded audio is started.
On the screen I want to:
say animal name
play his sound
But the app plays only sound without saying label (animal name).
Expected behavior:
play / say first action in list
play / say second action in list
etc
Undertand, that it's primarily to make more actions together and not in sequence. But it would be nice improvement, when actions which need to play sound could be in sequence.
Add ordering for this actions would be nice benefit for that cases.
The text was updated successfully, but these errors were encountered:
I think adding more functionality to audio playback could be beneficial, as previously commented. This might be achievable with minimal complexity by managing promises to execute sequentially. I would be happy to try implementing this if the repository maintainers are interested.
It would be nice, when TTS / audio actions can play in a sequence.
For example, when you add 2 or more actions from:
It will play / say only
last one.Last one in drop down menu maybe? If I put 3 actions: Speak label, Play recorded audio and Speak custom text. Only Play recorded audio is started.
On the screen I want to:
But the app plays only sound without saying label (animal name).
Expected behavior:
Undertand, that it's primarily to make more actions together and not in sequence. But it would be nice improvement, when actions which need to play sound could be in sequence.
Add ordering for this actions would be nice benefit for that cases.
The text was updated successfully, but these errors were encountered: