![]() I tried encoding DVD (= laughably fast codec + tiny resolution) in handbrake and the speed was not measurable (0 seconds!) despite preparation (downsize from original) took some time. Nice brag, but M1 is "ok" at best when it comes to editing or current material, i just assisted in some thread where user was sad with M1 rendering speed. Generally h265 should be smaller for the same crf You can queue up an encode or two overnight and then just let it run.Īs to the people who say Turing/Ampere NVENC can match x264/x265 - at what bitrates? It seems that you need significantly more bitrate to get the same quality level with hardware encodes. I will say it is very fast and if you are okay with the quality and file sizes it produces, nothing wrong with using it. It wasn't really built around offline video encoding. ![]() NVENC was really designed around fast encoding for game streaming in real time as not to affect CPU resources. Most times the NVENC H265 encodes are around the same size as my x264 encodes. The NVENC H265 encodes sometimes come out a little smaller, but it's usually not a significant difference. I think this has to do with some of the more advanced options available in x264 that are not available in NVENC. I notice that x264 retains slightly more fine detail. I find that while NVENC H265 does look good, it doesn't look quite as good as x264 compared to the original Blu-ray content. I use CRF 24 for the H265 encodes and CRF 20 for the x264 encodes, default speed settings. ![]() I have tried both NVENC H265 (on my RTX3060 and previous GTX1070) and x264 (Intel i7 8C/16T).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |