-
Notifications
You must be signed in to change notification settings - Fork 24
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
[Request] New features to Text To Speech #1176
Comments
Work is ongoing to improve the tts engine right now. Looking over the list of ideas the ideal way to do this would be to try and keep it as simple as possible which is try because we shouldn't bury the settings like Twitch does right now. I have a few questions though as I am trying to understand each feature.
|
Sorry. It was my fault. I didn't explain extensively the ideas I've posted.
"dice" means "says" in Spanish. It was just an example. What I wanted to suggest was what the TTS reads should be customizable with variables/placeholders. Maybe someone doesn't want any word to be TTS'ed between the username and the message ([username] [message]) or maybe someone wants more than a word like "has commented" between the username and the message ([username] has commented [message]) or maybe only wants the message to be TTS'ed ([message]).
Didn't know that you could long press and do moderation tasks. With that method the only way to mute an account from a TTS is when that account already chatted. If you could write the accounts you want to be ignored by TTS you could anticipate to it.
As there is no visual indication on chat that a user has been TTS muted maybe a list of TTS muted accounts will be great or else the same applies from previous point as you will need that account to chat to check if is TTS muted or not or to unmute it.
Yes. You could ignore all commands starting with "!" like !youtube !instagram !uptime .... but allow !hello command. Or vice versa. You could allow all commands starting with "!" like !hello !bye .... but ignore !youtube !instagram
Are considerations of the bulletin points. That was a brief explanation of what I wrote now on the above lines. |
*Ignore command prefix and ignore selected commands I think it shouldn't be both at same time so user must choose one or other option. The same goes to allow command prefix and allow selected commands.
**Allow selected commands should have priority over ignore command prefix. ie:
Allow selected commands: !tts [message]
Ignore command prefix: !
Should read the !tts message instead ignore it.
The text was updated successfully, but these errors were encountered: