It would be interesting to see what Apple compressor could do. ![]() If I had a new M1 type processor I would review the setup. But in the end didn't feel it was worth it for my setup to bother with either 265 and VB. Mind you that was a few versions ago in HB it may have been improved or I could have fiddled a bit more. When I did my own tests there was some noticeable quality issues with VideoToolbox compared to the software render. You should check out the quality of the results. MacBook Pro 14" M1 Max with 32Gb and macOS 12.2.1 The results are eye opening for me and once again I am just looking at times, not final video quality. Once using VideoToolbox option then again using standard settings. I got the Big Bunny Buck video that the Handbrake team likes as a benchmark in both 1080p and 2160p formats then converted them to the same size H265 MKV format. ![]() It's just that the Max could do multiple encodes at once. This is the reason why encodes using these engines are the same speed regardless of M1 Pro or M1 Max. Please see where they say VideoToolbox is using dedicated video encoding engines on the M1 Pro / Max chips. So is it using the ProRes cores on M1? I'm looking at an M1Pro with bonus money and it's always chapped my hide that performant acceleration solutions take money.or I'm just looking in the wrong places.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |