One caveat worth noting is that as soon as subtitle burn-in comes into play (especially at 4K), then you’ll easily hit 100% CPU usage and encounter stutters. It’s less of an issue if you’re using good clients and have control over that, but may be a problem if you’re sharing with your family and they have problematic playback clients.
Subtitles being “burned into” the frames instead of being a separate track, also known as hard-coded sometimes. This enables one to use subtitles on devices which cannot traditionally use them or screw up the display. But this means the server needs to re-encode each and every frame, which is a massive load on the server.
Hardware encoding is really great to have on a server. A lot of the time you wouldn’t even think about its existence in a desktop use case but if you monitor resource metrics on a server you can see how huge of a help it is.
I use an old 7700k for my media server. Took a little stint of configuration to pass the integrated graphics device from the Proxmox hypervisor, into the k8s worker node VM, and then into the Jellyfin pod, but very much worth it. Jellyfin x264 1080p transcoding now takes roughly a third of the CPU resources compared to doing it all in software.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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).
One caveat worth noting is that as soon as subtitle burn-in comes into play (especially at 4K), then you’ll easily hit 100% CPU usage and encounter stutters. It’s less of an issue if you’re using good clients and have control over that, but may be a problem if you’re sharing with your family and they have problematic playback clients.
what is subtitle burn-in?
Subtitles being “burned into” the frames instead of being a separate track, also known as hard-coded sometimes. This enables one to use subtitles on devices which cannot traditionally use them or screw up the display. But this means the server needs to re-encode each and every frame, which is a massive load on the server.
Hardware encoding is really great to have on a server. A lot of the time you wouldn’t even think about its existence in a desktop use case but if you monitor resource metrics on a server you can see how huge of a help it is.
I use an old 7700k for my media server. Took a little stint of configuration to pass the integrated graphics device from the Proxmox hypervisor, into the k8s worker node VM, and then into the Jellyfin pod, but very much worth it. Jellyfin x264 1080p transcoding now takes roughly a third of the CPU resources compared to doing it all in software.
deleted by creator