START HERE
Trigger one test alert and count both its animations and its sound. Two animations suggest duplicate alert instances or events; one animation with doubled sound suggests a second audio route. Close previews, isolate one browser source, then add monitoring and desktop capture back separately.
1. Record the difference between an event and an echo
Make a short local recording while triggering one clearly recognizable provider test. Avoid testing during a burst of real subscriptions or redemptions: several legitimate events can arrive close together.
- Two full animations: check repeated provider events or multiple loaded alert boxes.
- One animation and closely spaced sounds: suspect direct capture plus a monitored or desktop copy.
- A second sound much later: check open stream players, replay queues, and other computers or applications playing the alert.
Note whether the duplicate exists in the saved file or only in your headphones. Local monitoring can be annoying without duplicating the outgoing mix; the recording tells you which problem you actually have.
2. Remove playback outside the production source
Close alert pop-out players and provider preview tabs after the test has been queued. Mute your live stream player, including a dashboard preview. Do not mute the whole browser if it also supplies the game or interview audio you intend to capture; identify the individual player instead.
Repeat the same sample. If the recording now contains one sound, reopen the closed items one at a time until the extra route is identified. Streamlabs specifically identifies background alert playback as a cause of echo. Keep the test controlled rather than changing a source and a browser tab simultaneously.
3. Audit loaded alert boxes, including nested scenes
Look through the active scene, nested scenes, and overlays. A full overlay may already contain an AlertBox even if you also added a separate alert source. Give intentional sources recognizable names so you can tell them apart.
Temporarily leave one alert instance active and trigger the sample again. If duplication disappears, restore other visual elements without restoring their redundant AlertBoxes. StreamElements' overlay guide warns against duplicate AlertBoxes across overlays.
When reusing the same source across scenes, add the existing source or paste a reference rather than creating independent browser copies unnecessarily. A hidden browser can remain loaded; its shutdown-on-hide property controls that lifecycle. Test transitions before enabling shutdown everywhere, because restarting a page can interrupt or reset its current widget state.
4. Test direct output without the monitor return
For an alert managed through OBS, turn off its local monitoring while leaving its intended audience output enabled. Record a test. If the echo disappears, the headphones or speakers used for monitoring were probably also being captured elsewhere.
One workable design is direct browser-source audio into the audience mix, with monitoring sent to an endpoint excluded from desktop capture. Another is intentionally capturing only a monitored mix. Choose one design and document it; combining both accidentally causes the same waveform to arrive twice.
The current OBS mixer separates output mute from monitoring. Use the actual mute and monitor controls on your installation; do not assume a legacy menu label from an older tutorial still exists. If the source meters show one alert on two channels named differently, mute one route for the next recording and compare.
5. Check the event queue only after the route is clean
If two animations still appear with a single browser source and no preview playback, inspect the provider's activity or replay history. Compare event type, time, and any visible identifier. A gift event and its recipient notification may be separate event types, rather than a broken sound setting.
Record which event triggers which variation before changing provider rules. Check for a second alert service configured for the same event. Turning down one sound is not a reliable fix: it leaves two animations, timing conflicts, and potentially two future sound assets.
Prove that all intended scenes behave the same way
Test the starting, gameplay, and break scenes in sequence. Include one transition while an alert is playing and another after it finishes. Listen to the recording with the stream player and provider preview closed.
The pass condition is one intended event, one intended animation, and one sound in each required output track. If the problem returns only after a scene change, record that scene pair and inspect their shared or duplicated sources. Keep the working source in place while fixing the other scenes. Once alerts fire cleanly on a single mixer channel, you can also keep browser alerts on your livestream while excluding them from local recordings.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.