What you will be able to doYou can distinguish the picture path from the control path and choose the setup your platform supports.
Before you start
- Your streaming software and the source type it accepts.
- The supported Windows desktop setup if using iTok Camera.
Three separate jobs
- A browser overlay displays the picture from a private iTok source URL.
- iTok Camera on the supported Windows setup provides a composed camera/video path.
- An OBS control connection can run supported actions such as changing a scene or source visibility.
Prepare the camera path
Follow the desktop Camera and Source setup controls for the installed version. Confirm the selected camera, permissions and composition. Check the final size and crop in the streaming software rather than assuming the editor preview is the output capture.
Keep audio capture separate. A camera feed does not by itself prove that TTS, soundboard or music reaches viewers. The Windows path does not establish the same native feature on Mac or Linux.
Choose the correct OBS control path
The Windows desktop Connect OBS controls provide native connection status and scene switching. That path is separate from the local companion’s event-triggered targets.
For event-triggered scene or source-visibility responses, pair the companion and configure the corresponding target in Action connections. Read its availability before saving a rule. Test deliberately and observe OBS itself; a queued command is not proof of execution. Keep a manual route to your scene if the control connection is unavailable.
Check the failed path, not every connection
If only the camera picture is missing, check camera selection, permissions and capture. If only an OBS action fails, inspect the control connection and target. If the overlay is current but the public stream is delayed, measure the broadcast path separately.
Do not clear working scenes or restart an active broadcast just to diagnose a control label. Record the affected stage and its error, then follow that stage’s setup guide.