3 ms·
I've setup jellyfin on my media server but I barely use it because the web player bugs make it unusable for me. I think most issues are due to the fact my hardw
by ajnin 5y ago
I've setup jellyfin on my media server but I barely use it because the web player bugs make it unusable for me. I think most issues are due to the fact my hardware is underpowered for the task, and the player gets confused when the server replies come slow and not in the same order as they were requested. In practice subtitles go out of sync regularly, I get "codec not supported by browser" messages with the actual video playing fine behind it when seeking and frequently enough to make watching videos too annoying to bother.
There are also other annoyances like the player forgetting my subtitle selection when jumping to the next video of the same season of a show.
There's also no quality setting that is just "stream the source file directly". It seems to always want to transcode when embedding subtitles, which I guess is done by ffmpeg on the server but is really the player's job.
I know they're working on a new player, though it's not included in jellyfin yet.
- jeroenhd 5y agoIn my experience, the "codec not supported by browser" error generally means that transcoding either failed or stalled. I get the error message when ffmpeg dies in the middle of a transcode myself. The transcoder still has the file cached on disk as far as it has transcoded it, but Jellyfin notices that the process has died and throws errors. I don't think a new player will fix that issue, it's usually a resource problem on the server side. There is a "stream the source directly" option, it's the default even, but only when it's possible to do so (i.e. the media is in a streaming container and not AVI or DivX). You can copy the download URL and paste it into your favorite native player if you want to force it, but that will probably lead to a full file download if the web player doesn't stream the file already. The only way I can think of to avoid this issue is to pre-transcode the media on your NAS to a streamable format. As for the subtitles, I'm a little annoyed as well that the setting doesn't always stick (it works sometimes, which is even worse). I've never had desync issues though, that's probably more of an issue with the transcode lagging and confusing the player or just mismatched subtitle files.
- klahaha 5y ago> subtitles go out of sync regularly can be problem with subtitle source? > "codec not supported by browser" probable problem with browser not jellyfin? > There are also other annoyances like the player forgetting my subtitle selection when jumping to the next video of the same season of a show. +1 > There's also no quality setting that is just "stream the source file directly". It seems to always want to transcode when embedding subtitles, which I guess is done by ffmpeg on the server but is really the player's job. Direct source file is download button it can play in vlc, or can use FTP. why embed subtitles? here i think jellyfin use external track for subtitle (default parametres)
- 3np 5y ago> "codec not supported by browser" Unless you're very specific and consistent with your source media codecs, I highly recommend using jellyfin-mpv-shim when streaming from the browser. You just start the headless client wherever you want to play and it comes up as a "cast target" from the icon in the top right. Much better performance and codec support. MPV also has great subtitle control and caching. https://github.com/jellyfin/jellyfin-mpv-shim https://github.com/jellyfin/jellyfin-mpv-shim Also, if you haven't, it may be worth updating to the latest point release. There have been a couple of bugs that have come and gone but I think it's in a good place right now.