Selfhosted

49381 readers

630 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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

120

How big is your media library? (twun.io)

submitted 3 days ago by SpookyMulder@twun.io to c/selfhosted@lemmy.world

64 comments fedilink hide all child comments

Background: I've been writing a new media server like Jellyfin or Plex, and I'm thinking about releasing it as an OSS project. It's working really well for me already, so I've started polishing up the install process, writing getting started docs, stuff like that.

I'm interested in how other folks have set up their media libraries. Especially the technical details around how files are encoded and organized.

My media library currently has about 1,100 movies and just shy of 200 TV shows. I've encoded everything as high quality AV1 video with Opus audio, in a WebM container. Subtitles and chapters are in a separate WebVTT file alongside the video. The whole thing is currently about 9TB. With few exceptions, I sourced everything directly from Blu-ray or DVD using MakeMKV. It's organized pretty close to how Jellyfin wants it.

What about you?

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

[–] SpookyMulder@lemmy.4d2.org 6 points 2 days ago (2 children)

The 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.

[–] avidamoeba@lemmy.ca 3 points 2 days ago

All-in, I wanted something on the order of 1MB for client app, server, all dependencies, everything.

Okay that's gotta be radically different!

[–] dutchkimble@lemy.lol 1 points 2 days ago (1 children)

Does it not need to transcode then if it runs on cheap hardware?

[–] SpookyMulder@lemmy.4d2.org 1 points 1 day 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.