With HQDN3D+ColorCorrection+Levels+Saturation my CPU is maxed out and GPU is barely utilized. With no filters at all my GPUs are barely utilized on 1080p60 and CPU utilization is in 60%-80% range. So with 1080p60 I could see h264_libtoolbox utilizing GPU (sometimes both GPU, yey!) but barely! So I started playing with 1080p60 material and on Windows 1080p60 utilize GPU about twice as much both for QSV and NVENC, i.e. BTW, exporting 1080i as 1080i just doesn’t work, nor do I care it to work. Bizarrely enough same timeline could encode with NVENC on Windows say at 12Mbps VRB but fails at say 40Mbps VRB, but other timeline could encode at 40Mbps but fail at 12Mbps - it is very inconsistent in my experience, but it is a topic for another thread.īased on my experience on Windows I concluded that may be NVIDIA just doesn’t like 1080i, no matter that I export it as 1080p30. On Windows I’ve noticed that encodes on my 1080i material were failing a lot - it appears that NVENC doesn’t like 1080i material and errors out. I’ve been doing encodes on the same Hackintosh/Windows and on MacBookPro. What do I mean by “occasionally” and “it depends” and how did I arrive to this conclusion? Let me share my experience. By occasionally I mean it depends a lot on material and filters. Videotoolbox does use GPU but only occasionally. I am not confident macOS Activity Monitor accurately reports GPU utilization with Intel hardware encoding.Īfter a few more renders here is what I found:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |