Hello, I'm currently running a pc with a i7 8700k intel core i7 cpu, a 1080ti, and 32gb ddr4 ram, with watercooling and everything, cpu is overclocked to 5ghz, while the gpu isn't overclocked at all. When recording, I'm using ~50-60% of my cpu while ingame, which I don't think is bad. The temperature doesn't spike either. Somehow I still get the message "Encoding overloaded", I've tried many different settings, and my output is almost always some 1fps nonsense, I know that I'm recording in 240fps, with 2560x1440, but I've tried 1920 at 60 fps, and there's not a big difference in the cpu usage. I don't really get it? - the logs is here aswell. Also I should mention that I used the same settings a few months ago with OBS, where the output was really smooth and good looking, no jitter or lag at all. Please help a fellow gamer :)
Question / Help Encoding overloaded issue - On a REALLY good pc
- Thread starter Pluzclaw
- Start date
Narcogen
Active Member
Start by turning off psycho active tuning.
Don't use CBR for recording, that's for streaming. Use CQP rate control instead, with a quality setting between 14 (high quality) and 23 (good quality). Looking at how low your bitrate is for CBR (5000) I'd suggest 23. That bitrate is much, much too low for 1440p240. It's not even suited for 1080p60. Even if it didn't lag, it would likely look pretty bad.
17:32:30.788: Video stopped, number of skipped frames due to encoding lag: 4649/4723 (98.4%)
However, the amount of encoding lag you're getting here at these settings is massive-- almost 100%. You're not close to being able to do this. I'm not certain what was going on before, but nothing of my experience with OBS leads me to believe you can do this on a 1080. People are trying to do this on a 20xx series card and getting similar results.
You were already getting small frame drops at 1080p60. There's nothing to indicate that these numbers would stay the same once you increased to 1440p240, and it's predictable that the number of dropped frames would increase dramatically.
17:28:45.342: [jim-nvenc: 'recording_h264'] settings:
17:28:45.342: rate_control: CBR
17:28:45.342: bitrate: 5000
17:28:45.342: cqp: 20
17:28:45.342: keyint: 250
17:28:45.342: preset: mq
17:28:45.342: profile: high
17:28:45.342: width: 1920
17:28:45.342: height: 1080
17:28:45.342: 2-pass: true
17:28:45.342: b-frames: 2
17:28:45.342: lookahead: false
17:28:45.342: psycho_aq: true
17:28:45.342:
17:28:45.401: ==== Recording Start ===============================================
17:28:45.401: [ffmpeg muxer: 'adv_file_output'] Writing file 'D:/OBS recordings/2020-01-04 17-28-45.mp4'...
17:29:14.834: [ffmpeg muxer: 'adv_file_output'] Output of file 'D:/OBS recordings/2020-01-04 17-28-45.mp4' stopped
17:29:14.834: Output 'adv_file_output': stopping
17:29:14.834: Output 'adv_file_output': Total frames output: 7030
17:29:14.834: Output 'adv_file_output': Total drawn frames: 7053 (7064 attempted)
17:29:14.834: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 11 (0.2%)
17:29:14.834: ==== Recording Stop ================================================
17:29:14.834: Video stopped, number of skipped frames due to encoding lag: 11/7062 (0.2%)
Don't use CBR for recording, that's for streaming. Use CQP rate control instead, with a quality setting between 14 (high quality) and 23 (good quality). Looking at how low your bitrate is for CBR (5000) I'd suggest 23. That bitrate is much, much too low for 1440p240. It's not even suited for 1080p60. Even if it didn't lag, it would likely look pretty bad.
17:32:30.788: Video stopped, number of skipped frames due to encoding lag: 4649/4723 (98.4%)
However, the amount of encoding lag you're getting here at these settings is massive-- almost 100%. You're not close to being able to do this. I'm not certain what was going on before, but nothing of my experience with OBS leads me to believe you can do this on a 1080. People are trying to do this on a 20xx series card and getting similar results.
You were already getting small frame drops at 1080p60. There's nothing to indicate that these numbers would stay the same once you increased to 1440p240, and it's predictable that the number of dropped frames would increase dramatically.
17:28:45.342: [jim-nvenc: 'recording_h264'] settings:
17:28:45.342: rate_control: CBR
17:28:45.342: bitrate: 5000
17:28:45.342: cqp: 20
17:28:45.342: keyint: 250
17:28:45.342: preset: mq
17:28:45.342: profile: high
17:28:45.342: width: 1920
17:28:45.342: height: 1080
17:28:45.342: 2-pass: true
17:28:45.342: b-frames: 2
17:28:45.342: lookahead: false
17:28:45.342: psycho_aq: true
17:28:45.342:
17:28:45.401: ==== Recording Start ===============================================
17:28:45.401: [ffmpeg muxer: 'adv_file_output'] Writing file 'D:/OBS recordings/2020-01-04 17-28-45.mp4'...
17:29:14.834: [ffmpeg muxer: 'adv_file_output'] Output of file 'D:/OBS recordings/2020-01-04 17-28-45.mp4' stopped
17:29:14.834: Output 'adv_file_output': stopping
17:29:14.834: Output 'adv_file_output': Total frames output: 7030
17:29:14.834: Output 'adv_file_output': Total drawn frames: 7053 (7064 attempted)
17:29:14.834: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 11 (0.2%)
17:29:14.834: ==== Recording Stop ================================================
17:29:14.834: Video stopped, number of skipped frames due to encoding lag: 11/7062 (0.2%)