Closed blmhemu closed 2 years ago
Thanks for opening your first issue here! Be sure to follow the issue template!
Can you try mapping /dev/dri
and see if it works? The device ownership logic is already there
I tried to list all groups cat /etc/group
and was not able to see any group named render
.
And yes I tried mapping the /dev/dri folder and tried to play 4k hevc file. But it did not even open !
Don't worry about the groups, the container handles that automatically.
Do this for me on the host:
ls -al /dev/dri
Question : Are the VA API driver / libraries installed by default ? Will post the answers soon (My rpi takes a long time to boot)
Here are the details:
Yup, the container should handle the permissions properly.
The links you posted are very thin on the technical details. They just say it works on ubuntu server but not desktop (no clue why that would be the case), and no mention of any drivers.
Yeah the details are thin. But I am assuming for the moment that dtoverlay=vc4-kms-v3d-pi4
is where it gets the drivers.
Also not sure if it has to do anything with the docker BASE IMAGE
Because I am guessing ubuntu provides a special iso image for rpi.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
https://github.com/jellyfin/jellyfin-docs/pull/484
There is no VAAPI support on Raspberry Pi. VAAPI is only possible on Intel, AMD and Nvidia. The video core on Broadcom chips can be accessed via OpenMax and V4L2 until now.
Pi developers are trying unify decoder and encoder pipeline by using DRM PRIME. For more details see https://github.com/jc-kynesim/rpi-ffmpeg/tree/dev/4.3.1/drm_prime_1
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Closing as this isn't a container issue as confirmed by Nyanmisaka.
The guide shows that RPI currently supports v4l2 and OpenMAX. But the newer jellyfin release seems to support VA-API. It requires the user to be added in "render" group. Please have a look at https://jellyfin.org/docs/general/administration/hardware-acceleration.html and https://www.reddit.com/r/jellyfin/comments/jhwt49/vaapi_hardware_transcoding_working_on_the/ Looks like HEVC decoding is also supported !