Question / Help LAG
- Thread starter doge
- Start date
Narcogen
Active Member
Narcogen
Active Member
17:21:16.399: Windows Version: 10.0 Build 17134 (revision: 829; 64-bit)
Windows is out of date and a broken feature is likely reducing OBS performance. You should upate; read the link at the bottom of this post.
19:19:47.058: Output 'simple_file_output': Number of lagged frames due to rendering lag/stalls: 79057 (18.8%)
Rendering lag caused by GPU overload. Most likely the above Windows issue contributes to this.
https://obsproject.com/wiki/GPU-overload-issues
19:19:47.060: Video stopped, number of skipped frames due to encoding lag: 183352/420083 (43.6%)
Encoding lag.
I assume you're using x264 encoding instead of NVENC because you can theoretically get higher quality at your relatively low bitrate (2500) and that is true, but if your CPU can't run your game and OBS at the veryfast preset without dropping half of all frames then you're better off with NVENC.
https://obsproject.com/wiki/General-Performance-And-Encoding-Issues
17:23:08.308: adding 23 milliseconds of audio buffering, total audio buffering is now 69 milliseconds (source: Audio Output Capture)
17:23:10.305: adding 23 milliseconds of audio buffering, total audio buffering is now 92 milliseconds (source: Audio Output Capture)
17:23:16.436: adding 23 milliseconds of audio buffering, total audio buffering is now 116 milliseconds (source: Desktop Audio 2)
17:23:42.421: adding 23 milliseconds of audio buffering, total audio buffering is now 139 milliseconds (source: Audio Output Capture)
17:27:50.595: adding 23 milliseconds of audio buffering, total audio buffering is now 162 milliseconds (source: Audio Output Capture)
17:29:11.434: adding 185 milliseconds of audio buffering, total audio buffering is now 348 milliseconds (source: Audio Output Capture)
Increasing audio buffering during a stream is also indicative of CPU overload.
Windows is out of date and a broken feature is likely reducing OBS performance. You should upate; read the link at the bottom of this post.
19:19:47.058: Output 'simple_file_output': Number of lagged frames due to rendering lag/stalls: 79057 (18.8%)
Rendering lag caused by GPU overload. Most likely the above Windows issue contributes to this.
https://obsproject.com/wiki/GPU-overload-issues
19:19:47.060: Video stopped, number of skipped frames due to encoding lag: 183352/420083 (43.6%)
Encoding lag.
I assume you're using x264 encoding instead of NVENC because you can theoretically get higher quality at your relatively low bitrate (2500) and that is true, but if your CPU can't run your game and OBS at the veryfast preset without dropping half of all frames then you're better off with NVENC.
https://obsproject.com/wiki/General-Performance-And-Encoding-Issues
17:23:08.308: adding 23 milliseconds of audio buffering, total audio buffering is now 69 milliseconds (source: Audio Output Capture)
17:23:10.305: adding 23 milliseconds of audio buffering, total audio buffering is now 92 milliseconds (source: Audio Output Capture)
17:23:16.436: adding 23 milliseconds of audio buffering, total audio buffering is now 116 milliseconds (source: Desktop Audio 2)
17:23:42.421: adding 23 milliseconds of audio buffering, total audio buffering is now 139 milliseconds (source: Audio Output Capture)
17:27:50.595: adding 23 milliseconds of audio buffering, total audio buffering is now 162 milliseconds (source: Audio Output Capture)
17:29:11.434: adding 185 milliseconds of audio buffering, total audio buffering is now 348 milliseconds (source: Audio Output Capture)
Increasing audio buffering during a stream is also indicative of CPU overload.
Narcogen
Active Member
I have linked a troubleshooting page for each problem that explains the possible causes and suggests possible remedies.
You should switch to the NVENC encoder if possible, and use a higher bitrate for streaming to compensate for reduced quality if your internet provider can handle it.
You should also update Windows, manually if necessary, as the build you are using is three years out of date.
You should switch to the NVENC encoder if possible, and use a higher bitrate for streaming to compensate for reduced quality if your internet provider can handle it.
You should also update Windows, manually if necessary, as the build you are using is three years out of date.