How to enable chat reading on TikTok LIVE? TTS in Thunderstream step by step

Before you choose your voice: check the message path

Open the live stream and ask the viewer for a new, regular comment. If the entry is not in Thunderstream, first check the correct account connection. Changing your voice tone will not fix missing chat data.

If you have several platforms, do a separate test on each of them. Please check the platform ID on your entry so that a message from Twitch is not taken as confirmation that YouTube is working. Old history comments do not replace a new test.

A dictionary without difficult abbreviations

Step by step · 1–4

1. Action

   Send a short sentence without a command or an emoji.

   ✓ After this step you will see

   The new comment is visible in Thunderstream.

2. Action

   Open Lektor TTS and expand Lektor AI.

   ✓ After this step you will see

   You see the reading and voice tester settings.

3. Action

   Turn on reading and select the language, e.g. Polish.

   ✓ After this step you will see

   The test is for a specific language, not a random voice.

4. Action

   Select available engine and voice.

   ✓ After this step you will see

   The list corresponds to the capabilities of the device or configured provider.

Enlarge the screenshot ↗

Step by step · 5–8

5. Action

   Start with a slow tempo of around 1× and a moderate volume.

   ✓ After this step you will see

   The short test is self-explanatory.

6. Action

   Select playback in panel or chat overlay.

   ✓ After this step you will see

   You know which place actually emits the speech.

7. Action

   First, set the template {message}.

   ✓ After this step you will see

   The content itself is read; then you can add {username}.

8. Action

   Write down and listen to a short sentence from the tester.

   ✓ After this step you will see

   You check the voice and playback device.

Step by step · 9–12

9. Action

   In TTS Moderation, review roles, length, replays and prohibited words.

   ✓ After this step you will see

   You know what is deliberately left out.

10. Action

    Check how to ignore symbols in nicknames and emojis.

    ✓ After this step you will see

    Unwanted markings do not interfere with speech.

11. Action

    Send a new comment and check the TTS log.

    ✓ After this step you will see

    You see the status of the entry: waiting, reading or skipping.

12. Action

    Go to another panel tab and submit another comment.

    ✓ After this step you will see

    The enabled voice-over still supports approved text.

Enlarge the screenshot ↗

Step by step · 13–14

13. Action

    Record the test with a microphone.

    ✓ After this step you will see

    The voice is heard once and does not drown out the conversation.

14. Action

    Repeat the test separately on each platform.

    ✓ After this step you will see

    The Twitch read is not the only confirmation for the remaining chats.

An example you can reproduce

"Voice test number one" from the tester checks the synthesis and device. “Chat test number two” with LIVE additionally checks message reception and filters. If the tester is working and the second sentence is not in the log, changing the volume will not fix the input problem.

Turn on the voice-over and set a calm starting point

For your first try, choose a simple sentence, such as "Hi, we're checking the chat reading." This will make it easier to distinguish a configuration error from an intentional omission of an emoji, command or illegal word.

1. Open Lektor TTS, turn on the tool and select the reading language. For Polish messages, start with a Polish voice.
2. Select an available voice, set a moderate speed and volume, and then run the test. The names and availability of voices depend on the selected synthesis method and device.
3. Set a statement template: just a message or a nickname and a message. Check whether the inserted text actually corresponds to what you want to hear.
4. Save your settings. After switching the voice, test the short text again with Polish characters and your username.

Filters: readable chat without reading all spam

1. In Moderation TTS, view blocked words and settings for skipping unwanted messages.
2. Check how to ignore emojis and symbols in nicknames. The underscore in the username does not have to be pronounced.
3. Adjust length, replay and eligible viewers limits. Set mild rules first, then tighten them based on real chat.
4. Check the comment with the emoji, the repeated entry and the command separately. Compare the result with the settings and reading log.

Queue and delay: Not every message has to wait forever

Reading takes longer than writing a short comment. If there is a lot of text coming in, even a properly functioning voice can lag behind. Reduce the maximum message length and check the queue limit and age limit for posts.

Too large a queue means reading a long-ended conversation. Too small and you may miss part of the message during an intense moment. Match the values ​​to the pace of your community, not how many items fit into the panel.

Audio and double reading

Choose one place to actually play the speech. If you use a readout in a panel or program, capture this sound for transmission. If you have selected a chat overlay, please check the correct source and its audio track.

Don't run a second independent copy of the voiceover in another tab just to see the preview. The phone can remain silent while the computer reads. Dual audio can also result from capturing the same program with a separate source and desktop audio simultaneously.

Final test and work outside the TTS tab

1. Start a short local recording and submit a new comment from your platform of choice.
2. Navigate to another tool in the panel. An enabled voice-over should continue to support permitted messages as long as the panel or program playing it is running.
3. Play the recording: the voice should be understandable, audible once and not drown out the microphone.
4. If you report a bug, please include the time, platform, and log entry status. Do not send tokens or private overlay links.

What do you see on the screen and how to fix it

Fix one thing at a time and try the same thing again. If you change several options at the same time, it will be difficult to determine what solved the problem. Don't delete a working source or entire configuration just because one widget isn't responding.

If you still need help, write down the program name and version, platform, approximate time of trial, expected result, and what actually happened. Attach a dump without passwords, keys and full private links. This description is much more useful than just the "not working" message.

Last attempt before use on LIVE

1. Save the changes using the button assigned to the edited function. If there are separate forms, check each changed part separately.
2. Open the settings again and compare the most important values. Simply moving the slider does not always mean a permanent save.
3. Check the result outside the editor itself: on the target scene, in the recording, or in the reopened configuration.
4. If the function uses the platform, separately acknowledge the new handled event during the active LIVE. Don't expect the appearance test to confirm account authorization.
5. Save the working values ​​and make a copy before the next major change. Next time you start up, start with a quick check.

Frequently asked questions