Text to speech speaks and describes emojis in messages incorrectly.

[diegoveloper]

I was viewing the chat comments, and when they sent a YouTube emoji, the bot described it with multiple words. The biggest problem was on TikTok, when they sent an animated image, I think, and the bot started describing it in base 64, which became infinite. I have two questions:

• How do I stop the bot from speaking and describing emojis/images?
• How do I stop the bot from speaking (is there any button for that)?

[steveseguin]

I thought I was stripping images and emojis from the TTS engine, so I'm a bit surprised to hear this.

There is a speaker-icon in the menu bar, that will generally let you stop the TTS; it turns red when the TTS is speaking, and you can press it to stop it, assuming you have the dock open. Other pages may not have a button to stop it, however it will not TTS by default -- you have to enable TTS.

Can you provide more details over your links, url parameters, which overlay you are using issues with, etc?

[diegoveloper]

Yeah, I have this URL: https://socialstream.ninja/featured.html?session=[key]&showtime=30000&tts=es-ES&latency=0&pitch=0.4&ttsclicked&ttsnewmembers&ttsdonos&showsource&speech&voice=jorge&server&server2&server3

I received a TikTok message and wanted the bot to reproduce it. I clicked on it, and then the bot started talking, but I heard it say 'base64' at the beginning of the image. I also noticed the same thing with YouTube emojis, the bot just described the emoji.

This is the dock I have, could I stop the bot talking with any of these controls?

[steveseguin]

I pushed an update to beta so the featured overlay no longer tries to “read” emojis, stickers, or base64 blobs—those simply get skipped now, so you won’t hear the endless data dump again.

Stopping TTS when you don’t want it:

• Dock page – The speaker icon (turns red while speaking) still works. Click it once to silence the current read-out and leave TTS off until you toggle it back on.
• Featured page – There’s no button, so use one of these options:
  • Append ?notts=1 (or &notts=1 if you already have query params) to the overlay URL, then reload it. As long as that flag is present, TTS stays off.
  • If you control the overlay via the remote socket/API, send {"action":"toggleTTS","value":"off"} to stop speech immediately. Use value:"on" or remove the notts flag when you want it back.

Let me know if anything still sounds off, but this should keep the bot quiet unless there’s real text to read.

[diegoveloper]

Any chance to move this into the master/main branch? I tested and it worked