Late frames detected
14.29% of your frames are late. This means the frames are being generated later than they were needed, causing your stream FPS to drop. Late frames are often caused by slow sources such as monitor capture, slow video capture devices or by trying to run your stream at too high of a resolution / FPS.
If you are using a webcam, try to lower the resolution of it. If you are using monitor capture, try switching to game source or window capture. If you must use monitor capture, ensure Aero is disabled.
You can also try lowering the resolution or FPS of your stream if you have an older CPU.
See
https://obsproject.com/forum/thread...ing-too-long-to-encode-read-this-first.23334/ for more information on how to resolve this issue.
Skipped frames detected
The video encoder is unable to encode your frames in realtime, causing skipped frames (the video output will appear frozen). This is often caused by running at too high of a resolution / FPS combination for your CPU. Try lowering your resolution and/or FPS. If you have changed the x264 preset, put it back to default (veryfast).
See
https://obsproject.com/forum/thread...ing-too-long-to-encode-read-this-first.23334/ for more details on how to fix this problem.
Wireless detected
You appear to be streaming over a wireless connection. While this can be OK, keep in mind that interference from other radio sources or obstacles can cause your connection to momentarily stall, resulting in dropped frames or disconnects. A wired connection is strongly recommended for a reliable stream.
Possible slow server
The server you are streaming to (rtmp://live.twitch.tv/app) took 637 ms to connect. This may mean your connection or the server is slow, or the server is far away from you. If you are using twitch.tv, you may want to try using
JTVPing to find an optimal server.
Slower preset in use
You have changed the default preset to faster. Using slower presets can result in late frames and high CPU usage / low FPS. You should only change the preset if you are sure you have the CPU power to spare.
Bad server selected
The server you are streaming to (rtmp://live.twitch.tv/app) took a very long time to connect. This could be due to a poor connection, server problems or streaming to a server that is a long distance away from you. Streaming to servers that are closer to you often results in the best results. If you are using twitch.tv, try using
JTVPing to find an optimal server.
Dropped frames detected
40% of your frames were dropped due to poor network conditions. Frames are dropped when data can not be sent fast enough to the server you have selected. This is caused by trying to stream at too high of a bitrate, or by the streaming server you selected not being able to accept the data at the rate you are sending.
Try switching servers, especially if you are using twitch.tv. As a test, you could also try streaming to a different provider to check whether the problem is on your end or not.
Note that some ISPs will temporarily increase your upload speed at the start of a transfer - if you only start to drop frames after 30 - 60 seconds, your ISP is likely doing this and you will need to use a lower bitrate.
Finally, if you are using a wireless connection, keep in mind that interference from other radio sources can cause your connection to stutter and drop frames. A wired connection is strongly recommended when streaming.
See
https://obsproject.com/forum/viewtopic.php?f=5&t=8870 for more advice on how to fix dropped frames.
Connection stalls detected
Your connection is stalling while sending data. This can result in frame drops, stream freezes and disconnects. Try changing the server you are streaming to, or lowering your bitrate
8 issues found (5 major, 3 minor).
