mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-03-01 11:20:59 +03:00
Using jellyfin-ffmpeg with nightly docker image? #900
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 @retrostrobe on GitHub (Sep 10, 2019).
Hi all,
Is there a trick to use the latest version of ffmpeg from jellyfin-ffmpeg? When I pull the nightly using docker, the version that I get is 3.2. I'm running OMV on a RbPi3. Cheers.
@anthonylavado commented on GitHub (Sep 17, 2019):
@joshuaboniface Any thoughts?
@JustAMan commented on GitHub (Oct 10, 2019):
paging @nvllsvm
@retrostrobe how do you grab and launch your container?
@andrewrabert commented on GitHub (Oct 10, 2019):
@retrostrobe Are you running on ARM? jellyfin-ffmpeg is currently only available on x86_64.
Output from an x86_64 machine:
@retrostrobe commented on GitHub (Oct 12, 2019):
@nvllsvm Yes, I'm on ARM (RbPi3) and using OMV where I've used their Docker plugin.
I've installed jellyfin-ffmpeg outside of Docker (downloaded the Debian version from the repository). Trying to find ways to add those binaries into the container, or somehow 'link' to them. Being new to Docker, it's a bit of a trial and error.
@retrostrobe commented on GitHub (Oct 12, 2019):
I've solved this temporarily by opening up a shell session within the container, installed jellyfin-ffmpeg, and restarted. Running 4.2.1 without any issues. I know that I have to repeat this process every time I pull a new image – I'll keep on looking for a more permanent solution.
@cowbe0x004 commented on GitHub (Oct 25, 2019):
How did you install jellyfin-ffmpeg inside the container? It's giving me some dependency errors but I can't install those dependencies because they are not available.
@retrostrobe commented on GitHub (Oct 25, 2019):
@cowbe0x004 – I got those errors too. I think I fixed the dependency issue with
apt-get install ffmpegand possibly (can't remember) an installation of a static build of ffmpeg 4.x. Once that was working, jellyfin-ffmpeg installed without issues.Also, the jellyfin-ffmpeg installed the binaries to
/usr/lib/jellyfin-ffmpeg– had to copy them back to/usr/bin/Let me know how it goes.
@cowbe0x004 commented on GitHub (Oct 25, 2019):
@retrostrobe thank you. I didn't realize the docker image has different os so I was installing the wrong package. jellyfin-ffmpeg installed without complaining about dependency.
@JustAMan commented on GitHub (Oct 25, 2019):
@nvllsvm maybe we should just install
jellyfin-ffmpegpackage from our repos when building Docker forjellyfininstead of using a Docker build offfmpeg?@jannislehmann commented on GitHub (Nov 8, 2019):
I just tried this as well.
Using the jellyfin-ffmpeg on a raspberry pi 4 works. The docker bundled version does not.
Is there a newer issue to handle this, or could this issue be re-opened?
@JustAMan commented on GitHub (Nov 11, 2019):
I've re-opened this one.
@travisboss commented on GitHub (Dec 8, 2019):
Having same issue on a RPI 4 now. No fix seems to work.
@travisboss commented on GitHub (Dec 10, 2019):
Attaching transcode log. I was able to get jellyfin-ffmpeg install inside the docker but still cannot play anything that needs any sort of transcoding on a RPI4 using OMV.
Here is the logs: https://pastebin.com/XnBiux3T
@jannislehmann commented on GitHub (Dec 10, 2019):
@travisboss the log still says something about ffmpeg 3.*, which means that you are not using jellyfin-ffmpeg but the pre-installed one.
@retrostrobe commented on GitHub (Dec 10, 2019):
By default, jellyfin-ffmpeg installs to
/usr/lib/– make sure you copy the binaries to/usr/bin/as per my original comment: https://github.com/jellyfin/jellyfin/issues/1730#issuecomment-546161109@travisboss commented on GitHub (Dec 10, 2019):
@Cludch @retrostrobe I cp -r the jellyfin-ffmpeg/ to /usr/bin should I just copy the entire folder jellyfin-ffmpeg and switch to that folder in jellyfin?
[2019-12-10 07:47:34.378 -06:00] [ERR] Error processing request: "A task was canceled." [2019-12-10 07:48:34.913 -06:00] [INF] Attempting to update encoder path to "/usr/bin/jellyfin-ffmpeg". pathType: "Custom" [2019-12-10 07:48:34.932 -06:00] [ERR] FFmpeg validation: The process returned no result [2019-12-10 07:48:34.934 -06:00] [WRN] FFmpeg: Custom: Failed version check: "/usr/bin/jellyfin-ffmpeg/ffmpeg" [2019-12-10 07:48:34.957 -06:00] [INF] FFmpeg: Custom: "/usr/bin/jellyfin-ffmpeg/ffmpeg"This seems to happen when I change to the jellyfin-ffmpeg folder.
@jannislehmann commented on GitHub (Dec 10, 2019):
Just reference the new binary within the jellyfin web interface.
@travisboss commented on GitHub (Dec 10, 2019):
@Cludch Thanks, I did that and get this result in my logs it seems to not be able to verify the version of ffmpeg?
@jannislehmann commented on GitHub (Dec 10, 2019):
I have no test system as of right now.
Could you run
/usr/lib/jellyfin-ffmpeg/ffmpeg -versioninside the container?@travisboss commented on GitHub (Dec 18, 2019):
@stale[bot] commented on GitHub (Apr 16, 2020):
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.