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
but I'm unable to understand if this is a bug, or something missing or whatever.
So: really sorry if this post may be inappropriate.
If this is inappropriate, please consider this post null.
What are the steps to reproduce?
After a button click on ui or event, I passed in msg.payload the text to reproduce by TTS to AudioOut node.
Please note tha inside msg there's the socketid, and its value is correct.
What happens?
if I've got 2/3 computers connected, I noticed that every one play the same audio.
What do you expect to happen?
if there is on msg the socketid valorized, the audio should be played only on correct client (in my example the same that press the button,or definitely plays the "action")
Please tell us about your environment:
Node-RED-Dashboard version: 3.4.0
Node-RED version: 3.0.2
node.js version:
npm version:
Platform/OS: Linux(docker container)
Browser: Chrome.
The text was updated successfully, but these errors were encountered:
"DiscIaimer": I post previously on nodered forum, here:
https://discourse.nodered.org/t/dashboard-ui-audiout-is-it-possible-play-tts-only-on-specific-socketid-client/78637
but I'm unable to understand if this is a bug, or something missing or whatever.
So: really sorry if this post may be inappropriate.
If this is inappropriate, please consider this post null.
What are the steps to reproduce?
After a button click on ui or event, I passed in msg.payload the text to reproduce by TTS to AudioOut node.
Please note tha inside msg there's the socketid, and its value is correct.
What happens?
if I've got 2/3 computers connected, I noticed that every one play the same audio.
What do you expect to happen?
if there is on msg the socketid valorized, the audio should be played only on correct client (in my example the same that press the button,or definitely plays the "action")
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: