I am guessing HEVC encode/decode is handled using/via the T2 chip hence it doesn't show up. I was only referring to the VideoToolBox API, not the command but glad you looked it up. This is really not bad at all.įfmpeg -i file_example_MP4_1920_18MG.mp4 -c:v hevc_videotoolbox -quality quality -b:v 3M -bufsize 16M -maxrate 6M outputhevcIntel.mp4įrame= 901 fps=143 q=-0.0 Lsize= 5194kB time=00:00:30.52 bitrate=1393.9kbits/s speed=4.85xĪnd for x264 the codec is "h264_videotoolbox" with 268 FPS:įrame= 901 fps=268 q=-0.0 Lsize= 11309kB time=00:00:30.52 bitrate=3034.7kbits/s speed=9.09xĮDIT: There is something strange for hevc_videotoolbox codec 1) it looks there is no load on the iGPU. h264_videotoolbox behaves as expected with visible load on iGPU. Posted by: thank you for your hint: I got now the correct codec for MacOSX: it's actually "hevc_videotoolbox" (ok, that was easy), and result is 143 FPS. So, unfortunately, most of your post is incorrect. The best case scenario (which won't happen) could be for Apple to provide multiple options to boot bootcamp Windows (one with iGPU and the other with dGPU set). Finally, Apple switches off the integrated GPU as macs use gmux (fundamentally different to non-Apple laptops with integrated + discrete chips) and Windows has no mechanism to switch gmux on the fly (so you need to set the mux then reboot - done today using NVRAM and managed in early EFI). Recommendations: Intel recommends updating the Intel® VTune Profiler software to version 2023.0. Intel® VTune Profiler software is included as part of the Intel® System Bring-up Toolkit before version 2023.0. In fact, contrary to this, look at Apple's A-series chips that support this, starting from the A9 - so they do care somewhat. Intel® VTune Profiler software is included as part of the Intel® oneAPI Base Toolkit before version 2023.0. The older Macs can't do it because there was no hardware for it. 8-bit HEVC will use hardware acceleration, while 10-bit won't as of now.Ģ is on Intel and is a hardware limitation - not sure how Apple is responsible. Also, Apple software is far from overpriced (hardware, sure), and as far as I can tell, in media they are the most performant. This is the reason why Handbrake developers are not too fond of it. szatmary at 5:54 While performance of a Intel UHD graphics 620 iGPU is very good for the price point, there is no comparison, to a dedicated GPU. 11th Generation Intel Core i7 Processors Code Name Products formerly Rocket Lake Vertical Segment Desktop Processor Number i7-11700 Lithography 14 nm Recommended Customer Price 355.00 - 365.00 Use Conditions PC/Client/Tablet CPU Specifications Total Cores 8 Total Threads 16 Max Turbo Frequency 4. If the API was better, we would all be in a better place. As to what is better Quicksync vs NVENC, it totally depends on hardware generation, the content, and the options used. Quick Sync is a hardware implemented GPU-feature offered by many of Intels current Core i9, i7, Core i5 and even Core i3 processors. I believe Apple's video encoding API is videotoolbox, which is GPU-accelerated but allows only extremely limited tweaking (typical Apple). MacOS can use QuickSync using ffmpeg (example app is VideoProc which is honestly too expensive given that under the surface it's using ffmpeg) and Final Cut Pro also uses this if you export to H264 (FCP doesn't support HEVC export).
0 Comments
Leave a Reply. |