Record it game screen recorder app is a comprehensive application that provides game screen recorder with facecam and audio for mobile game enthusiasts and content sharers. 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).Record it is a completely FREE no ads screen & GIF recorder & screenshot app with NO watermark! (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) Below 12 should not be used unless having a specific reason. 12 can be used when the output will be edited later, to minimize re-encoding artifacts, but will result in VERY large files. CQP does quality-target encoding to maintain a given image quality level. Recording should be done using CQP, not CBR. 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?). They cause problems even in otherwise perfect setups. Disable Lookahead and Psychovisual Tuning. When using NVENC, use the Quality preset, not Max Quality (you are not, just including for completeness). 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. ![]() I'm still mildly curious what underlying issue you're looking to solve that needs locked CFR. 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. There is ZERO need for it beyond "we've always done it this way".Ĭlick to expand.Interesting results. We aren't even broadcasting analog any more, and every TV has been full-integer signal ready for at least 15 years now. Still want that crap to be kicked in a hole, buried, and forgotten as soon as possible. If your capture device 1000% can, then it depends on your source rate. ![]() Many cannot, and jerking back and forth from the fractional source feed, to an integer capture rate, BACK to a fractional rate will just increase judder significantly over just capturing integer and recording integer. So if that's your underlying issue? Recording to MKV and remuxing to mp4/mov is how you fix it, not worrying about one-off VFR hits from an ffmpeg inspection pass.Īs far as fractional values, make sure that your video capture device can capture at fractional rates properly. Premiere, Vegas, Resolve, and a few others are notorious for absolutely screwing up BADLY when handed direct-record MP4 or MOVs from OBS, even to the point of completely crashing. Remuxing from MKV to MP4/MOV also can result in a cleaner rewrap structure and indexing, which means that video editing suites will be able to ingest them and scrub with fewer issues. which won't exist for a live recording, which are always variable to a certain extent. There are 'recovery tools' out there, but they only work properly with a clonable atom. MP4 and MOV store the metadata atom at the end though, meaning if ANYTHING goes wrong during recording, the recording is permanently and 100% irrecoverably corrupted as it won't receive the finalization it needs to be complete and playable. ![]() Remuxing just rewraps the videostream in one of the other containers.
0 Comments
Leave a Reply. |