mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Unable to transcode certain file to chromecast client with VAAPI HW encoding enabled #2258
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @richardbrodie on GitHub (Nov 11, 2020).
I have enabled VAAPI hardware decoding for H264 and hardware encoding, and tested a variety of files and clients and all seems to work well with one exception. I am unable to stream this particular H264 file to this particular client. If however I change to use software encoding, I am able to stream to the chromecast.
Media Info of the file
FFmpeg Logs
non-working chromecast client
working android phone client (set to 4mbps minimum 1080p quality)
Server System (please complete the following information):
Client System (please complete the following information):
@nyanmisaka commented on GitHub (Nov 11, 2020):
It's a known issue from AMD VAAPI driver.
Check here for a temporary solution. https://github.com/jellyfin/jellyfin/issues/2120
@richardbrodie commented on GitHub (Nov 13, 2020):
Disappointing, am I right in interpreting your last comment there as saying that my particular issue isn't going to be fixed?
@stale[bot] commented on GitHub (Mar 20, 2021):
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.