Add timer and donation overlays to OBS
Add Aarothon Browser Sources to OBS Studio, choose overlay dimensions and configure alert audio.
Add an output#
Open OBS in the studio, copy an output URL, then use Sources → + → Browser in OBS Studio. Paste the URL and use the suggested width and height. Copy from the running app so the host and port match. Do not use the studio settings page as an overlay.
Which URL?#
Timer: /overlay/timer. Wheel: /overlay/spinwheel. Goals: /overlay/goals, with separate /checkpoints and /progress outputs. Leaderboard: /overlay/leaderboard. Recent Events: /overlay/recent-events. Notifications: /overlay/alerts/youtube, /overlay/alerts/gank, /overlay/alerts/zypage, /overlay/alerts/streamlabs, /overlay/alerts/wescan. YouTube events received through Streamlabs still use the YouTube output; Streamlabs is for native tips.
Audio#
Enable Control audio via OBS for a notification Browser Source to route it through the OBS mixer. Check its meter, mute state and track routing. Monitoring controls what you hear locally; it is separate from what the stream receives. The OBS Browser Source guide explains these options.
Empty output or duplicate sound#
A disabled module renders transparently. An enabled Recent Events feed with no accepted events has no event rows; its title can still be present. For repeated sound, check duplicate Browser Sources and desktop audio monitoring as well as the provider’s original alert box. A preview does not require another paid donation.
Preview audio versus live audio#
In 4.2.2, Chạy preview plays sound in the Studio tab. The matching OBS output shows the preview picture but deliberately does not duplicate its audio. A silent OBS meter during this preview is expected. Real notifications play audio on their OBS output. Validate live audio routing with a supported provider test where available; do not pay for another donation just to test a chime.
Keep your report ID and tell us which step behaves differently.