Comments

Replacing TV and movie streaming services is pretty trivial, and typically one of the first projects for any new self-hoster, but music streaming services are a whole different beast. There’s a growing need to replace the likes of Spotify, but there’s no one-size-fits-all solution, and maintaining an on-disk music library will always be a lot of manual work. That being said, I’ve put together a stack that I’m happy with for now, and there was some interest in the full details, so I’ll try to slap together a tutorial here.

  • bulwark@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    3 days ago

    I’ve been monitoring Lidarr on the reddit page and I think they might have fixed it. Beets replaces lidarr’s tagging and renaming function but as far as I can tell doesn’t have a plugin to monitor for new releases. I already had a docker app called rundeck that I use to launch scripts so it was easy to get it to launch beets to move the album into my library and fix any issues. It’s not 100% automatic, because sometimes beets isn’t certain it scraped the right album.

    • hosaka@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      That sounds like a good alternative for me. I didn’t use lidarr to pull in new releases, mainly to tag and organise the files on disk, I’d mostly import albums manually when I come across something I want. So I wanna drop an album in some import directory, get it tagged with listenbrainz data and placed in the right place. Is that achievable with beets?