A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
The Android client seems to have dropped a few player engines in a recent update. Previously there was an option to use libvlc, omxplayer or a third option that I can't recall. Seems the developer opted to go with the worst option.
The AndroidTV app can use external players such ss VLC. I went with kodi as a client instead.
I see, thank you 😊
It's not an issue, it's expected behavior for transcoding when subtitles are in the original format.
You can disable subtitles burning while transcoding, or you can try and find a different client that will use subtitles from a file, but it's probably going to be hit or miss, and require a bunch of upfront work.
I've found that as well with some files. At first I thought the issue was with the jellyfin instance had not enough capabilities, but after trying the same file with its subtitles, it worked on any other client: flatpak, web, and regular android. So for me it is the chromecast/androidtv device, so I am now looking what to replace it with