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.

  • Kelly Aster 🏳️‍⚧️@lemmy.worldEnglish
    6·
    7 months ago

    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.

    • StitchIsABitch@lemmy.worldOPEnglish
      2·
      7 months ago

      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)

      • Kelly Aster 🏳️‍⚧️@lemmy.worldEnglish
        2·
        7 months ago

        I don’t think Tailscale counts as a reverse proxy, but it does support HTTP/3 and QUIC so that suggestion may not apply here. Still, it might be worth double-checking to see if they are disabled. Also, have you tried disabling Tailscale altogether and connecting directly?