Why don’t you watch his review and find out? Both 4K ProRes and h264 encodes with a 19min 10bit input and a mix of gnarly codecs such as XF AVC, Dolby Vision iPhone and Cannon 8k. 4x faster on h264, 10x faster on ProRes whilst using only 10% battery life vs 75% on the Intel machines (even those including the T2 chip with hardware encoder).
There’s many YouTube reviews showing the same….video editors are gobsmacked at what these new M1 Max machines are capable of….when they make statements such as “this is faster than my $15k 18c Mac Pro with Afterburner and 192Gb”, you can guarantee that this is a paradigm shift for many pros. What previously needed a desktop computer and an office can now be done mobile, on battery in the client’s office.
I rarely watch YouTubers because many YouTubers are not experts (rather the opposite) but just fanboys with little knowledge but lots of viewers.
The issue of quality and file size is usually ignored in such "tests" (many of the "testers" are not even aware that there are differences in the result apart from the speed), although there can be huge differences. They only look at the speed of the encoding. That is all.
It has always been the case that hardware encoders are super fast, but the results (quality, file size) are mediocre to lousy. NVENC seems to be a positive exception.
Of course, you have to compare the hardware encoders against the really good software encoders (i.e. for H.264 you take x264, for H.265 you take x265) and not against mediocre to bad software encoders (typically the stuff that Apple, Adobe & Co include with their Pro software).
These "great" YouTuber have not paid attention even before. Here in the forum, on the other hand, there are people who pay attention.
"Seeing exact same thing. I haven't compared the VT vs x265 quality yet extensively but eye test, the VT version had to be encoded at 8K+ BR to yield comparable quality to x265 which was closer to 2K BR. And of course the resulting 9GB file vs 2.3GB file."
Hey guys, I have big collection of series on iTunes and I would love to convert all H.264 videos to H.265 to shrink my storage. For that reason I'd consider buying Mac Mini M1. To those who already bought it, has someone tried to convert x264 to x265 and tell me how that went? What software did...
forums.macrumors.com
"H.265 (VideoToolbox [= HardwareEncoder])'s quality is significantly worse than the quality of the same size H.264 (x264). But I thought this was to be expected? Note however that I'm on an intel Mac and I can not use the CQ slider. I am forced to use constant bitrate which affects video quality significantly."
iOS A-series chips have had hardware H265 encoding for years. I have heard that this hardware acceleration has finally come over to Macs with the new M1 series chips. I would like to ask someone with an M1 Mac to try out the following benchmark: 1. Download the 30MB 720p sample video from here...
forums.macrumors.com
"
I think that a visual quality of hardware video encoder (VideoToolBox H.264) in M1 Macs is not great.
I compared a software libx264 encoder (Mac) and NVIDIA Geforce (NVENC) on Windows 10 with the same bitrate or constant quality mode producing almost identical file size.
I see many visual artefacts on a video encoded with VideoToolBox H.264 (1080p 60 fps) 3300K or CQ56. It's especially noticeable on video with animated photo slideshows and blur effect. Too many artefacts. NVENC and libx264 produce much better visual results with the same file size."
developer.apple.com
So if speed is all that matters to you, then hardware encoding is the way to go. If you are also concerned about quality in relation to file size, then the hardware encoder is not necessarily the right choice.