For example, in 1-hour long movie, it will take 2 hours to encode one file. On my laptop, with Intel core I7 6500U with 2 cores, 4 thread and 8 gigabytes of memory, It takes twice the time of the movies to encode. Good news right? Yeah right, The hard pill is that we are trading space for computing complexity. However, I found out that we can save more than 70% of the space with the same quality by converting those file to H265. A 30 minutes movies took almost 1GB of storage. Good times.Have you ever want to try the ludicrous power of 24 CPU cores? I sure have! In this post, I am experimenting with Google cloud engine to transcode H264 files to H265. But based on the M1 performance, I think I will keep my powder dry for the rumored M1X or M1Z models, which should start off at least 70% faster than the M1.

The true import of this is that the Macbook Pro M1, which also has a fan and therefore will perform virtually identically to the Mac mini M1, is going to completely obliterate the 13' Macbook Pro 4-core i5 I just bought in June.

Compare to the i7 mini, which is very warm to the touch, with a blast of hot air from the rear vent.

I'm doing some x264 -> x265 software encoding right now on my newly-arrived 8GB RAM Mac mini M1, and the performance under the Handbrake 1.4 beta 1 appears to be on par with my 2018 32GB RAM Mac mini 6-core i7 in terms of frames per second (they're churning away on the same file right now), which is somewhat less than I expected based on reported Geekbench scores, but the Mac mini M1 remains very responsive and its fan, although running, remains silent and there is very little heat coming out of the machine - either the case, or the rear vent.

Convert h264 to h265 ffmpeg