+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: ffmpeg niggles (/t-ffmpeg-niggles)
ffmpeg niggles - lsces - 2025-02-19
I'm a little out of my depth here, and probably trying to be too clever. I have V10.10.4 running on the development machine from openSUSE and I think it's running with ffmpeg-4-4.4 and all seems fine.
I've installed it on the main server, but also downloaded 10.10.6 direct from Jellyfin and on the whole everything is working just by swapping the active directory ... except that some files will not play, and if I am looking at it right it's ffmpeg that is playing up.
I'm getting "Unrecognized option 'x264opts:0'."
I've switched back to the openSUSE 10.10.4 and the problem is solved, and I'm happy with that but I'd like to install the latter ffmpeg7 but not quite sure what the knock ons are. I should say that the server does not have an active desktop, being text only so I'm doing this via the command prompt. And I have not bothered with 'docker' at all on the servers which just have an nginx/PHP/Firebird stack and Plex running.
Jellyfin may still be playing catchup with Plex, but it does seem to have all that I need to simply switch off the Plex server.
RE: ffmpeg niggles - TheDreadPirate - 2025-02-19
ffmpeg 4.4 is super old. Additionally, jellyfin-ffmpeg is not a simple re-label. It is significantly modified and customized for improved transcoding performance. Jellyfin uses transcoding parameters that won't work with the standard ffmpeg.
If Jellyfin is the only app using ffmpeg, there is no concern about switching from ffmpeg 4.4 to jellyfin-ffmpeg 7.
You'd need to get one of the generic pre-compiled versions from our git.
https://github.com/jellyfin/jellyfin-ffmpeg/releases/tag/v7.0.2-9
RE: ffmpeg niggles - lsces - 2025-02-21
Still struggling with this, but I'm not pinning down the exact problem. I have two openSUSE Leap 15.6 machines both with a copy of 10.10.4 running and on the whole they mirror one another. The niggle is that SOME films are playing perfectly from the development machine but not from the main server. Or at least THAT was what I thought, but it seems it's just not consistent. I've built jellyfin-ffmpeg from source and have a working copy and can switch between ffmpeg4 and ffmpeg7 (Gave up on docker - it's too much trouble just for one program)
ffmpeg7 is giving me
Unrecognized option 'preset'.
while ffmpeg4 is still giving me
Unrecognized option 'x264opts:0'.
I can test this having copied the full command line from the log file and I'm not seeing any other problem.
But what is more confusion is that the problem film I'm testing with works perfectly on jellyfin on the smartTV ... it is accessing the same film from firefox that is throwing the error. So what am I missing here? I presume that it is 'TranscodeManager:' that is kicking in bu I should not need to change the coding at all as I have 1000BaseT on the local network ... I've not made this available off site yet.
(P.S. how do I get registered so I can add a proper sig section?)
RE: ffmpeg niggles - TheDreadPirate - 2025-02-21
Can you share the ffmpeg log so I can see what the ffmpeg command is? What is probably happening is that there is a parameter missing for "preset" or some other malformed ffmpeg command. Can you also upgraded to 10.10.6? I recall this was a bug in an earlier version, but I can't find the release not for it.
Regarding your signature. IIRC, you have to make a certain number of posts before that becomes available. I don't remember how many.