Stick PC for a media client?

Submitted ⁨⁨6⁩ ⁨hours⁩ ago⁩ by ⁨eyesaremosaics@lemmy.zip⁩ to ⁨selfhosted@lemmy.world⁩

Are mini stick PCs practical to set up as a media player, eg with jellyfin? Some advantages are the small form factor that plugs straight into the HDMI port, and flexibility/privacy vs using a dongle from a shitty company like amazon/google/roku.

Are there any things to watch out for to ensure it has enough compute power and hardware decoding? I just want it to play HD video with a jellyfin app/browser page.

I’m assuming it’s no big deal to install Linux on (x86 hardware?), do you need to watch out for specific device support? Thanks

original

Comments

Sort:hotnew top

yaroto98@lemmy.world ⁨6⁩ ⁨hours⁩ ago
I found this one on amazon

a.co/d/05wDgslY

it advertises linux compatibility. So, I’d agree with you, installing shouldn’t be a problem. I’ve heard about a project called Plasma Bigscreen, might be exactly what you’re looking for. I’ve also heard flir remotes work pretty will with linux tv boxes. Those plug pcs have usb slots, you might want to figure out if you need an extension cable so the ir can reach the dongle.

original
- eyesaremosaics@lemmy.zip ⁨5⁩ ⁨hours⁩ ago
  Ok, I’ve been checking out some older ones for half the price (possibly used as well), the main requirement I’ve been checking is just hardware decoding, with a light weight Linux setup I think it should be sufficient.
  
  The remote is worth considering, I might look into Bluetooth or RF based approaches as they are a bit more flexible than IR with positioning. Or even phone app based methods are possible
  
  original
  - yaroto98@lemmy.world ⁨4⁩ ⁨hours⁩ ago
    Yea, with a full pc setup and OS I don’t think you’ll have a problem with watching media. Even if hardware isn’t available for your cpu (unlikely) software will be. In the jellyfin client you can change your player to vlc if you have any issues playing video.
    
    original
- yaroto98@lemmy.world ⁨5⁩ ⁨hours⁩ ago
  To also answer the transcoding issue, Jellyfin should be ablento handle it. I have had issues where the client thinks it can play a media stream so the server serves it, but the client fails to play it. I usually either download a different file or manually transcode it to a different filetype that I know the client can play. I wouldn’t think a celeron processor would have issues playing media. Those issues were on like firetv or roku embedded system boxes, not full pcs.
  
  original
AMillionMonkeys@lemmy.world ⁨5⁩ ⁨hours⁩ ago
I run an older Raspberry Pi (B?) with Kodi + Jellyfin on it as my client for my TV. I know Pis specifically aren’t a great value proposition anymore, but the hardware is really unimpressive and it works just fine - so you don’t need much.

original
- eyesaremosaics@lemmy.zip ⁨5⁩ ⁨hours⁩ ago
  Do you know what number model it is? I tried using an old 2B but it was too slow and doesn’t have hardware decoding as far as I can tell. I’ve heard you need around 4B for media playback, but the price is not so great for a simple use like this. Stick PCs seemed to have some cheaper options, including hardware decoding, with the advantage of plugging straight into the HDMI port
  
  original
  - cmnybo@discuss.tchncs.de ⁨2⁩ ⁨hours⁩ ago
    All of the Raspberry Pi models have hardware decoding. Even a Pi 1B will play a 30 mbps 1080p bluray rip. I used to run OpenELEC on a 1B. The interface on XBMC was really laggy, but h.264 videos played smoothly.
    
    You need a Pi 4 or newer for h.265 hardware decoding. The Pi 3 has enough power to software decode some h.265 videos.
    
    The video player you use needs to be compiled specifically for a Raspberry Pi for the hardware decoding to work though.
    
    original
  - AMillionMonkeys@lemmy.world ⁨3⁩ ⁨hours⁩ ago
    I’m pretty sure mine is a 2B as well, but I’d have to go digging behind the TV to know for sure. I know it’s not newer than that. It works fine for me running LibreElec+Kodi+Jellyfin, but I don’t play anything more complicated than 1080p h264. If you want HD or Atmos or whatever complications, yeah, you’ll want hardware decoding.
    
    original
    -> View More Comments
irmadlad@lemmy.world ⁨6⁩ ⁨hours⁩ ago
I don’t run Jellyfin, so take this as is. From what I understand tho, Jellyfin does take a fair amount of resources to run in an ideal situation. Meaning it takes some RAM for multiple simultaneous transcodes, several users, large libraries, etc. A lot of the cheaper Stick PCs come with less than stellar specs. The Stick PC I just randomly picked because it was 8 GB RAM is a MeLE Business Grade PCG02 Fanless N100 Mini Stick PC 8GB. IT retails for $350 USD. For half of that price, you could opt for an SFF Optiplex, bump the DDR3 RAM to max the mobo, and DDR3 is fairly cheap, and still have resources to run other Docker containers if you wanted. For example I run an Optiplex SFF with the i7-4790 chip and 32 GB DDR3 RAM. Currently I have 53 total containers running and it really doesn’t break a sweat. Total cost of the box plus RAM was about $175 USD.

If you are going for the portability aspect, that’s where I think a Stick PC would function best. All that being said, you have options just depending on what your criteria are for running Jellyfin.

original
- aBundleOfFerrets@sh.itjust.works ⁨6⁩ ⁨hours⁩ ago
  OP speaks of a jellyfin client, not the server
  
  original
  - irmadlad@lemmy.world ⁨6⁩ ⁨hours⁩ ago
    Ahh, I missed that. So that would explain all the downvotes with no explanations why. Thank you for bringing that to my attention.
    
    original
    -> View More Comments
Shadow@lemmy.ca ⁨6⁩ ⁨hours⁩ ago
As a media client, totally. Lots of people run jellyfin on Android TV sticks and things like that.

original