No, that is counter intuitive. It may appear more expensive at first, but on the long run it is a lot more cheaper. It avoid vendor lock-in, recurring increase of dev costs and licensing and lots of other plagues of closed proprietary development like blackbox development and justification of hidden complexity as a driving factor on costs. I worked with legacy closed proprietary sw development and lock-in combined with legacy complexity made man-hour costs exorbitant. These are partially solved by open-sourcing, as kicking out a team and putting a new one is easier, but most importantly transparency as a driving factor on quality of development.

https://github.com/jellyfin/jellyfin-web/issues/4346

Lol at people down voting without a clue.

Anyway, that issue is 1 year old, and subtitles for some reason just keep getting worse with each update. It is not being taken seriously.

It is so easy to reproduce that there must be something more involved to it, explaining why some people dont have the issue.

I tested and validated with these clients: web, roku, android, android-tv, fire and LG

All have the same issue. So maybe some combination of factors with server.

The bugs are different depending on the media, sometimes delayed subtitles and most of times no subtitles at all. Also, trying to switch subtitles to other languages sometimes just dont take effect unless the playback is restarted. Anyway, it is baraly usable.

I really like Jellyfin and push for it, but since last release, it became barely usable. Unfortunately, it made me and all my users switch to Plex again. Where they preferred to buy the respective Plex clients instead of dealing with Jellyfin issues. It is sad, it could be money donated to Jellyfin at some time.

Seriously, if Jellyfin doesn’t fix all subtitles issues with their clients, it will be really hard to be taken as a serious competitor in the area. I hope they take this issue seriously and fix it asap before further damage to the project happens.