Back
Русский
АнглийскийNov 9, 2026
Stream Won’t Start or Keeps Lagging? What to Check in OBS, StreamVi, and on Your Platform
You hit Start Streaming in OBS and say hello. Then someone in YouTube chat writes, “We’re still on the waiting screen.” Pull up your stream on another platform. If you can hear yourself saying hello there, part of the broadcast is already live. Leave OBS running and find out what YouTube is waiting for.
1. Find out how much of the stream is affected
Open a viewer page on another platform. In the right StreamVi project, open Home → Information and look at the incoming stream status and bitrate. Live video and sound help you distinguish the current feed from a placeholder that may stay up after a disconnect. The StreamVi guide includes a screenshot of the incoming stream panel.
What you find tells you where to look next.
- Nothing is live, and StreamVi shows no input. Check whether OBS is sending video.
- The picture freezes everywhere or bitrate keeps dipping. Open OBS Stats and watch which counter is rising.
- StreamVi shows a steady input, but nothing is live. Open Channels in StreamVi and check which outputs are enabled and whether any show an error.
- Only one channel is affected. Leave OBS and the working streams running. Check that output in StreamVi, then open the intended account and event on the platform itself.
If another platform is showing what you’re doing right now and you can hear your mic, leave that output running. If it’s on a waiting screen too, the incoming status in StreamVi tells you where to look next.
2. Check that OBS is sending the stream
Your OBS preview can look fine even when the video has stopped going out. Look at the bottom of the window for the live timer and the bitrate OBS is actually sending.
If OBS is reconnecting or stays at 0 kbps, note the time. Then confirm the active OBS profile and the selected StreamVi project. For an RTMP connection, open Home → RTMP and Key in StreamVi and Settings → Stream in OBS. With Custom selected as the service, the server and stream key should come from that StreamVi project. Both fields are shown in the OBS setup guide for StreamVi.
Found an old server address or a key from a different project? When it’s safe to interrupt the feed, enter the current values and start streaming again. Keep the key hidden and out of screenshots. If the settings match and bitrate keeps dropping during the stream, open Stats.
OBS shows a steady outgoing bitrate and StreamVi shows the incoming stream and its parameters. If OBS is sending but there’s still no input, open the Event Log in StreamVi and check the ingest server’s status.
3. Open OBS Stats
The stream is live, but viewers see freezes or jerky motion.
Open View → Stats. Say OBS lost 80 frames at the start and the number hasn’t moved since. Those 80 will still be in the total. Look for the counter that’s climbing now.
Try one change from the table, then watch that same counter again. Compare similar moments. If you were losing frames in a fight, sitting on the game menu won’t tell you much.
| Counter going up | What’s happening | First action and how to check it |
|---|---|---|
| Dropped Frames (Network) | OBS is struggling to deliver the feed to the ingest server. | Pause cloud sync or another active upload. Check whether network drops and bitrate dips stop. |
| Frames missed due to rendering lag | OBS can’t assemble the scene fast enough. A game may be taking too much GPU time. | Cap the game’s frame rate if you can do it without quitting. Check whether the rendering counter rises more slowly. |
| Skipped frames due to encoding lag | The encoder can’t compress finished frames fast enough. | During a break before a test run, lower the OBS frame rate, for example from 60 to 30 fps. Check the encoding counter on the same scene. |
If the counters are steady and only one platform stutters, open the preview in that platform’s dashboard and compare it with what plays on the viewer page. If network drops continue, compare upload speeds to StreamVi’s ingest servers between broadcasts or follow OBS’s troubleshooting steps for an unstable connection. The OBS guide has more ways to lighten the load on rendering and encoding.
4. Check the input, outputs, and event log in StreamVi
OBS is sending but StreamVi shows no input. Or the input is healthy and one channel shows an error.
On the project’s Home page, open Information for the incoming status, bitrate, and frame rate. Under Channels, check the switch and status for the affected output. In Analytics, open the broadcast and compare bitrate changes and reconnect times with the Event Log. Filter by time, server, platform, or channel. A missing data point in Analytics is different from a measured zero. Empty log? Try widening the time range or clearing the filters.
If only one channel shows an error, open that platform’s dashboard and confirm the account and event while the others keep streaming. If the input keeps disconnecting and you’ve confirmed the server address and key, look up the server on the StreamVi server status page. Between broadcasts, use the speed test under Home → RTMP and Key to compare upload performance to the available servers. If drops recur, try another ingest server in a short test with the same video settings. Changing servers means reconnecting OBS and can interrupt every output, so save it for a break if some destinations are still live.
Once the input stays up, open the viewer page. You should see live video and hear the audio. If the input is steady and one platform is still quiet, check that platform on its own.
5. Check the destination platform and account
StreamVi has video and other platforms are live, but YouTube is still waiting. Or one of two connected accounts is live and the other is missing.
Open the affected channel in StreamVi and confirm where it sends video. In the destination dashboard, check the account, page or community, live-streaming permissions, and the specific event. Say one VK community is already live and the other still shows a waiting screen. Check whether the connected account has access to the second community and which event it’s sending to. The fields vary by platform. StreamVi’s guide covers where to find each platform’s streaming settings.
The next move depends on where your viewers are waiting.
- YouTube. Open Live Control Room for the right channel in YouTube Studio and select the scheduled event. If you have a preview and auto-start is off, click Go live there. If you have no preview, read the stream health message and confirm that the event matches the one selected in StreamVi. YouTube walks through that last click in its guide to starting a scheduled stream with an encoder.
- VK. Check that the VK page or community selected in StreamVi is the one you want and that the connected account still has access. Open the specific broadcast in VK. If the dashboard shows a preview and offers a button to go live, start it there. For a separate VK Video Live connection, check your channel in VK Video Live. The VK setup guide shows where to choose a community and grant access.
- Telegram. Open the group or channel where you have permission to start a broadcast. In Start With, check that the RTMP address and key match the Telegram output in StreamVi, then start the broadcast in Telegram itself. Multichat uses a separate connection for messages. The StreamVi walkthrough shows where to find those details and where to paste them.
Open the link you shared with viewers. If you can see what’s happening live and hear the audio, the right event is up. If it still reports an error, copy the exact message so you can include it when you contact support.
6. Run a test or collect details for support
The picture is back, or the problem keeps returning after you’ve checked the settings.
Try to recreate the moment the stream started struggling. If the picture broke up in-game, load the same scene, play for a bit, and talk into the mic. On YouTube, you can test the picture and sound in a separate unlisted stream. If your broadcast is already live, check it on a phone or from another account with access while keeping the current feed running.
If it happens again, contact support from the StreamVi dashboard menu. Start with what you saw. For example, “At 7:42 p.m. the OBS bitrate dropped to zero, and we lost video on every platform.” Include the date, time and time zone, the affected platform and output, the ingest server, and the exact error message. Add the broadcast ID from Analytics if available and the project ID if needed. Attach an OBS Stats screenshot from when the issue occurred. Hide stream keys, tokens, URLs containing secrets, and login details. Mention which outputs kept working and what you’ve already checked. The StreamVi guide shows where to find the broadcast ID and error message.
Under the conditions that triggered the issue, bitrate stays steady, the affected frame counter stops rising, the error doesn’t recur, and viewers have picture and sound on every intended output. If the problem usually appears ten minutes in, let your test run past that point.
You can fine-tune your settings before the next stream. Our OBS bitrate guide for Twitch and YouTube walks through what your connection and each platform can handle.
