Software producing files that were 25%-33% of the original H.264, VTB 33% to 50% of the original. Software encoding was yielding 15-25fps, VTB 180-220fps. Both may be more than I could get away with, but the aim of the conversion project was to "save disk space", not "save as much disk space as I possibly could" and I wanted to be sure that the output wasn't going to disappoint me. I've attached my two presets (not so much to share them, more it's easier than listing what settings they contain), but with Handbrake 1.4.2 on the M1 Mini (it was current when I started my project), I found software RF20 to be more than acceptable and also VTB CQ45. Also potentially not helped by hardware or software changes. ![]() I eventually settled on H.265 10-bit as my preferred encoder but then the challenge of finding "the best" quality/speed compromise begins. The professional Quadro family supports unlimited instances in theory but the practical limits are governed by the amount of available VRAM and CUDA cores.As Box mentioned, finding settings in amongst the myriad of options Handbrake offers and then trying to decide which one provides the smallest file sizes and best quality viewing experience is hard, to say the least Word to the wise, if you're going to try this you better make sure you have a video card with a 4Gb frame buffer because a 2Gb buffer is no were near enough. > whether you can encode multiple clips in parallel using NVEncC seems to depend on the capabilities of the vpu Consumer gpu's are limited to 2 NVENC instances at any one time there is one small "loophole" that can be exploited to get around this limitation, NVENC is capable of encoding to multiple resolutions in one go, so if you had a 4k source you could output a 4k, 3k, 2.5k, 1080p and 720p at the same time and it would only count as a single instance of NVENC. I can encoded two HD (1920x1080) clips using NVEncC works without a problem here (GeForce GTX 980Ti), encoding more than that in parallel causes the lastest encode to crash at startup. support to NVEnc&Co without new vpu chips which is designed to support this.Įncoding multiple movies in parallel with Hybrid using NVEncC works fine here, as long as the card supports it. Which is why you can't simply add b-frame, 2pass. If you check your gpu during encoding you will see that only the VPU is fully used, the gpu isn't used that much.īut using a specialized vpu (like used on normal consumer graphic cards) has it's limits, the vpu is a cheap chip which is really limited in what it can do. (a programming language which allows to use the graphic processing units). ![]() Thus the argumentation only explains why this is the case.Ĭurrently hardware encoding on AMD/Intel/NVIDIA graphic cards doesn't use OpenCL/CUDA/. ![]() Your argumentation has some merit any explains why gpus are not as efficient as cpus for general purpose computing, but the fact remains that the gpu isn't used (like I wrote before otherwise the high end flagship cards with way more cuda cores would be way faster than the lower/middle class cards which just have the same vpu.) This is the reason why NVIDIA, AMD, Intel all use dedicated vpus&co and not the gpu for encoding. Yes, you loose some quality if you use more cores (happens on CPUs too), but that quality loss isn't that much.Īnd yes, most algorithm can't be (easily/efficiently) ported to use lots of slow and limited processing units instead of a few fast processing units.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |