For whatever reason, the framerate is still erratic during this 0.5s noisy part and I just can't seem to understand why. Results were better, but still unimpressive.
So, I lowered the max bitrate to 16000 in an attempt to stabilize the framerate during playback. As it turns out, when this noisy 0.5s scene occurs, it uses this opportunity to apply a huge bitrate, as evidenced by the fact that the NVENC video is much higher quality compared to the x265 one (only during this noisy scene). NVENC allows you to specify a "maximum bitrate", and I would typically set that to 50,000 (no reason in particular, it didn't seem to influence the resulting filesize, so I kept that value). I have a theory as to why this is happening. After watching the resulting MKV file, I noticed the framerate was behaving erratically, especially when a very noisy scene would occur, such as when a player kills you, and your screen shows a 0.5 second noise overlay effect to indicate that you have died.Īfter a lot of experimentation back and forth between NVENC and x265, I determined that x265 produces a much smoother playing video, but doesn't produce as high quality of a result compared to the NVENC video during the noisy part.
I started off converting using NVENC because it converts at a very fast rate compared to x265 (no surprise there). I'm mostly here to report my very unprofessional findings and ask a couple questions. I've been recording some gameplay footage of Battlefield 4 using Nvidia Geforce Experience at 50,000 bitrate, then using Xmedia Recode to convert to 10,000 bitrate (for storage purposes).
0 kommentar(er)
