MFC Hardware acceleration doesn't work properly with 10bit HEVC

[tuxrinku]

Describe the bug
I'm using the Odroid XU4 arm board which is supposed to benefit from the MFC hardware acceleration, however, when enabled, MFC hardware acceleration is actually 50% slower than when hardware acceleration is completely turned off. I tried with an hevc 1080p encoded file.

System (please complete the following information):

• OS: LibreELEC
• Virtualization: Docker
• Clients: Browser
• Browser: Firefox 76
• Jellyfin Version: nightly (image from linuxserver.io)
• Playback: Transcode
• Installed Plugins: Anime / Kodi sync
• Reverse Proxy: nginx
• Base URL: none
• Networking: Host
• Storage: Local

To Reproduce

Enable hardware acceleration and set it to Exynos V4L2 MFC. Then try to play an hevc encoded file.

Expected behavior
The transcoding should be faster with hardware acceleration enabled

Logs
ffmpeg-transcode-80ceb825-c646-44be-acca-47b218d02ab7.txt

EDIT: Seems it's happening only with the 10bit HEVC files. It works with other HEVC files. Sadly I have mostly 10bit files.
EDIT: Still present in 10.6.1 using the official docker image

[eh8]

Same problem here, see attached log. Using an ODroid HC1 and HEVC transcoding doesn't work with hardware acceleration. Since this board lacks the muscle to transcode without hardware acceleration from Exynos V4L2 MFC and all web browsers do not currently support H.265 playback, I have no other means of viewing such content without other utilities like jftui or jellyfin-mpv-shim.

Where's a good place to start looking at this issue? It sounds like from various forum threads that ffmpeg doesn't support the necessary profile to decode 10bit H.265/HEVC. As a start, the option to enable 10bit decoding for HEVC should be disabled for MFC, since it won't load and gives users the wrong impression of its functionality at the moment.

[stale]

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

[Bolkarr]

It would be great if there was a fix for this

[stale]

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

[eh8]

This is still a living issue

[neo-neo1]

Anyone with a solution?

[eh8]

The only reference I could find to this problem was on an Armbian forum post.

Unfortunately I feel like this issue will not addressed in the foreseeable future, which is quite understandable given how ODroids are rather niche devices compared to the RPi community.

[jellyfin-bot]

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

[neo-neo1]

The only reference I could find to this problem was on an Armbian forum post.

Unfortunately I feel like this issue will not addressed in the foreseeable future, which is quite understandable given how ODroids are rather niche devices compared to the RPi community.

To call ODROIDs "a rather niche device" is a tremendously disingenuous statement. They use Amlogic SoC's such as S905X (and it's variants) which is THE MOST WIDELY USED SoC in Android based set top boxes. Additionally Amlogic SoC's are easily the second most used on SBCs. Thanks for your help none the less.