Using Video ToolBox on M1 Max Powerbook

HandBrake for Mac support
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
jjmccrae
Posts: 4
Joined: Fri Jul 19, 2019 9:32 am

Re: Using Video ToolBox on M1 Max Powerbook

Post by jjmccrae »

Was just curious about the new MBP14 and Handbrake and stumbled upon this thread. Currently using a 2016 MBP to convert DVD to digital and its takes its time so any new Mac will be better.

But if I’m reading/following correctly until the API is updated it doesn’t really make a difference in a spec bump from 8-core CPU, 14-core GPU to either the 10CPU,14GPU or 10CPU/16GPU.

Currently looking at a new MBP14 and don’t know which to land on.
varase
Posts: 33
Joined: Sat May 14, 2016 9:29 am

Re: Using Video ToolBox on M1 Max Powerbook

Post by varase »

The M1 Pro SoC has media encode/decode engines for H.264, H.265, and ProRes.

The M1 Max doubles up the encode engines, and doubles up the ProRes decoders.

Use of the VideoToolbox speeds things up nicely - VideoToolbox _may_ use the QuickSync stuff in your CPU or your discrete GPU if you have one.

Most recent machines have video IP blocks in the T2 chip, and M1 machines have a Media Engine built in to the SoC.

In the GUI version, check the Video tab and check to see what Video Encoders you have available. Hardware encoding may not be as versatile, but if available it sure is faster.

The latest snapshot versions of Handbrake seem to use the video encode IP blocks of the 2021 MacBook Pro. It's available here: https://github.com/HandBrake/handbrake- ... es/tag/mac.
User avatar
Ritsuka
HandBrake Team
Posts: 1357
Joined: Fri Jan 12, 2007 11:29 am

Re: Using Video ToolBox on M1 Max Powerbook

Post by Ritsuka »

1.5.1 is out and contains the fixes to the issues discussed in this thread.
varase
Posts: 33
Joined: Sat May 14, 2016 9:29 am

Re: Using Video ToolBox on M1 Max Powerbook

Post by varase »

Ritsuka wrote: Wed Jan 12, 2022 7:25 am 1.5.1 is out and contains the fixes to the issues discussed in this thread.
Thank you.
Post Reply