5 hours ago
(This post was last modified: 5 hours ago by TheDreadPirate. Edited 1 time in total.)
You could modify the environment to override. I think $JELLYFIN_FFMPEG_OPT is defined in /etc/default/jellyfin.
But also give transcode throttling a try.
We used to make it easy to modify the ffmpeg path but, again, there was a not insignificant security vulnerability in ffmpeg. We backported the patch into jellyfin-ffmpeg, but then came the conversation about users running custom ffmpegs for the lulz. We figured that not making it easy would prevent "for the lulz" users from changing the ffmpeg path, but still allowing the change to be made via the environment file would allow power users to still make a change.
But also give transcode throttling a try.
We used to make it easy to modify the ffmpeg path but, again, there was a not insignificant security vulnerability in ffmpeg. We backported the patch into jellyfin-ffmpeg, but then came the conversation about users running custom ffmpegs for the lulz. We figured that not making it easy would prevent "for the lulz" users from changing the ffmpeg path, but still allowing the change to be made via the environment file would allow power users to still make a change.