Read Comments (TTS)
Read Comments has Google Voice read your viewers' comments aloud, so you can keep interacting without watching the chat the whole time.
What is Read Comments
The Read Text (TTS) action in the Interaction Center reads a specific text when something triggers it. This feature is different: it reads viewers' comments as they are, continuously, for as long as the live runs.
This works differently from other IndoFinity features, and it is behind the most common complaint: "I can hear the TTS on my PC but my viewers can't."
Read Comments doesn't use a Browser Source. The sound plays directly from the app.indofinity.com dashboard tab, or from the desktop app if you use it.
For viewers to hear it, the browser or desktop app audio has to be captured in OBS, either through Desktop Audio or through an Application Audio Capture pointed at the browser or the IndoFinity app.
Before you start
Your TikTok Live has to be connected. The dashboard tab also has to stay open. If you close it, nothing gets read.
Setup steps
1. Turn it on and set up the voice
In the Settings section:
| Setting | What it does |
|---|---|
| Enabled | Turns the feature on |
| Language | The Google voice language |
| Speed | Speaking speed |
| Pitch | How high or low the voice is |
| Volume | Voice volume |
| Random Voice | Switches between voices at random instead of using one voice the whole time |
The Tester section plays a sample with the current settings. Use it to get the voice right before you go live.
2. Choose who gets read
In the Who can use? section, pick at least one target. There are two extra filters:
| Setting | What it does |
|---|---|
| Minimum Team Level | Only team members at a certain level or above |
| Minimum Top Gifter | Only viewers in the top gifter ranking |
If no target is selected, you'll see "Please select at least 1." and no comments are read.
On a busy live, reading every comment means voices pile up nonstop. Limiting it to top gifters turns TTS into a perk viewers notice, and the live stays pleasant to listen to.
3. Choose which comments get read
In the What type of comments will be read? section:
| Option | Behavior |
|---|---|
| All Comments | Every comment that passes the target |
| Comments starting with a dot (.) | Only comments that start with . |
| Comments starting with a slash (/) | Only comments that start with / |
| Comments starting with specified words | Only comments that start with a word you've listed |
With All Comments, ordinary chat gets read too. With a prefix such as ., viewers decide for themselves what they want read aloud, and regular chat stays quiet.
4. Set the Template
The Template sets how the spoken sentence is put together.
{comment} by {username}
{comment}If it doesn't, the dashboard refuses to save it: "Template must contain {comment} for Google TTS to read comments." Without it, none of the comment text gets read.
Other useful variables are {username} and {nickname}. See Message Variables.
Word filter
The Word Filter section stops certain comments from being read. Enter the words separated by spaces, then click Save Words.
Comments that contain any of those words aren't read at all.
TTS reads whatever viewers type, out loud, to your whole audience. A filter list prepared in advance is much better than adding words after something has already been read out.
Special User
The Special User section sets a voice per person, or stops specific people from being read at all.
Each entry has Username, Allowed, Language, Random Voice, Speed, and Pitch.
It has two main uses: giving moderators or loyal viewers a voice of their own, and silencing people who abuse TTS without turning the feature off for everyone.
Common problems
Symptom: I can hear the TTS on my PC but my viewers can't. The browser or desktop app audio isn't being captured in OBS. See the warning near the top of this page.
Symptom: no comments are read at all.
Check in this order: Enabled is on · at least one target is selected · the comment type fits (if you set the . prefix, regular comments are ignored) · the dashboard tab is open.
Symptom: some people never get read. Check Minimum Team Level and Minimum Top Gifter, since both filter without telling you. Also check the Special User list, because that person may be set to not Allowed.
Symptom: comments get skipped on a busy live. The TTS queue is full. Tighten the target or use a prefix so fewer comments go into the queue.
See also
- Message Variables
- Interactions, for TTS triggered by gifts rather than comments