Totally agree. I don't know why my camera can't record pure 30 and 60 fps. As capture device I use avermedia live gamer bolt. It must be capable to record this tyes of framerate.
Never simply assume, when you're operating on this level, and using a consumer-grade card. Heck, don't assume even if you're using a prosumer or studio card. Check the product whitesheets, when you're getting this in-detail.
I took a peek at them and it appears that for 2160p, 1440p, 1080p, 720p, 480p, and 640x480 it does support decimal rates (and does not specify fractional, but close enough), but only supports integer
capture for any other of its supported resolutions.
Finally tested my full dual PC setup with capture card and laptop. Same problem with remuxing - variable framerate. MOV - constant framerate. Stats window always showed 0 dropped frames and there are no lack of performance from GPU.
Log -
https://obsproject.com/logs/9iGXGPY-VI6hmNop
So, do my fears of remuxing have some foundation now?
Interesting results... which shouldn't happen. In your case, then yes. OBS
should be defaulting to CFR mode (the VFR mode switch formerly in Settings->Advanced was actually removed entirely from the UI at some point), but for some reason is not in your case.
I'm still mildly curious what underlying issue you're looking to solve that needs locked CFR. And if it's video editor scrubbing or ingest issues (which is the usual one), if you've tested the remuxed video files, even with the VFR present.
Additional testing steps:
-When using NVENC, use the Quality preset, not Max Quality (you are not, just including for completeness). Disable Lookahead and Psychovisual Tuning. They cause problems even in otherwise perfect setups. B-frames should never go over 2, unless you're playing an EXTREMELY low-motion game (I've seen 4 being used A LOT lately, where did you get this value from?). Recording should be done using CQP, not CBR. CQP does quality-target encoding to maintain a given image quality level. 22 is 'good', 16 is 'visually lossless'. 12 can be used when the output will be edited later, to minimize re-encoding artifacts, but will result in VERY large files. Below 12 should not be used unless having a specific reason. (cqp is how far the encode is allowed to deviate from 'perfect' uncompressed video; the lower the value, the larger the file, but the better the quality)
-Do these issues persist only with NVENC? Are you able to test with x264 Software encoding? HEVC x265? I ask because NVENC does present some other erratic issues on some setups (notably audio desync with multi-track audio in recordings for some reason, but not with single-track).