I am at my wits end with this and kindly ask for assistance.

I cannot for the life of me decide on how to set up my music library for the foreseeable future:

  • I started out having my library on my local pc, managed by MediaMonkey
  • As I bought a NAS, I moved my library to it and used Navidrome to stream it to an android app (Synfonium)
  • This meant that I’d lose the MediaMonkey management, but I thought for now I’d just manually transfer new songs/playlists over to the NAS when needed
  • As I started streaming with Navidrome, I noticed that the speeds were really bad and music often buffered (no idea why, Jellyfin works fine), so I cached all the songs offline
  • This made me think that I don’t even need Navidrome since at that point I could just copy the music files to my phone if they’re gonna be offline anyway, but then I don’t have a backup on the NAS

And now I’m kinda lost, unsure what the best way to handle this is. I’d like to keep MediaMonkey in the flow for library and playlist management, and streaming is pretty cool for those times where I’m listening on other devices. However, having the music on my NAS just seems to create an extra middleman. What’s most important to me is a smooth mobile experience, with a good UI and no interruptions, as that is where I listen to music 95% of the time.

How do you do it ? Any suggestions for how to future proof my setup without too much of a hassle (still kinda new to all this stuff)? For reference I don’t have a huge music library, maybe a few dozen GB, so it still fits easily on my phone.

Sorry if this was too long or doesn’t fit the subreddit, but I hope someone can enlighten me.

1 point

How much music do you have that you actually listen to a lot on your phone?

Most phones are over 200 gigs now so you should have plenty of room to just store it on your phone.

Also, when the bombs go off, wouldn’t it be nice to have your favorite song on your phone so you can listen to it one last time before the darkness creeps in?

permalink
report
reply
0 points
Deleted by creator
permalink
report
reply
8 points

I think you need to address your 4th bullet point and troubleshoot the buffering. That shouldn’t be happening. Are you streaming from outside your LAN when this happens or does it happen even when inside your LAN?

permalink
report
reply
2 points

Depends, I get two problems, one where the song will abruptly stop playing at about the 1 quarter mark (only skipping the song or restarting will fix), and the other being the generally slow and unreliable streaming. The former happens everywhere, even in the webUI in my LAN, and the latter only when out and about (Tailscale into my network).

permalink
report
parent
reply
1 point

Not sure on the first one. I’ve only had that happen on certain clients, but the fact that it happens in the web UI throws me for a loop. Have you dug into the logs when it happens? Looks like there is a debug option you can set in config. I’m assuming you don’t use tailscale to connect while on LAN? When troubleshooting I usually try to eliminate things one at a time. Disconnect from tailscale to eliminate that possibility, connect via IP instead of hostname to eliminate reverse proxy from the situation and see if it improves, etc.

Regarding out and about, what is your upload speed? Are you using direct play or are you transcoding?

permalink
report
parent
reply

the song will abruptly stop playing at about the 1 quarter mark (only skipping the song or restarting will fix)

You aren’t the only one to report halted playback in Navidrome. It appears to be a known open issue that goes back a few years.

One user in particular suggested last fall that the source of the bug may not be Navidrome’s fault. Are you using a reverse proxy?

For those that are still struggling with this issue, I can confirm that (in my case) the problem was related to the HTTP/3 QUIC protocol (not a Navidrome issue). As suggested by a few others in this thread, the issue can be addressed by ensuring that your reverse proxy supports and is configured for HTTP/3 QUIC, or by turning off the QUIC protocol on the client side (browser configuration), or by disabling HTTP/3 (with QUIC) feature on Cloudflare.

permalink
report
parent
reply
2 points

Interesting, I am actually not using a reverse proxy, just Tailscale (or does that count as a reverse proxy?), I had previously been using nginx proxy manager but ditched that because it became too much of a hassle (and everyone says it’s not secure enough)

permalink
report
parent
reply
11 points

Why not just use Jellyfin if you said it works fine?

permalink
report
reply
4 points

I meant streaming shows with Jellyfin works fine, so I don’t see why streaming music shouldn’t work at least as well. I don’t like using streaming clients such as Plex or Jellyfin for music, they just feel quite unpolished.

permalink
report
parent
reply
5 points

Plex has the PlexAmp

permalink
report
parent
reply
4 points

Symfonium works with Jellyfin. ;)

permalink
report
parent
reply
4 points

I thought its Finamp that works with Jellyfin. Is that just alternative of Symfonium?

I don’t stream music often, but never had issues with Finamp

permalink
report
parent
reply
4 points
*

I’m not familiar with MediaMonkey so this may not be an option but…

I’ve used Subsonic for a number of years as my streaming server. I don’t use tools to manage my files but one of the things I really like about Subsonic is that it will present the local file system structure to the clients (rather than only relying on ID3 tags). So if I create a directory called “1990s” it will show up in the Subsonic hierarchy (eventually - it scans periodically for new files).

I’m assuming you could use MediaMonkey to manage the files on your NAS over CIFS? Then Subsonic could just read the filesystem over NFS as well and serve what you have setup.

Subsonic clients offer the option to cache files or stream as well which is great for traveling.

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

Community stats

  • 4.7K

    Monthly active users

  • 3.5K

    Posts

  • 75K

    Comments