@nprofile1q... Sassy

@nprofile1q... Best lolis

@nprofile1q... Maybe it's just me, but that sounds like a great idea.

@nprofile1q... Or you can specify the bitrate directly with -b:v. I think 4500K should be good.

@nprofile1q... For 264, I'd use no lower than -crf 28. You can use -crf 32 and in my opinion it looks fine.

And I personally like to use -preset slow or even -preset veryslow because I'm patient. It helps with quality while keeping a similar bitrate. But with slower rendering, I'd go as high as -crf 34.

@nprofile1q... Yep. It seems counterintuitive, but if the bitrate is *too* high, it fails to play correctly. Luckily, you can use that exact fide file, compress it to about 4Mbps, and it won't have the playback bugs (unless the file is truly corrupted, in which case you'll need to start from scratch. In that case, just set your editor export to 30 crf).

I'm a big nerd for video compression. I've rendered videos with obscene bitrates, and while all the framedata is fine, playback looks glitchy.

@nprofile1q... Is that unedited footage directly from your recording software?

Either way, I promise you it can be compressed further an not look like trash. Also, "High Efficiency" doesn't mean low bitrate; it means less loss (in comparison to 264).

Do you have ffmpeg, and also know how to use it? You can compress it with your hardware encoder so it's fast to complete, and lossy compression it especially good quality with HEVC.

@nprofile1q... That's viddy-games for ya. All the graphics are rendered on the fly, often within the GPU, and then sent directly to your monitor with little to no overhead. Unlike any video format which squeezes all some-thousand frames into a single, extremely dense file.

@nprofile1q... I am 100% looking now

@nprofile1q... Eh. I guess.