6/19/2023 0 Comments M1 mac handbrakeAt least you can stuff the Mac Studio to the gills with RAM, if you need it.Īpple MacBook Pro 14-inch (Apple M2 Max, 2023) Since the M2 chips feature unified memory integrated alongside the CPU and GPU, there's no way to add additional RAM down the line, which used to be another reason to get the Mac Pro. The Mac Studio is so ridiculously overpowered, only the most demanding users would need the Mac Pro's PCIe expansion. With all that power, who needs a full-sized PC tower?Īnd really, that's what I kept asking myself as I tested our review unit, which was equipped with an M2 Ultra and 192GB of RAM. If you want to truly push your system (and wallet) to the limit, the M2 Ultra can also be configured with a 76-core GPU and 192GB of RAM. Step up to the M2 Ultra and you effectively get two M2 Max chips: It starts with a 24-core CPU, 60-core GPU and 64GB of memory. What's most notable is the additional upgrade options: You can configure the M2 Max chip with a 38-core GPU and 96GB of RAM (previously you were capped at 32GB of memory). Compared to last year's M1 Max, the new chip has two more efficiency cores and six additional GPU cores. It also shows that the iMac PRO is for many applications still a great machine.The base Mac Studio is now equipped with an M2 Max chip, featuring a 12-core CPU (with eight performance and four efficiency cores) and a 30-core GPU, as well as 32GB of RAM. The speed is still reasonable and not worrying me. At this point in time I'd not compare any real world since many might still use Open CL or Open GL implantations of code which are 2nd best to say the least - or in other words - it will take some time to fully unleash the potential of the MBPs with M1 MAX - maybe just a fresh compilation and sometimes heavy lifting under the hood in the underlying code base.ĭon't worry - this will happen rather soon. In other words - the Apple ARM implementation of HandBrake seems to underperform dramatically - this is most presumably the case for many 3rd party applications. it is still faster than the CPU driven transcoding on both machines. MBP is 15 % faster as expected - very reasonable for a laptop.GPU time for transcoding the identical film:.The results are a mixed bag for the transcoding speed: MacBook Pro 14.2" 10C / 64 GB RAM / 8 TB / 32 GPU cores.iMac PRO late 2017 10C / 64 GB RAM / 2 TB / AMD Vega 64 / 16 GB RAM.Audio transcode to two 7.1 audio streams MA to AC3 5.1.Setup a quick transcoding from MPEG4 to h.265 with the two scenarios: I have to admit that I am using it only occasionally. That explains why it was crushing my CPUs.Īs promised - done my test - looks like there is some inconsistency in the results with respect to HandBrake. Thanks for the replies! This is my first time using handbrake on Mac, I did not realize I needed to use videotoolbox in order to use hardware acceleration. to my understanding handbrake uses the CPU on MACs and since 1.4.0 it runs natively with an Univ resale binary on non Intel MACs. Will give it a try tonight and report back - acc. Is this typical? I thought this app was updated for apple silicon, and I expected it to make better (any?) use of GPU acceleration. I'm getting like 2-3fps, and more worryingly, my CPUs shoot up to 100c+ almost instantly. I have a trial version of Final Cut which can make short work of the conversion (but obv would cost a lot to buy), and another converter called videoproc also seems to perform pretty well. It seems like HEVC is the way to go, but unfortunately iMovie doesn't encode from Sony's h.264 format to HEVC, so I've been looking at conversion tools. I've started shooting more home videos after the recent birth of my daughter using a Sony A7RIV, and I'm trying to figure out the best way to encode my movies for more efficient storage. Hello, I recently purchased an 14" MBP with M1 max (32 core) and am trying to figure out if my performance results on Handbrake are typical.
0 Comments
Leave a Reply. |