Re:Why I use Jellyfin for my home media library
by counttheforks on Thursday October 27, 2022 @07:07PM
(#33365245)
But I want to use the web client. Why is it inferior?
Re:Why I use Jellyfin for my home media library
by 3np on Thursday October 27, 2022 @07:21PM
(#33365376)
Typically because you are trying to play media with codecs that aren't supported by your browser, and transcoding is either not working or working suboptimally. Native clients (like MPV, VLC, or the desktop app) tend to have better codec support and support decoding the native media stream directly.
Some people work around this by making sure they only store supported codecs, either by being selective with media or offline transcoding (which can be instrumented with software like https://github.com/HaveAGitGat/Tdarr).
There's nothing "magic" here. Your options regardless of software are inherently:
1. Make sure to only store and stream supported media (as explained above)
2. Do the decoding and playback in a capable client (like mentioned above you can make it fairly seamlessly with the web client together with jellyfin-mpv-shim)
3. Live transcoding (may require tweaking drivers and codecs on your server; significantly increases server hardware requirements and load)
More info here: https://jellyfin.org/docs/general/clients/codec-support
Re:Why I use Jellyfin for my home media library
by counttheforks on Thursday October 27, 2022 @07:43PM
(#33365580)
How is any of that related to subtitles not working right in the web client? The media I download does not require transcoding.
The other subs-related annoyances (takes time to appear; transcoding/DS behave differently) appear in web client only and not when playing trough a "proper" player (mpv-shim/kodi/whathaveyou), which also support convenient timing adjustments. Maybe switching clients is a work-around that works for you. jellyfin-mpv-shim would be the smoothest if you just want to continue issuing local playback ("cast") from the web interface.