Does it not need to transcode then if it runs on cheap hardware?
Comment on How big is your media library?
SpookyMulder@lemmy.4d2.org 4 days agoThe short answer is because it’s a fun project, and I wanted to see if I had it in me to make exactly the media server I want.
The longer answer is that I wanted something dramatically and fundamentally different from what either Jellyfin or Plex have to offer.
- Can run without breaking a sweat on junk/old/cheap hardware like a Raspberry Pi or old laptop.
- Can be safely Internet-facing – no anonymous access, and no web-based admin features or API.
- Hyper-lean and minimal. All-in, I wanted something on the order of 1MB for client app, server, all dependencies, everything.
I don’t see either of those goals happening with a contribution or fork, because achieving them would require some dramatic feature deprecation.
dutchkimble@lemy.lol 3 days ago
SpookyMulder@lemmy.4d2.org 2 days ago
Yep, transcoding is the main reason I had to buy any new hardware when getting my library going with Jellyfin.
For me, the main draw of Jellyfin wasn’t the transcoding. It was being able to browse and stream my library from anywhere. My partner and I would alternate weekends hanging out at each other’s places, and we just wanted access to the library from wherever we were and whatever device we were using.
I was willing to put up with weeks of encoding to get everything into a web-compatible format. But that’s just me and I know it’s not for everyone. I’m curious where the palatibility for that is on the spectrum more broadly.
avidamoeba@lemmy.ca 4 days ago
Okay that’s gotta be radically different!