Also usually the performance of platforms is good enough for audio transcoding to be executed in software. Meaning encoding audio shouldn’t be a problem.
More modern open codecs like libopus provide even better compression without being affected by any patents. The patents protecting MP3 and AC3 have expired some time ago. A lot of codecs today can be transcoded without paying any licensing fees. The software and APIs available are licensed under varying open source licenses which could have an effect on ones personal project depending on its licensing model. Many codecs are patented and require license fees being paid. When working with audio and video one also has to consider the legal aspects. To get the most annoying aspects of this topic out of the way, let’s directly start with those. That’s also where I started off, with the investigation on how to make use of hardware video transcoding on the mentioned platforms. Plex does not support hardware transcoding on the Raspberry PI 4 and on AMD graphics hardware running Linux. The reason behind this is to support hardware platforms which are not supported by Plex. I was starting with investigations on how to build a Plex alternative optimized for the Raspberry PI 4 and other efficient x86_64 based platforms. Whenever a project starts with the thought “How hard can it be?”, it usually turns out much more extensive than initially estimated. The Raspberry PI 4 features a hardware video encoder for h264 and decoders for h264 and hevc.
0 kommentar(er)
