Right now I'm running Jellyfin on an old mini-PC with a Celeron J4105. That seems a bit underpowered. I'm using Linux Mint and the installation is with Docker. I'm looking to replace it with something better, so what would you recommend? My criteria are:

Easily available (second hand is fine)
Budget friendly (under € 500 would be nice)
Repairable
Upgradable (at least SSD and RAM)
Low power consumption at idle
Handles all the transcoding stuff without breaking a sweat
Plays nice with Linux

I guess my best bet would be some sort of second hand mini PC like they're being offloaded on eBay by the truckload. But I have no idea which particular models would be a good fit for me. I'm also fine with buying something new, of course.

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

[–] [email protected] 3 points 4 months ago (2 children)

Honestly, I'm not sure about the whole transcoding situation. I watch content on a ChromeCast hooked up to a 4k TV. With video in MKV containers I cannot fast forward or even pause sometimes. Transcoding those to an MP4 container in in Handbrake also didn't help. I don#t really know anything about all this stuff so I'm not really sure what to do.

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

That's imo the most important question. If you do not transcode the specs don't need to be crazy. Maybe there are test files somewhere. Mkv is judt a container, there could be anything inside of it. I play x265 and 264 in mp4. All devices support it and I don't need to transcode anything. No worries. Very quick.

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

There is a chart in the jellyfin docs that shows what codecs are supported which will help see why or when you need to transcode. I'm not sure how upto date it is, but it's an ok starting point.

If you are using handbrake to limit transcoding, bring the file to h264 or h265 and eAC3 for audio. Audio transcoding is very easy for most hardware, but video can be tricky. With that said, I don't have transcoding enabled for my setup and it's been working great for over a year now. For the few times I have audio codec issues, I'll just fix the file myself with ffmpeg and remux the file with the new eAC3 track.