That log doesn't show any dropped frames for rendering or encoding
And typically, those who know much more than I about OBS, recommend against using CBR for recording (typically required for streaming, and not recommended for recording). Granted, if you are streaming and recording locally (and using same settings so as to not 2X encoding workload, then of course you'd be recording to CBR)
https://obsproject.com/forum/threads/best-settings.140188/#post-514693 @FerretBomb comment #2
...snip...
2) Record using CQP or CRF, not CBR. CBR is only used for streaming, where the back-end infrastructure requires it. CQP/CRF are quality-target based encodes, and will use as much or as little bitrate as is needed to maintain a constant image quality. No wasting bitrate on simple/slow scenes, no choking on fast-moving or complex scenes. 22 is a good starting point. 16 will result in much larger files, but near-perfect video. 12 should only be used if you plan to edit and re-encode later, and will be VERY large. Anything lower than 12 shouldn't be used unless you know exactly why you need it, and what problems it can cause.
then, only if still having performance issues you might try
3) Use the Quality preset, not Max Quality. Likewise, turn off Psychovisual Tuning. Both of these options use CUDA cores, and tend to cause significant problems like encoding overload when it should otherwise not be happening.
Jun 9 2021
Look-ahead allows the encoder to dynamically select the number of B-Frames, between 0 and the number of B-Frames you specify. B-frames are great because they increase image quality, but they consume a lot of your available bitrate (you should use CQP for recording so bitrate is not an issue), so they reduce quality on high motion content. Look-ahead enables the best of both worlds. This feature is CUDA accelerated; toggle this off if your GPU utilization is high to ensure a smooth recording.
Psycho Visual Tuning enables the Rate Distortion Optimization in the encoder, which greatly optimizes the way you use bitrate (not sure exactly how this works with CQP, possibly same quality at lower bitrate), improving image quality on movement. This feature is also CUDA accelerated.
Then, no idea if this is relevant, but just in case.. .throwing out random tidbts... you may want to look into the new Windows 10 Hardware-accelerated GPU scheduling ("HAGS") added with version 2004. I don't know if that is still causing issues with OBS (and if so which version/circumstance/config)
