legacy-python-cli VS jellyfin-mpv-shim

I really tried to use PyInstaller and Nuitka to deploy a Python command line [1] to Windows, Mac, and Linux users. We couldn't get around some system dependencies like OpenSSL needing to be available and not broken on user machines. We ended up re-writing the whole program from Python into Go [2].

Using Go solved so many long-tail bugs for us and just simplified the whole process of shipping code to user machines.

[1] https://github.com/wakatime/legacy-python-cli

[2] https://github.com/wakatime/wakatime-cli

You could try Jellyfin-MPV-Shim but it’s not much of a UI and I don’t know if the playback will be any different from Jellyfin Media Player. Same thing about playback goes for JellyPlayer.

You mean something better than Jellyfin Media Player? It works pretty great for me on my Mac. Some people like Jellyfin-MPV-Shim but I don’t think it’s much of a UI.

As others have said, MPV Shim is another option on PC that also uses the same player as JMP. It has more options too that you use for the player like enabling shaders, video aspect ratio changes, volume gain changes, and so forth. Though it works as a hidden player that only appears when you cast to it.

Support IPv6 addressing with a protocol prefix (#306)

Fix endless video skipping with auto profiles. (#323)

I'm wondering if there is a bug in the Jellyfin server that is causing remote control connections to get lost. I had to put some really aggressive self-healing logic into MPV Shim to get it to stay connected reliably. This doesn't exist in web so JMP may suffer these reliability issues.

I use Jellyfin MPV Shim with uosc and thumbfast.

Jellyfin MPV Shim v2.3.1