logoalt Hacker News

ndriscollyesterday at 1:11 PM1 replyview on HN

Your player scans your library and indexes/sorts it however you'd like. I think this is how basically every player with a library function works? Like jellyfin loads my library in the same structure I've had it for 20 years, and it gives me various ways to view by name, artist, release date, rating, etc. and builds search indexes. I just point it to the roots of my libraries.

I said it needs a place to write playlists (or write access to your playlist folder(s)).

I wouldn't do it this way, but there can be more than one folder containing the same file (hardlinks).


Replies

giantrobotyesterday at 8:47 PM

> Your player scans your library and indexes/sorts it however you'd like.

Which means the concepts of files and folders becomes immaterial. If a music player is only interfacing with a database of music metadata it doesn't matter how the bytes on disk are organized.

There's a reason there's been 30+ years of file systems trying to tack on database functionality (BeFS, WinFS, etc) or over the top metadata indexing (Spotlight, Lucene, etc) to file systems. The files and folders abstraction is not sufficient for non-technical users in many cases.

show 1 reply