Quicksync h .26410/31/2022 ![]() Yes, the four CPU cores are at 300% utilization, but obviously there's some hardware assist going on. But the ridiculously fast Mac Mini VideoToolBox H.265 video encoding doesn't use the GPU. H.264 VTBx runs on the Intel HD 630 GPU, which performs the same as the 530 one in the MBP. #QUICKSYNC H .264 FULL#(Strangely, x265 doesn't seem to use all hyperthreads to their full capacity.) Added benefit: the computer doesn't get very hot and the fans don't spin up, while they run at full blast using x264 or x265. If we can believe the Activity Monitor GPU history, VTBx uses the Intel HD 530 GPU but not the AMD 450 Pro. X264 and x265 run on the CPU, VTBx also still seems CPU-bound, but also makes use of the Intel Iris GPU.Ģ016 MacBook Pro, 2.6 GHz Core i7 (4 cores, 8 threads) Results in seconds.Ģ013 MacBook Pro, 2.4 GHz Core i5 (2 cores, 4 threads) I really don't like using average bitrate, as it can inflate file sizes unnecessarily, but it was the only option for VideoToolBox encoding. I used Handbrake's Fast 1080p30 preset but with the quality changed to an average bitrate of 1500 kbps. #QUICKSYNC H .264 MOVIE#And everyone should see this 118-year-old movie at least once, too. It has no sound so that doesn't use up additional time. I used Le Voyage Dans la Lun from 1902 for this purpose, because at 11 minutes it's big enough that the start/stop overhead won't dominate but small enough that testing doesn't take forever. So I did some testing, with very interesting results. Turns out that VideoToolBox is an Apple framework for decoding and ecoding video, using hardware features for that purpose when possible. ![]() The new thing I noticed are the (VideoToolBox) options. ![]() The default encoders in Handbrake for these codex are x264 and x265, respectively. The former is older, faster and more compatible, the latter produces smaller files. The most obvious choices are H.264 and H.265. When you encode a video, you can select between several encode options. Will an AMD RX 580 in this configuration be able to hardware decode H.264/H.I discovered something interesting in the video encoding app Handbrake today. I would love DR16 to utilise the current hardware for smooth playback - why is it not doing that? Using other apps, playback is smooth using GPU, confirming GT 1030 is able to. So it seems neither Intel Quick Sync nor GPU is used. I can confirm that GPU shows no activity when playing back 8-bit 4:2:0 H.264/H.265 (and CPU maxing out) in DR16. Why? The GT 1030 is able to hardware decode these files using other software. Here I do not have the option "Decode using H.264/H.265 using hardware acceleration" available/visiable at all. ![]() I have terrible choppy H.264/H.265 playback, in DR16. #QUICKSYNC H .264 FREE#On another older installation another place, I use the free version of DR16 with Windows 10, an Intel Ivy Bridge CPU (3770 as I recall) and an NVIDIA Geforce GT 1030. How does this match first and second bullet point above? It seems to be GPU, as the Activity Monitor show RX 580 GPU activitity when simply playing back H.264 in the Media page (ensuring it doesn't render any effects from color, fusion etc). On one installation I use with the free version of DR16 with macOS, an i7-8700K CPU and AMD RX580 GPU, I have the option (under Preferences) "Decode using H.264/H.265 using hardware acceleration" available and active.ĭoes this refer to CPU (Intel Quick Sync) and not GPU?
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |