Selfhosted

39435 readers

3 users here now

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!

founded 2 years ago

MODERATORS

[email protected]

Self-hosted Jellyfin CPU or GPU for 4K HDR transcoding? (lemmy.one)

submitted 6 months ago by [email protected] to c/[email protected]

61 comments fedilink hide all child comments

Hey everyone, I'm building a new server to run Jellyfin (with a few other services like Pi-hole) and I'm stuck on GPU or CPU transcoding.

My main concern is smooth 4K HDR transcoding for 1 stream. I've been reading mixed advice online – some people say a strong CPU with good single-core performance can handle it, while others recommend a dedicated GPU.

Should I focus my budget (~$1000AUD/$658USD) on a good CPU, or spend some of it on a dedicated GPU?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 6 months ago (3 children)

I've been trying to get this to work for weeks now. No dice, so far. Anybody know any useful guide on setting it up for a docker installation? Or does it only work if you install the.deb? I use Mint, BTW. Server is a Dell with a 9th gen i5.

[–] [email protected] 4 points 6 months ago* (last edited 6 months ago) (1 children)

I also struggled to get it to work with an Intel Celeron N5100. To get it to work I followed the instructions in the Jellyfin documentation. It seems like there are some additional steps for some versions of Intel CPUs, could it be that yours is affected? After enabling "Low-Power Encoding" it worked as expected.

[–] [email protected] 2 points 6 months ago (1 children)

Do you have it installed with docker?

[–] [email protected] 4 points 6 months ago

Yes, I have it installed as a Docker container in a Debian 12 machine. My Docker compose file is something like this:

  jellyfin:
    container_name: jellyfin
    image: jellyfin/jellyfin
    group_add:
      - "105" 
      - "44"
      - "102"
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/dri/card0:/dev/dri/card0

The group numbers were obtained following Jellyfin's documentation.

You also need to configure Jellyfin from Menu > Playback. In "Hardware acceleration" I selected "Intel QuickSync (QSV)". I have selected all but AV1 (not supported by my CPU) from "Enable hardware decoding from:" and from "Hardware encoding options:" I have enable all 3 of them.

[–] [email protected] 4 points 6 months ago (1 children)

What specifically isn't working? I've got Jellyfin running on Docker with transcoding from a Nvidia GPU.

I pretty much followed the documentation here: https://jellyfin.org/docs/general/administration/hardware-acceleration/nvidia. I can share my docker-compose for that specific use case if you'd like.

[–] [email protected] 2 points 6 months ago (1 children)

"jellyfin-ffmpeg5 deb package" is one bit I'm confused about. Is that part of the docker installation? If not, if I install the deb, can the docker installation use it? Do I have to configure something there?

[–] [email protected] 2 points 6 months ago

Yes it looks like it is included in the official docker image

[–] [email protected] 1 points 6 months ago

Check the Jellyfin wiki