Jellyfin freeze on M1 Mac mini

[Gismo]

Hi, 
I'm still struggling with an hanging server since I upgraded from a Mac mini 2012 to a Mac mini M1 16gB with Ventura The only way is to kill the server via Activity monitor. 

I also tried to install a fresh version and add all my files again to the server

I add the last few hours from my debugging log and I hope you can help me, because it's really frustrating! But I really love the project and I'm really thankful for the really hard work from the dev team.

[sevenrats]

I don't know all the details, but its not terribly surprising that this doesn't work. Jellyfin needs to be built for this architecture directly, and, I suspect running the x86 ffmpeg through the Rosetta layer is causing this issue, and this is sorta corroborated by the fact that your log ends during a transcode.  If you have a bit of grit, my next step would be to try using Vargol's native builds of ffmpeg, and swapping out the x86 ffmpeg binary with a native built one. https://github.com/Vargol/ffmpeg-apple-arm64-build

[Gismo]

Hi,
thanks for the very quick response! I'll give it a try the next days because I'm traveling for business at the moment. I also saw that other logs stopped during other ffprobe things like checking the media files and so on so would make really sense.

Do you have tips to avoiding issues? Or only compiling it and change it with the x86 version?

[sevenrats]

ive since received reports in chat that the entire application is working on apple silicon through rosetta, ffmpeg and all. I can't confirm or deny either way. Maybe specifics about your platform will help get to the bottom of the issue.

[Gismo]

Ok good to know, I have a native ffmpeg binary and it seems that its working better. But I wonder if i should also change ffprobe, because this is also a x86 binary.
Do you know where i can set the path for it? I would to try a arm binary for that.

if no specific way to configure the only idea would be to use a system link to the arm binary, but then after every update of the app i have to create a new system link.

As requested my setup is MacOS 13.6.4, M1 Mini 2020 16GB ram and 256 SSD.

[cashewtree]

I launch Jellyfin on my M1 ARM64 using a Properties list file which sets the path.
The Plist is here: https://github.com/allanpeda/jellyfin-he...yfin.plist

I also have a monitor that checks site response and restarts it if it hangs. It seems that simply refreshing has kept things working, as the PID is constant.
https://github.com/allanpeda/jellyfin-he...in-monitor

[Gismo]

This is also a good idea.

But I think I have the solution.

Since I replaced the ffmpeg with a arm64 binary and now the ffprobe with a arm64 binary it’s really stable now. No freeze since more than a week. In the past this was not possible. Unfortunately there is no path for ffprobe to edit so I used a system link to link the ffprobe from the application.app to my arm64 binary.

I hope this can help others till a real arm64 build will released.

[ThijmenDam]

Facing the same problem, and currently building the custom ffmpeg binary. However, I’m not sure how I can properly replace the binary that is included with Jellyfin server. Would really appreciate some help if you have the time.

[TheDreadPirate]

You wouldn't need to replace it. You would stop Jellyfin and edit encoder.xml (encoding.xml?) located in ~/.config/jellyfin/ and change the ffmpeg path to the custom ffmpeg.

[gnattu]

Jellyfin 10.9 will be available with native Apple Silicon support. If you are brave enough then you can help test the unstable builds now: https://jellyfin.org/docs/general/testing/server/macos

Please do note that the first unstable build still requires you to use the web GUI or edit the config file manually to locate the ffmepg binary, because the config file will override the -ffmpeg cli parameter. This is going to be changed in later builds.