2 ms·
The problem with Armbian is, while it's neatly packed and made with a lot of care, you lose board-specific capabilities, esp. in Rockchip systems. Using Armbia
by bayindirh 2y ago
The problem with Armbian is, while it's neatly packed and made with a lot of care, you lose board-specific capabilities, esp. in Rockchip systems.
Using Armbian for OrangePi 5B means losing hardware accelerated video encoding, AI acceleration, etc. But, I bought the board for these features.
I'd either use OrangePi's own, short living Debian image with all the features or an Armbian build which I won't be able to update cross-release but will be supported and developed, losing all the differentiating features of the board.
There's no winning here. This is why Raspberry Pi is winning.
- rcarmo 2y agoActually, the new Armbian releases do have GPU support (I mention that in my piece).
- bayindirh 2y agoHow about video encoding? I want to use mine as an on demand video encoder for a custom project.
- einsteinx2 2y agoMaybe try reading TFA? There’s a whole section on transcoding.
- bayindirh 2y agoThe article states: Update: Like I mentioned above, in the weeks since I fleshed out this draft Armbian came out with an Ubuntu Noble version with improved MESA/VPU support, but I haven’t had time to test it yet. I’ll update this post when I do. Which is what I’m asking. The article doesn’t contain information on media transcoding with Armbian, and I asked the question to learn whether there is more info on that. Otherwise, OrangePi’s image already does what I want. Video encoding has a lot of patents attached to it, so the access to that IP block is not always open source due to plethora of reasons. It’s a very non-ideal situation for non-embedded use, hence the question.
- rcarmo 2y agoThe Jellyfin version I tested comes with an ffmpeg build with RK3588 support.