Choose the sources your scene needs
Chat, OBS alerts and TTS have separate overlay URLs. Add the features you want as separate Browser sources so you can position chat and notifications independently and check their audio. CrewJoke controls styling; OBS controls the source dimensions and position.
For two linked platforms, use the shared dashboard URLs. Select message or event sources within each feature’s settings rather than generating another set of links for every platform. With one connected channel, settings use that channel’s data without an extra selection step.
Example: a gaming scene with chat and speech
Copy the chat widget URL, create a Browser source and position it in a free part of the frame. Then add a separate TTS source. Send an ordinary message, check its text and confirm that speech is audible in the mixer.
Add alerts after that and send a test. Checking one source at a time makes it easier to find the problem when text appears but audio is silent.
Checks before going live
Check every scene where chat or audio should work. TTS needs an active overlay connection; the dashboard does not replace it. Offline testing depends on the channel’s speech permission and daily allowance.
Keep overlay links private. After resetting a token, paste the new URL into OBS. The same visual style can be used for both channels, but event availability and feature restrictions still depend on the source platform.
The default limit is 100 spoken messages per day. Get 50 more by following the news through the CrewJoke Telegram bot. The bonus lasts while subscribed. Discuss a higher limit through the channel’s direct messages.
Get +50 in the bot