this post was submitted on 30 Jan 2024
77 points (96.4% liked)
Technology
59135 readers
6622 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Jellyfin server itself isn't all that intensive. My "server" is running on a 13y/o low-end desktop CPU (Pentium E5800, in case you're curious). However, if you noticed your laptop struggling, as others have pointed out, that's probably when it was transcoding. While I want eventually update my server with transcoding hardware, I just disabled transcoding completely for now, and it's pretty workable.
What's the point of transcoding for local serving?
If the client can’t play the codec because of some limitations, you are required to transcode. You can, of course config *arr services to pick only wanted codec, or skip "bad" codecs
Interesting. I think ccwgtv can read h264 and h265, I guess av1 would be a "bad" codec then?
It depends on device, my apple tv on my TV screen has sometimes problems with specific audio channels as well as with some 4k HEVC HDR files. Most it is performance of the device running the client, or it can also be some licensing stuff. On Apple TV, jellyfin uses the the video player provided from apple, I assume, at least in plex it is like that. This comes with the limitation, that some codecs are supported by apple.
To be fair, that laptop is running windows in all its bloated glory and that probably didn't help