+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: ffmpeg path not set (/t-solved-ffmpeg-path-not-set)
Pages:
1
2
ffmpeg path not set - 1RealOldGeek - 2023-12-11
Jellyfin 10.8.13
CentOS 7
Installed rmpfusion first then JellyfinServer, JellyfinWeb, Jellyfin . No error at any time. ( followed https://jellyfin.org/docs/general/installation/linux/ ) Verified ffmpeg at /usr/bin/ffmpeg.
Problem I cannot play any videos. Log file indicates can’t it find ffmpeg. How do I set the path in Jellyfin to the installed ffmpeg in version 10.8.13?
I found the following note at jellyfin.org/posts/jellyfin-security-and-you. Which might as we’ll be greek as the XML file contains no mention of ffmpeg. So how do I make Jellyfin work?
~As part of this release, we have made a change to the behaviour of the "FFmpeg path" GUI configuration option in Jellyfin. Specifically, in version 10.8.13, this functionality has been disabled, and will be fully replaced in the next major version (10.9.0). Editing this value in the GUI in 10.8.13 or later will not change it. In the short term, those wishing to make further changes to their FFmpeg binary must do so by editing the encoding.xml configuration file instead of using the GUI, and the server must be restarted after making the change.~
FWIW, The website is in grave need of attention. All forum post links return "The specified thread does not exist." Every link to a forum post is malformed and must be manually edited to work. IE https://forum.jellyfin.org/t-transcoding-4k-problems&highlight=“ffmpeg+path”
RE: ffmpeg path not set - Serge K - 2023-12-11
https://forum.jellyfin.org/t-ffmpeg-path-jellyfin-10-8-13
RE: ffmpeg path not set - TheDreadPirate - 2023-12-11
For security reasons, the ffmpeg path for the official docker image is not user changeable.
RE: ffmpeg path not set - 1RealOldGeek - 2023-12-12
(2023-12-11, 08:15 PM)TheDreadPirate Wrote: For security reasons, the ffmpeg path for the official docker image is not user changeable.
Does that mean that Jellyfin will not work on CentOS at all? So why release a RPM? Am I forced to use docker?
TIA
RE: ffmpeg path not set - Venson - 2023-12-12
> Does that mean that Jellyfin will not work on CentOS at all? So why release a RPM? Am I forced to use docker?
Its the other way around. You cannot change ffmpeg __on docker__. Every system where you invoke the ./jellyfin program directly, you can use the commandline argument to set the path to jf-ffmpeg
RE: ffmpeg path not set - 1RealOldGeek - 2023-12-12
I'm sorry I don't understand. Ive re-read the docs and find no mention of how to do that. Maybe I don't understand my issue not being able to play any video without Jellyfin complaining it can't find ffmpeg. Where can I can it in the docs to pass that in a command line?
TIA
RE: ffmpeg path not set - tmsrxzar - 2023-12-12
(2023-12-12, 06:12 PM)1RealOldGeek Wrote: I'm sorry I don't understand. Ive re-read the docs and find no mention of how to do that. Maybe I don't understand my issue not being able to play any video without Jellyfin complaining it can't find ffmpeg. Where can I can it in the docs to pass that in a command line?
TIA
a quick search on the google machine brought up this link https://github.com/jellyfin/jellyfin/pull/1017/files (*fixed link)
which seems to indicate that you can pass --ffmpeg and --ffprobe via the ENTRYPOINT in your docker
(adjust to your setup as needed)
RE: ffmpeg path not set - 1RealOldGeek - 2023-12-12
Is my posts being added to another thread. WTH is going on?
RE: ffmpeg path not set - Serge K - 2023-12-12
of course you can not find any info regarding ffmpeg in encoding.xml
you need to add some strings:
see this link and find EncoderAppPath and EncoderAppPathDisplay
https://mega.nz/file/hm1hxapS#D44nWETYWz-UKrMFAjVKC9uOZZeyPc3lJtHBqlgynrg
but there must be your pathes
RE: ffmpeg path not set - TheDreadPirate - 2023-12-12
There was another thread from a couple weeks ago that you responded to (I'm assuming accidentally) with the same/similar question.