mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: Hardware encoding fails on macOS with Intel GPU #4720
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 @yaakovfeldman on GitHub (Mar 17, 2023).
Please describe your bug
I am running macOS Ventura on a 2012 mac mini with a Ivy Bridge cpu. This supports Intel QSV encoding for MPEG-2.
I get an error when enabling hardware encoding but if I edit the ffmpeg command (form the logs) to remove
-vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709,scale=trunc(min(max(iw\,ih*a)\,426)/2)*2:trunc(ow/a/2)*2,format=nv12"and the-hls_segment_filenamethen it works.On such old hardware getting hardware acceleration working is important because otherwise a single stream can use most of the cpu!
Is there any way to edit the command being passed to ffmpeg? I can live without the custom colourspace, and omitting the custom segment filename doesn't seem to cause any issues (the separate chunks are still created, they are just named
<output filename><chunk number>.ts.The ffmpeg command that didnt work can be seen below, but this worked:
Jellyfin Version
Other
if other:
10.8.9 (native binary download)
Environment
Jellyfin logs
FFmpeg logs
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@Ritchie1108 commented on GitHub (May 6, 2023):
maybe you have to choice "Apple Video Toolbox"
https://jellyfin.org/docs/general/administration/hardware-acceleration/#supported-acceleration-methods
@jellyfin-bot commented on GitHub (Sep 4, 2023):
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 master branch, 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.