It's quite resource limited after allI bought a Raspberry Pi 4, 4GB recently to create my home server for Jellyfin. 147GHz (I have active cooling so not a problem) Moving transcoding folder off of the Pi's SD card and onto the external HDD with the video files. Intro. If you are not planning to run Jellyfin on a Raspberry PI, you can look into using Intel or Nvidia. Folder on server: /mnt/Data/rpibackup. If I understand correctly this is only supported on Ubuntu Server, however it doesn't specify which version (I assume 20. 0GB 1080p mp4 file. This decision was made because Raspberry Pi is currently migrating to a V4L2 based hardware acceleration, which is already available in Jellyfin but does not support all features other hardware acceleration methods. Usually Kubernetes distros require a ton of nodes, hardware resources, and configuration to get setup, but Microk8s can be deployed in about 2 minutes, and can be used in as small as a single-node cluster on something as light as a Raspberry Pi. When the container is recreated, necessary devices and drivers will be mapped in. I have a Roku Express 4K set up on my 1080p television. I wonder if hardware acceleration would work for the OrangePi5 using the linuxserver/jellyfin docker image, since it relies on V4L2 and by mapping the /dev. 5) in a docker container on Linux trying to use my Intel i5-9600K for Intel Quick Sync. sudo usermod -aG video jellyfin. This will run Plex great,. 7 i believe which i had just setup jellyfin using the docker container jellyfin/jellyfin. I have 12 users on it, with their watch status. Simple conversions from another hardware accelerated codec to another HWa codec will work at near real. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. Arch Linux The Extra repository contains builds for both jellyfin-server and jellyfin-web. I just have HDTV 1080p content or HEVC and I use only Direct play for all my users but my friends with a good internet connexion have a lot of lag. I will say that transcoding is way beyond what my mini PC can do, but the i5-6500T's hardware acceleration looks great for Jellyfin - both x264 and x265 encoding/decoding. The supported and validated video hardware acceleration (HWA) methods are: Intel Quick Sync Video (QSV) NVIDIA NVDEC/NVENC (NVENC) AMD Advanced Media Framework (AMF) Intel/AMD Video Acceleration API (VA-API, Linux only) Apple Video Toolbox (macOS only) Raspberry Pi Video4Linux2 (V4L2, Linux only) Enabling Hardware Acceleration for Jellyfin. What this translates to, in layman's terms: smooth video playback with low system resource. It will help with h264/AVC, but does not support VP9 or HEVC, so you'll have to use software decoding for those. Raspberry Pi; Micro SD. 04 on raspberry pi 4 8gb using jellyfin 10. My gpu is a GTX 760. Support for external libraries, map view on mobile app, video transcoding with hardware acceleration, and. zip; Usage Image Info. 265 hardware block is for decoding only - to encode video, for instance from the Raspberry Pi camera, you will continue to use H. Manually create a “jellyfin” folder and “cache” subfolder within your Docker shared folder. 0-1 armhf Jellyfin is a home media server. If not I would consider switching to Plex. It doesn't seem to happen when streaming to a. <p>This decision was made because Raspberry Pi is currently migrating to a <code>V4L2</code> based hardware acceleration, which is already available in Jellyfin but does not support all features other hardware acceleration methods provide due to lacking support in FFmpeg. 264 for playback on non-HEVC devices (Chromecast gen. like hardware transcoding and app downloads. Enabling hardware acceleration. Encoding is not a given. I had reached out to Jellyfin support and was told that my hardware was "crying". Raspberry Pi 4 OpenMediaVault 6, Docker, lscr. 2. . 9 on RPI 4 64bit RPIOS. Raspberry Pi 3/4 Ensure you increase the allocated RAM for your GPU to at least 128 (raspi-config > Performance Options > GPU Memory). 4. sudo systemctl enable ramfs. It may even struggle with multiple simultaneous users even if they are direct playing the media. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it. An LXC Ubuntu container on Proxmox, running on a Dell R720 with dual E5-2690 v2 cpu's and an Nvidia Quadro P1000. - Some container: Portainer, Jelly Fin, Jdowloader, Komba. Hello, I've been using jellyfin on my raspberry pi 4 and i noticed some bugs when using the OpenMAX OMX hardware acceleration, some files the playback work's flawlessly,. Hardware acceleration (HWA) includes hw decoding and hw encoding. The only time it ran (jf 10. Video Acceleration API (VA-API) is a specification and open source library to provide both hardware accelerated video encoding and decoding, developed by Intel. ). Be sure that under VA API Device there is the right device (/dev/dri/renderD128). (2 mechanical hard drives are connected to the 2 USB 3. Hardware acceleration should be working for the following platforms: VAAPI. Hardware acceleration: VA API VA API Device: /dev/dri/renderD128 Enable hardware decoding for: H264 HEVC VC1 . Ubuntu 22. 5. Others will correct me if I'm wrong, but the jellyfin docs for hardware acceleration make no mention of raspberry pi. Their claims are probably based on some sort of GPU assisted encoding and it'll take time for some driver to work its way down to ffmpeg. It seems that Jellyfin has dropped support for hardware encoding via OMX libraries as Raspberry Pi is migrating to V4L2. Click on Hosts > Proxy Hosts > Add Proxy Host. What you've described is setting Jellyfin for Hardware acceleration for playback. Playing recordings and also live TV works without problems. nfj25 commented on Dec 30, 2020edited. Navigate to Settings > Server > Transcoder to access the server settings. Raspberry Pi 4 VAAPI. I followed the instructions here…Jellyfin on Raspberry Pi4 Hardware Acceleration. UVD was introduced with the Radeon HD 2000 Series and is integrated into some of AMD's GPUs and APUs. Jellyfin on Raspberry Pi 4 Question. 36. This is a complete tutorial of how I finally achieved full iGPU passthrough to my Ubuntu 23. Hardware used- Board - Raspberry Pi 4B - 4GB (with heatsink, case and case fan) SD Card - Sandisk 16GB Class 10 HDD - WD Essentials 2TB . This would make sense as easyrider. x through the beta versions of it. As of Jellyfin 10. I am running jellyfin 10. 4. If you have some spare cash lying around and want to experiment, the Pi maybe OK. Odroid XU4 Armbian bullseye with Linux 5. BonziBuddy3153. 0 added full acceleration encoding and decoding support for the Pi 4, with LS supporting it in 10. Hello, I am currently facing the problem, that Jellyfin uses around 50-100% of the CPU while idiling. 5. 8 hardware acceleration on Raspberry Pi via OpenMAX OMX was dropped and is no longer available. Software Engineer at Raspberry Pi Ltd. I've chosen the option 'Full - decode, filters, encode'. The gpu on a rpi4 is not capable of hardware accelerated transcoding. Supports Windows, Mac OS, and Linux. Using the jellyfin-ffmpeg on a raspberry pi 4 works. com) EnableRemoteAccess. Still unresolved. The Jellyfin project and its contributors offer a number of pre-built binary packages to assist in getting Jellyfin up and running quickly on multiple systems. JellyFin Hardware Acceleration Not Working (Windows 10 | Nvidia GTX 1060 3GB RAM) Hello, I have installed JellyFin on a Windows 10 Server which is equipped with GTX 1060 3GB. I have a Pi 4 1GB running OMV 4 with an instance of Emby (from which jellyfin is forked) running in a docker container as my home media server. The new Proton VPN Linux app is officially out of beta! Immich - Self-hosted photos and videos backup solution from your mobile phone (AKA Google Photos replacement you have been waiting for!) - October 2023 Update - Support for external libraries, map view on mobile app, video transcoding with hardware acceleration, and more 🎉. I have a Roku Express 4K set up on my 1080p television. Tue Oct 27, 2020 9:50 pm. 11. We welcome PRs to the script for any other common derivatives, or you can use the steps below instead. I have an Intel Core i5-7600K Processor with Intel HD Graphics 630 which I would like to leverage for hardware acceleration if possible as I think it would work better than just regular software transcoding. Hardware acceleration for transcoding on Raspberry Pi 4 with Jellyfin in Docker I'm looking for a guide/solution to enable hardware acceleration on a raspberry pi 4. 3. It is a powerful device that can run various applications and operating systems. However, as the relevant section of the HW Accel documentation points out, only H. ago. Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media. MMAL/OpenMAX (Raspberry Pi) Hardware acceleration users for Raspberry Pi MMAL/OpenMAX will need to mount their /dev/vc-mem and /dev/vchiq video devices inside of the container and their system OpenMax libs by passing the following options when running or creating the container:2. Steps to Reproduce. This happens to me regardless of hardware acceleration options. . I´m also going to show you how to enable OMX ha. 1. ffmpeg has rkmpp built in. Spun up the docker container as described in readme; Made sure all mappings, etc. In this video I show you how install the Jellyfin media server onto your Raspberry Pi4. ago. #7. FBDEV and FBTURBO are not used in KMS. Video Decode and Presentation API for Unix (VDPAU) is. you may need to turn off Protection mode for hardware acceleration. Help with h264_omx encoding on Raspberry Pi 4. Help with h264_omx encoding on Raspberry Pi 4. Here's a snippet of my docker-compose, I'm using linuxserver's image: Kernel: Linux pi4 5. Kodi on Orange Pi 5 with GPU Hardware Acceleration and HDMI Audio. 70-nvidia. RPI is almost always idling - no load. Everything has been working perfectly until a few days ago and now the Roku will not. ARM Related Support - The Jellyfin project DOES support Jellyfin on a Pi4 and even allows some variations of Hardware Acceleration. Try older versions of the container, I had capability issues with specific versions of jellyfin-ffmpeg. yml (in your case portainer UI). However I'm not having much luck, as the 1080p x265 content stutters. ffmpeg -i video. 264, at 1080p30 max resolution. When playing 1080p files they jump, or stall. ". The Jellyfin team puts it best here: “As of Jellyfin 10. Both machines spend alot of time running "ffpmeg -analyseduration" when I start playing back a 1 GB mkv or mp4 file. The video must be encoded in H. I found a GT730 (or some of the other entry level models in each series) combine some transcoding power with low energy consumption. You can easily create a media server with hardware acceleration on your Pi4! It works pretty well and can even play 4k videos! Jellyfin is an amazing open so. I see that you found the way to get the CPU work with Plex. The Raspberry Pi supports hardware transcoding in Jellyfin, which helps a lot. To do that: Start the raspi-config configurator, typing in a Terminal: sudo raspi-config. To be able to activate the hardware acceleration, first we need to enable the 3D video driver (so-called Fake KMS), and then set the memory to e. Playback of media is fine, however if I need to rewind or fast. docker pull jellyfin/jellyfin. In this video, we are going to show you "Jellyfin Media Server Guide - Install, Setup, and Libraries using CasaOS on Raspberry Pi 4Proxmox is quite a steep learning curve, going the Docker route first might be easier. I'm looking to play x265 1080p video using a Raspberry Pi 4 4GB model as a server, streaming to a Chromecast. JF and Pi 3B, like running on rocks. Now my question is, if Jellyfin could. I believe this satisfies this feature request. 3. . Install Jellyfin on your system with the installation method for your platform. Desktop client using jellyfin-web with embedded MPV player. (assuming you have a Raspberry Pi)Jellyfin on Raspberry Pi 4 I'd just like to start this question off thanking everyone that has helped create Jellyfin, providing such an amazing service to the community for free. . For gstreamer I don't know, but for ffmpeg decoding or encoding use/force the codec: h264_v4l2m2m. 264. Try older versions of the container, I had capability issues with specific versions of jellyfin-ffmpeg. 28-odroidxu4. Everything is up and running, however I can't help but notice performance issues on the NAS with the Jellyfin server. I read it has hardware acceleration via rkmpp. Is the client or the server the Raspberry PI? There’s no hardware acceleration on MPV Shim on RPI so heavy CPU usage is typical. io. Jellyfin is descended from Emby's 3. Available for free at home-assistant. Hi all, I'm having a problem transcoding H. Hardware video acceleration makes it possible for the video card to decode/encode video, thus offloading the CPU and saving power. The CPU get the hit. The Pi 4 is certainly capable enough. nyanmisaka • 3 yr. Transcoding can be GPU accelerated as well, BUT you have to pay for Plex pass. ffmpeg -hwaccel d3d11va -i input. 0, as well as numerous day to day enhancements. If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Views expressed are still personal views. Created using a Turnkey Core base container and then just following the debian install guide. 04 VM guest (6 cores and 4GB mem) on Proxmox ASROCK i7-4770 Intel. H264 software encode can cope with 1080p60 relatively easily, with 4k currently hitting around 24fps. 2023-09-28, 05:22 PM. However I'm not having much luck, as the 1080p x265 content stutters. Run the Jellyfin server on your system and gain access to the leading free-software entertainment system, bells and whistles included. Everything is working great, but HEVC files pause to buffer frequently. Is there a device or home server that you recommend? Planning on having Ubuntu server + Jellyfin. Also followed the hardware acceleration guide for RPi 4 but i still get the same results. note. NVEnv/NVDec. I'm having trouble getting hardware acceleration working on the Raspberry Pi 4. Once your share server is configured, you can edit your /etc/fstab on the Pi to mount the shares on boot. io image and it seems to have worked fine. rules. Synology. This decision was made because Raspberry Pi is. To take advantage of Jellyfin hardware acceleration on the Raspberry Pi, you'll have to add the Jellyfin service user to the video group to let the Jellyfin FFMpeg process use the encoder: sudo usermod -aG video jellyfin sudo systemctl restart. Without that, hardware acceleration didn't work. NET Core framework to enable full cross. I also tested v4l2 (everyone says it's the future). AV1 encoding support in Jellyfin is planned in the future. Jellyfin movie library not displaying content: [email protected], the hardware decoding part in Jellyfin applies to transcoding operations. Steps To Reproduce. If I understand correctly this is only supported on Ubuntu Server, however it doesn't specify which version (I assume 20. 01 on the Pi. Hardware acceleration encoding and decoding support added for the RaspberryPi 10. . If you're getting stuttering playback, it's very often because your server is having to convert the video on the fly into a format your client (in this case your web browser) can playback. This decision was made because Raspberry Pi is currently migrating to a V4L2 based hardware acceleration, which is already available in Jellyfin but does not support all features other hardware acceleration methods provide due to lacking support in FFmpeg. Apologies if this question has been asked before but I could only find very mixed responses so was hoping to hear from somebody using a similar setup or that may know. You need to give the user that runs jellyfin access to /dev/dri/renderD128. Current Behavior. ffmpeg: hwaccel_args: preset-rpi-64-h264. Have triced changing the "VA API Device" from. Alternatively it's trivial to update a package inside the container, just open a shell inside the running container: sudo docker exec --user root -it jellyfin. 2. Looks like it's not a performance issue. You can add multiple tuners for each mux. If you want most support on clients (devices and software you use to watch Jellyfin content from) then i recommend using files that are encoded in H264 (AVC) for the video track and AAC for the audio. In this tutorial, we will explain how to set up an Orange Pi 4 with Armbian, connect to Ethernet, set up a user, find the IP address, and SSH from a Mac on the same WiFi. That's pretty much it. It uses a particular kernel call to try and get the list of memory pages to copy to the VPU. Steps to reproduce: Install tvheadend-git from AUR and configure with wizard, set channels up and configure specific jellyfin user. For UPnP to be enabled, both the EnableUPnP and EnableRemoteAccess settings must be true. This is what I did in my Proxmox container. It has cross-platfo. So, I have just started working on RPI projects. 5. 5 gb at idle. 0 on 2 platforms: Raspberry Pi 4 with 4GB mem and USB 3 SSD. Jellyfin and Raspberry Pi OS will use about 1. Tools > Preferences. Hardware acceleration users for Raspberry Pi MMAL. Jellyfin 10. 04 VM in order to enable hardware acceleration on Jellyfin. Raspberry Pi 3/4 Ensure you increase the allocated RAM for your GPU to at least 128 (raspi-config > Performance Options > GPU Memory). 4. Raspberry Pi 4 - Best Jellyfin Client For Diy And Foss Options. Next is to enable HWA. Using such hardware allows some operations like decoding, encoding or filtering to be completed faster or using less of other resources (particularly CPU), but may give different or inferior results, or impose additional restrictions which are not. 2 release and ported to the . Quick Start. the Pi likely won't be able to keep up, particularly considering hardware acceleration is currently off the table. How I enabled 3D hardware acceleration and 4k60fps video hardware acceleration on Chromium for Armbian 23. Marking a series as 'watched' takes upwards of 10 - 15 seconds to reflect. Im currently trying to get some 1080p to work flawless, but have not had success yet. Otherwise, I'd suggest the NUC or workalike, or the Dell SFF or USFF machines. Jellyfin's hardware settings are extensive, but a bit lacking in documentation. This decision was made because Raspberry Pi is currently migrating to a V4L2 based. Jellyfin was not increasing any significant CPU/IO/RAM load at any time. So my experience on running Jellyfin on Raspberry Pi has not been as expected, have tried multiple options and in need for some pointers as to what to do, or move ahead on this forced marriage. Good luck getting a Pi to transcode. . nfs-client: RPI with Raspberry Pi OS buster, 192. Memory usage continued to climb after scanning the libraries and no scheduled tasks were listed as recently running when I noticed it in the morning. This can often offload a lot of resource utilization, as the hardware. It just need a single commend to enable the V4L2 decoder. Raspberry Pi 4 OpenMediaVault 6, Docker, lscr. Hi all, I'm having a problem transcoding H. 264 for playback on non-HEVC devices (Chromecast gen. I am running it through a docker container and it runs quite well for being on a raspberry pi. With an Intel CPU, I'm guessing I want. But it does not really have a benefit, as there is still a CPU bottleneck with the current ffmpeg implementation. CPUs/GPUs) have some built-in functionality that can be utilized by Jellyfin to really speed up the process of encoding/decoding video. ago. They are ordered below from lowest to highest load on the server: Direct Play: Delivers the file without transcoding. Intel hardware acceleration is generally well supported on Linux. On 64bit Raspbian, I found the following hardware acceleration is available on ffmpeg of rpi's distribution RPi-Distro/ffmpeg. Here is mine for a DS218+, I use the GID of the VideoStation user which I believed to be authorized to access the graphic card. There are multiple versions implementing a multitude of video codecs, such as H. ago. deprecate Raspberry Pi OMX/MMAL hardware acceleration in favour of V4L2. (For more informations: jc-kynesim/hello_drmprime) sudo dtoverlay. Orange Pi 5 / 5B / 5 Plus ; Hardware acceleration with Chromium. Jellyfin Settings. It now also supports Wayland through dmabuf. I have always had hardware acceleration enabled using V4L2 as advised. Download Jellyfin 10. Failover server is a Raspberry Pi 3B+ running DietPi, 120mm fan in 3P printed micro tower, it also stays on all the time. 2 release and ported to the . To take advantage of Jellyfin hardware acceleration on the Raspberry Pi, you'll have to add the Jellyfin service user to the video group to let the Jellyfin FFMpeg process use the encoder: sudo usermod -aG video jellyfin sudo. I'm running Jellyfin (10. Jellyfin is descended from Emby's 3. If you like FOSS and DIY builds, undoubtedly the Pi boards make the best Jellyfin clients. 7GB per day. But in a browser, it has to be transcoded to Webm, which The Pi 4B will need hardware acceleration / OpenMAX to do. Official. I have been struggling with this issue as well. Go to Advanced Options > GL Driver. EnableRemoteAccess. Download latest Poky distro, meta-openembedded, meta-raspberrypi. 8. This would make sense as easyrider. 7. This is drastically different than Jellyfin, where Jellyfin requires a server (which can be set up on various devices (like a Synology NAS, Raspberry Pi, TrueNAS, Unraid, etc). (Raspberry Pi) Hardware acceleration users for. I will need to get iGPU access to Jellyfin for transcoding. I wonder if a similar solution would work with Jellyfin. According to the official documentation, there are samples on how to mount the GPU devices on docker to allow HW acceleration on a Raspberry Pi 4, so I was wondering if something similar can be done on an Orange Pi 5 with a clean Ubuntu server. 4/10. Best regards. I suspect the slow CPU performance during scan is because Jellyfin is trying to generate Thumbnail for the episodes ? So the initial run will be. My assumption was that with hardware acceleration transcoding would be delegated to the integrated GPU (a Kabylake 630) and not tax the CPU itself. Can't see or use full 1TB exfat USB drive in Samba on Raspberry Pi and macOS r/DataHoarder • Dropbox now limiting advanced plans to 1TB per month, 250GB per week, 35. open your new jellyfin server in a browser. Jellyfin is running on Docker Client: Docker Engine - Community Version: 20. 5 ( download from hub. How I enabled hardware acceleration by entering these commands: Install firmware-amd-graphics in OpenMediaVault, make sure to add all non-free repositories. Based on Plex Media Player. Well, I do have plugin section in my config. I use Jellyfin Media Player (desktop), Jellyfin (android), Gelli/Finamp (music in android), Kodi / Jellyfin TV App (android tv box). The only time it ran (jf 10. I have Jellyfin installed using a portainer on a raspberry pi 4 to manage my docker services. This page covers what you need to know in order to select appropriate hardware for a Jellyfin server and take full advantage of its features (e. Jellyfin is descended from Emby's 3. My main purpose was a. There were a similar bugs mentioned in #2493 and #2494. Link to purchase DS1621+ on Amazon. Here you will enter your subdomain and domain like the example below. I'm looking for a guide/solution to enable hardware acceleration on a raspberry pi 4 (Raspian Buster) with Jellyfin running in Docker. To enable the web UI after installing jellyfin-web, make sure to remove the --nowebclient option from /etc/conf. I have monitoring in place. The prerolls work fine when I watch through a browser or the Android app, but on the Roku app, it goes straight to. After looking around on the internet I found the SBCs from Pine64 (built around the RK3399 ARM processor). Introducing: Raspberry Pi 5. I have simply listed below, for the reference of. Simply using the web interface via Firefox almost works right out of the box, but leads to occasional stuttering and screen tearing. Docker Image: linuxserver/jellyfin; Supported. Hardware Acceleration Jellyfin supports hardware acceleration (HWA) of video encoding/decoding using FFMpeg . I'm running a Raspberry Pi 3, which is used primarily as a Plex media server. You can easily create a media server with hardware acceleration on your Pi4! It works pretty well and can even play 4k videos! Jellyfin is an amazing open so. Headless 32 bit Raspbian OS using server version 10. Orange Pi 4 LTS is a single-board computer that is an excellent alternative to Raspberry Pi. for the screenshot i remove the network information. I'm having trouble finding the correct settings for Jellyfin Hardware acceleration. I figure I might as well focus on one thing at. Yes. Running 10. The major highlighted changes are: numerous improvements to Hardware Acceleration (HWA), including: OpenMAX (Raspberry Pi) Hardware acceleration users for Raspberry Pi MMAL/OpenMAX will need to mount their /dev/vcsm and /dev/vchiq video devices inside of the container and their system OpenMax libs by passing the following options when running or creating the container: OpenMAX (Raspberry Pi) Hardware acceleration users for Raspberry Pi MMAL/OpenMAX will need to mount their /dev/vcsm and /dev/vchiq video devices inside of the container and their system OpenMax libs by passing the following options when running or creating the container: This is because some of these are hardware-dependent (if you have say Windows and Nvidia graphics, do the same check, for fun), and some of these depend on OpenGL 3. Overclocking to 1400Mhz seems to have helped, but. However it's very specific about what it works with, h264 has been the only thing it's worked for so far. On a fresh Kodi install on Raspberry Pi OS (32-bit or 64-bit), any HEVC video will play audio only, if not crash Kodi. We technically do support RPi transcoding acceleration using OMX and jellyfin-ffmpeg on armhf and arm64 (enable it in the hardware encoding menu), though I'm not sure how well-tested or performant it is (I haven't used it myself). 264 and VC-1. Exec into the container and install non-jellyfin-ffmpeg, then point the path in Jellyfin's GUI to the new non-jellyfin-ffmpeg path. I am using Hardware acceleration : None I am using Raspbian Bullseye which comes with a Chromium browser. 168. How to optimize Jellyfin for scarce resources such as Raspberry Pi 4. It should. If I turn off the hardware decoding and acceleration from the Web interface, which Raspberry Pi can't do, I see that these. g. 264 encoding and decoding are possible; notably NOT HEVC. Go into the addon settings and toggle openmax. Contribute to akkupy/Homelab development by creating an account on GitHub. Both of them need a GPU (iGPU/dGPU) to run. From what I've read, the x265 implementation is dependent on ffmpeg, which, at the moment, requires an video output,. Pi 4 4gb Server, serving x265 content. The Raspberry Pi is a dev board and has been around for some time. I haven't tried any super high bitrate files, but I. CasaOS App Store; CasaOS Custom Install App Jellyfin. there is no hardware acceleration. This is fairly taxing on the CPU however. Odroid n2 server. Any transformation of data or routine that can be computed can be calculated purely in software running on a generic CPU, purely in custom-made.