[RECORDING] is it most optimal to have 0 frames not rendered?

[qwertywatsu]

Hello, last night I recorded a full game match in CS:GO with my Lenovo Y740 laptop.

The specs of my laptop are: 9th Gen i7-9750H (turbo boosted), and an RTX 2070 8GB with Max-Q Design

The settings I chose are: 1280x760 output, 60fps, 7500Kbps recording bitrate (720p60 for YouTube), set to high profile, and preset for performance.

Upon looking at the logs, I saw that I got some of the frames not rendered due to lag. My question is: is there a way to tweak my settings so I can record all the frames? Here is my log:

21:45:42.143: [NVENC encoder: 'recording_h264'] settings:
21:45:42.143: rate_control: CBR
21:45:42.143: bitrate: 7500
21:45:42.143: cqp: 0
21:45:42.143: keyint: 250
21:45:42.143: preset: hp
21:45:42.143: profile: high
21:45:42.143: width: 1280
21:45:42.143: height: 720
21:45:42.143: 2-pass: false
21:45:42.143: b-frames: 2
21:45:42.143: GPU: 0
21:45:42.143:
21:45:42.289: ---------------------------------
21:45:42.290: [FFmpeg aac encoder: 'Track1'] bitrate: 160, channels: 2, channel_layout: 3
21:45:42.290:
21:45:42.299: ==== Recording Start ===============================================
21:45:42.299: [ffmpeg muxer: 'adv_file_output'] Writing file 'D:/videos/2020-09-15 21-45-42.mp4'...
22:13:26.361: Stopping recording due to hotkey
22:13:26.647: [ffmpeg muxer: 'adv_file_output'] Output of file 'D:/videos/2020-09-15 21-45-42.mp4' stopped
22:13:26.648: Output 'adv_file_output': stopping
22:13:26.648: Output 'adv_file_output': Total frames output: 99844
22:13:26.648: Output 'adv_file_output': Total drawn frames: 99838 (99861 attempted)
22:13:26.648: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 23 (0.0%)
22:13:26.649: ==== Recording Stop ================================================
22:13:26.649: Video stopped, number of skipped frames due to encoding lag: 16/99860 (0.0%)

 

[koala]

A few lost frames at rendering lag are ok. Single lost frames may occur on recording start while everything still needs to stabilize, or on map loading of a game, or whenever some app switches to foreground or reinitializes its graphics engine.
Encoding lag is a bit worse, it is a sign of encoder overload thus not enough computing resources. Again, load spikes might occur on the same initialization events as above.

Use the stats window of OBS and observe the number of missing and skipped frames. If they only increase at game/map loading and in spikes, it's fine. If they increase continuously one by one over the whole duration of your recording, it's bad.

You have 60 fps, 99861 frames and 23 lagged. This is 99861 frames / 23 frames / 60 fps = 72 seconds per lost frame. That means, every 1 minute 12 seconds you have one lost frame if they are generated continuously. Almost not visible. And if they come in spikes, they come with some kind of transition (map loading), thus not visible entirely.