Skip to content

SE.Live troubleshooting

Start with the steps for your symptom. The SE.Live troubleshooting article includes screenshots and further diagnostics.

Open StreamElements → SE.Live Docks. If docks remain missing, use StreamElements → Logout, then sign in again. A canvas dock may be behind another panel; select it from the StreamElements menu.

Retry with Google Chrome. If a VPN or browser extension blocks login, temporarily pause it and retry, then restore it.

Can’t log in with an X (Twitter) account

Section titled “Can’t log in with an X (Twitter) account”

Remove two-factor authentication from your X account, then log in to SE.Live again.

The SE.Live Stream Deck plugin is sensitive to OBS’s install path. Install OBS to its default location to avoid the plugin not being recognized.

  1. Copy the overlay URL again from My Overlays → three-dot menu → Copy URL and paste it into the browser source’s Properties.
  2. Match the source dimensions to the overlay.
  3. Check that alerts are not paused or muted in the Activity Feed.

For stuttering, try changing Settings → Advanced → Enable Browser Source Hardware Acceleration. Restart OBS after changing this setting.

If you hear an alert but cannot see it, move its browser source above sources covering it.

Not hearing alerts at all? First confirm your audio device works outside OBS (Discord, Spotify, etc.), then check Settings → Audio: set your main output as Desktop Audio, and your microphone as Mic/Auxiliary Audio. Layer order also matters — an alert overlay’s browser source needs to sit above other sources, or you may hear the alert without seeing it.

Changing the alert volume:

  1. Open the browser source’s Properties and enable Control audio via OBS.
  2. Adjust its volume in the OBS mixer.
  3. To hear it locally, open Advanced Audio Properties and set its monitoring to Monitor and Output.

Check your audio routing if this produces duplicate sound. Still stuck? The OBS Discord covers general OBS audio routing questions.

Update OBS to its latest stable release, then reinstall SE.Live.

Update OBS and SE.Live, then temporarily disable other plugins and retry. Complete the BugSplat report if it appears — it sends a diagnosis report to StreamElements automatically.

If crashes persist, add --setrace to your OBS shortcut’s target field (right-click the shortcut → Properties) before reproducing the crash, then share both the resulting trace and your regular crash logs when you contact support.

If OBS hangs without producing a crash log (Windows, requires OBS 31.x+): reproduce the hang without closing OBS, open Task Manager (Ctrl+Shift+Esc → Details), right-click obs64.exe, and select Create memory dump file. If this fails, retry Task Manager as Administrator, and only create one dump at a time.

See Uninstalling SE.Live for the full removal steps, including how to back up your OBS profile first.

Check the combined bitrate of your multistreaming outputs. Also check for unused Backtrack buffers, which consume encoding resources even while idle.

If your stream lags or drops frames when streaming to multiple platforms at once, switch to GPU encoding — CPU encoding struggles once you’re sending three or more simultaneous outputs.

Use the OBS guide that matches the problem:

When asking for help, include:

  • Your OBS and SE.Live versions.
  • OBS logs and any crash logs from the Help menu.
  • What you were doing when the problem started.
  • The exact error message, if there is one.
  • Whether the problem happens every time.

Use the support request form to contact support. Remove stream keys and private overlay URLs from screenshots before sharing them.