But I was expecting the M1 Max to be way faster. Could someone with an M1 Max Studio repeat the same test? The Apple Store was really busy and it didn't seem right to hog the machine for another six minutes as I'd already been using it for 15.Īt some point relatively soon, I need to go 'legit' as I can't stay on Mojave indefinitely. Is there a known issue with Handbrake and the M1 Max? I searched and found some supposed issues from when the M1 (not Max or Pro) was first introduced, but I can't find a definitive answer. It took 4:38 to finish with an average speed of 68.66 FPS.ĭuring the test at the Apple Store, I had Activity Monitor open the entire time and it looks like Handbrake was using ≈ 830-50% CPU time during the encode. (I did not think to see how many GPU cores, but as the test was a software encode, it shouldn't matter much)ĩ700K 5 GHz, 32 GB, macOS 10.14.6, Handbrake 1.5.1

It took 6:17 to finish with an average speed of 50.76 FPS. I took a screenshot of the results and went back home to test the same file on my four year-old 9700K Hackintosh. While standing there for a few minutes, it seemed kind of slow.

Per Handbrake's benchmarking suggestions, I used the 'Big Buck Bunny 1080p30' file for a software encode using 'Fast 1080p30' and H.265. Just got back from the Apple Store where they kindly let me install Handbrake and encode a file on a Studio M1 Max.

Handbrake macbook