I recently had a crazy idea of using my idle mobile devices as a video render cluster. I have used the following FFmpeg command to compress a 4K H.264 footage to H.265 footage with a CRF (Constant Rate Factor) of 22, both on my Android phone and on my Mac:
ffmpeg -i vid.mp4 -c:v libx265 -crf 22 -c:a copy vid-265-crf22.mp4
The command uses pure software encoding and is multi-threaded by default. Both on my phone and my computer, all the CPU cores were utilized above 95% during encoding. I have used Homebrew on my Mac to install the FFmpeg package, whereas on my Android, I have used Termux.
The speed difference between desktop and mobile encoding was astounding! In the video, you will discover why there is such a difference along with what the future holds for H.265 software encoding on mobile devices.
Discussion on Doom9 Forum about x265 encoding speed on ARM processors:
https://forum.doom9.org/showthread.ph...
x265 Source Code:
https://github.com/videolan/x265
Nvidia NVENC hardware encoder quality test for H.264:
• Nvidia's RTX NvEnc is beyond impressi...
If you want to read or contribute, you can find this guide on:
https://quanticdev.com/articles/h265-...
"Hardware & Software" Playlist:
• Hardware & Software
- - - - - - - - - -
/ quanticdev
/ quantic_dev
https://quanticdev.com