Hey everyone,

I’m new here! I wanted to share a music search and discovery tool for Lidarr. It plugs into Spotify, TIDAL, Deezer, Last.fm, MusicBrainz, Plex/Tautulli, Jellyfin, and even some AI recommendations.

GitHub: https://github.com/aquantumofdonuts/mixarr/releases/tag/latest

Website: https://aquantumofdonuts.github.io/mixarr/

What it does:

  • Connects to Lidarr and analyzes your existing artists
  • Hooks into Spotify, TIDAL, Deezer, Last.fm, MusicBrainz, Plex/Tautulli, and AI services
  • Finds related/similar artists, new releases, charts, labels, playlists, etc.
  • Gives you a review queue to approve or dismiss discovered artists
  • Automatically adds approved artists to Lidarr with the profile you choose
  • Has a universal search and discovery interface across all services
  • Runs as a web app (Next.js frontend + Express backend) and plays nice with Docker

Why I built it:

I wanted one tool that I could point at my Lidarr library and get a steady stream of relevant artist recommendations.

Basically, make music discovery feel as automated and “infrastructure-y” as the rest of the *arr ecosystem.

Current status:

  • Working with Lidarr + Spotify/TIDAL/Deezer/Last.fm/MusicBrainz + Plex/Tautulli
  • Has subscriptions for different discovery sources (charts, playlists, related & followed artists, etc.)
  • Docker-compose setup available, plus local dev if you prefer
  • Early but usable; I’m actively using it myself and iterating

If you try it, I’d love to hear any feedback! Thanks!

  • Fmstrat@lemmy.worldEnglish
    3·
    16 days ago

    Nice. Couple of things:

    • The link in your post is broken 😉
    • Consider doing with Jellyfin anything you’ve done with Plex. Plex is on it’s way out, especially with Fediverse users.
    • aquantumofdonuts@lemmy.worldOPEnglish
      3·
      16 days ago

      I think the link is fixed now?

      I will definitely take the Jellyfin suggestion to heart. Mixarr is Plex-centric because that’s what I use, but I see that Jellyfin has a large share as well. Thanks for the suggestion!

      Edit: Added Jellyfin support. Four new subscription types in the “My Library” subscription preset group. You can pull and rebuild docker (or pull the latest image) to get the changes.

      • OR3X@lemmy.worldEnglish
        1·
        15 days ago

        Might also consider looking into Navidrome support. Not sure if it’s even possible but in my experience Jellyfin’s music experience is kinda crappy.

  • irmadlad@lemmy.worldEnglish
    2·
    15 days ago

    Connects to Lidarr

    So, I don’t run the ‘arr stack’, and am not interested in downloading, but I would like recommendations on new music. I am running Navidrome which scrobbles to Listenbrainz. How would Mixarr fit into this scenario?

      • irmadlad@lemmy.worldEnglish
        1·
        14 days ago

        Oh snap! Man, you didn’t have to do all that just for one dipshit who didn’t understand what Mixarr was. I should have done a bit more reading. I feel embarrassed. I will spin this up in an hour or two when I get my chores done. Thank you so much!

        • aquantumofdonuts@lemmy.worldOPEnglish
          1·
          14 days ago

          Haha no worries! It’s a useful feature. No reason to lock the subscription engine behind a Lidarr connection.

          But I think I will rest for a while now lol.

  • jabberwockiX@piefed.socialEnglish
    2·
    16 days ago

    This sounds great. I will have to check it out when I’m back home. I have been missing a music discovery tool as I am trying to avoid using any of the corporate overlord algorithm machines.

    • aquantumofdonuts@lemmy.worldOPEnglish
      1·
      16 days ago

      Awesome! I hope you like it. I’ve successfully converted my household from Spotify to Plexamp using this. Setup a few subscriptions, let the new artists and recommendations roll in, and you have a constant stream of new music.

  • Noggog@programming.devEnglish
    2·
    12 days ago

    Awesome!! I had been wanting to make something like this, but never got around to it. Excited to try it out tomorrow

  • SeventySeven@sh.itjust.worksEnglish
    1·
    15 days ago

    This is such good news to see this on my frontpage today, I’ll definitelybe giving this one a try later. Mad respect and appreciation for the amount of time this must have taken for you to make this. Thank you so much!

  • NarrativeBear@lemmy.worldEnglish
    0·
    15 days ago

    I am trying to put this behind Haproxy but not having much luck, I keep getting “client sent an HTTP request to an HTTPS server”.

    Anyone have a clue how to resolve this?

    I understand this image has its own caddy reverse proxy, not sure how to bypass that at the moment.

      • NarrativeBear@lemmy.worldEnglish
        0·
        15 days ago

        I am running in docker, I got 443 pointed at 3443.

        I saw the 3010 setting in the docs, i just can’t figure out if 3010 is pointed at 80?

        • aquantumofdonuts@lemmy.worldOPEnglish
          0·
          15 days ago

          3010 is the web port, on the web container itself (direct connection the the web ui). 3443->443 and 3080->80 are the Caddy ports, which also point to the web ui (just proxied through Caddy). Hopefully that’s not too confusing.

          • NarrativeBear@lemmy.worldEnglish
            0·
            15 days ago

            Understood, though it’s still kicking my butt TBH.

            Exposing port 3010:3010 seems to get me a connection refused. But I can still connect to port 3443:443. Both ports are set to TCP.

            Guess I’m just exhausted, will play around with it more tomorrow. Thanks for your help.

              • Statick@lemmy.worldEnglish
                1·
                14 days ago

                First, thank you for making this. Seems very useful… That being said I’m having the same issue, even after mapping port 80, it redirects to https/443 no matter what I do.

                services:
  mixarr:
      container_name: mixarr
      image: ghcr.io/aquantumofdonuts/mixarr:v1.1.0
      ports:
        - 3010:80 # Edit: change 80 to 3000 in order to bypass caddy in the container
        - 3443:443
      volumes:
        - ~/mixarr-data:/data
      environment:
        - SESSION_SECRET=$(openssl rand -hex 32)
        - FRONTEND_URL=https://my-domain:3443/
        - BASE_URL=http://my-domain:3010/
      restart: unless-stopped

                Edit: Just realized you have it using caddy, always, and it is set to redirect to 443. You should give people the option to run without caddy in the container. I have my own instance of caddy running, I don’t need it built in.

                That being said, changing it from pointing to port 80 and instead to port 3000 allows me to access it over http but ends up having authenticaton issues when trying to change settings.

                Edit 2: Oh there is a much more robust docker-compose file. I was just going based on the readme. Will give it a try a bit later.

                • NarrativeBear@lemmy.worldEnglish
                  2·
                  9 days ago

                  Thank you, your comment here helped me sort my issue out.

                  For anyone if you want to access this without the built-in proxy/caddy server set your ports in your docker compose like so.

                  • 3010:3000
                  • 3443:443 (this is the caddy port inside the container)