Live data from Hacker News

Show HN: Simpler access to your music from the web that looks nice

github.com

1–10 of 32 posts

Re: Show HN: Simpler access to your music from the web that looks nice

#7
My current solution is Navidrome[0], which is a similarly lightweight music server (also written in Go and FOSS [1]), with a similary nice Web UI that works well as a responsive webapp / PWA.

Probably the biggest difference however is that, instead of a custom API, it supports the somewhat-standard Subsonic API, which makes it usable via a large collection of native clients. It also has a few more features like multiple user accounts, etc.

TBH, the overlaps are big enough that I'm not seeing the space for Euterpe. I suppose the installation is a little bit simpler if you don't use Docker?

[0] https://www.navidrome.org/about/

[1] https://github.com/navidrome/navidrome/

Re: Show HN: Simpler access to your music from the web that looks nice

#9
post #7

My current solution is Navidrome[0], which is a similarly lightweight music server (also written in Go and FOSS [1]), with a similary nice Web UI that works well as a responsive webapp / PWA. Probably the biggest difference however is that, instead of a custom API, it supports the somewhat-standard Subsonic API, which makes it usable via a large collection of native clients. It also has a few more features like multi…

Wow! Even the website looks the same. With the vinyl in the background and everything ;D

Re: Show HN: Simpler access to your music from the web that looks nice

#10
My problem is, all my music is:

a) WAV files with no internal metadata (there is a metadata file alongside though and a album-cover.jpg) (My ripping process pre-dates the ubiquity of FLAC playback support)

b) stored on a central file server currently only accessible via SMB/CIFS.

And what I want is some remote head-unit solution connected to [powered] speakers running a touch screen UI that presents the lot as a music jukebox.

There's a lot of Android and Linux based front-ends but most of them insist on only indexing locally stored music, and also only supporting file types with built-in metadata support, even though my music is stored in a logical Artist/Album/Track.wav folder/file naming convention.

So I'm stuck. It feels like I need to hand-crank my own solution... but that would take a lot of time I don't have, and never be as nice as some of these established open-source projects.

Post reply on HN