[DE]Glen
New Member
Recording only, using NVENC, I noticed that my resulting MKV or MOV file ends up with slightly different frame-rate when using I444 instead of NV12 for Color Format; this can confuse editing software but I'm not sure what other problems it may cause.
I first noticed when taking clips into Kdenlive that I'd tried to record using ProRes using Custom Output (FFmpeg); KDenlive showed a prompt offering to change my project frame-rate because it turns out my clip wasn't 59.94 as it should have been. Historically I had no trouble with clips I'd recorded with NVENC so I thought it was some missing parameter to the custom encoder settings but after much fussing around I discovered that I could reproduce this merely but switching OBS from NV12 to I444 (Settings -> Advanced -> Video -> Color Format), even with my old NVENC settings.
Here's the FFProbe output for two clips recorded normally with NVENC (I can share settings if needed).
NV12:
I444:
I don't think it's a performance issue but I can try to rule that out if necessary; I can try on a much faster machine on Monday.
A similar but probably unrelated issue is that if I switch from the standard NVENC encoder to Custom Output, even with the NVENC encoder with nearly the same settings I get the same problem: the frame-rate in the file isn't 59.54 any more.
I'm interested in this configuration (ProRes in particular) because I'm hoping to capture from a 4:2:2 source for grading and editing later (ie: using my PC like at Atomos Ninja V). Even if ProRes doesn't work out I'd love to use Custom Output so I can record my audio in PCM for cleanup in post (AFAIK you can't save PCM any other way), but in either case I'm worried that if the frame rate isn't locked it'll cause problems with sync and editing.
I first noticed when taking clips into Kdenlive that I'd tried to record using ProRes using Custom Output (FFmpeg); KDenlive showed a prompt offering to change my project frame-rate because it turns out my clip wasn't 59.94 as it should have been. Historically I had no trouble with clips I'd recorded with NVENC so I thought it was some missing parameter to the custom encoder settings but after much fussing around I discovered that I could reproduce this merely but switching OBS from NV12 to I444 (Settings -> Advanced -> Video -> Color Format), even with my old NVENC settings.
Here's the FFProbe output for two clips recorded normally with NVENC (I can share settings if needed).
NV12:
Stream #0:0: Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 20573 kb/s, 59.94 fps, 59.94 tbr, 60k tbn, 119.88 tbc (default)
I444:
Stream #0:0: Video: h264 (High 4:4:4 Predictive) (avc1 / 0x31637661), yuv444p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 26990 kb/s, 60.15 fps, 59.94 tbr, 60k tbn, 119.88 tbc (default)
I don't think it's a performance issue but I can try to rule that out if necessary; I can try on a much faster machine on Monday.
A similar but probably unrelated issue is that if I switch from the standard NVENC encoder to Custom Output, even with the NVENC encoder with nearly the same settings I get the same problem: the frame-rate in the file isn't 59.54 any more.
I'm interested in this configuration (ProRes in particular) because I'm hoping to capture from a 4:2:2 source for grading and editing later (ie: using my PC like at Atomos Ninja V). Even if ProRes doesn't work out I'd love to use Custom Output so I can record my audio in PCM for cleanup in post (AFAIK you can't save PCM any other way), but in either case I'm worried that if the frame rate isn't locked it'll cause problems with sync and editing.