GitHub license Latest Tag Media Server Support: Jellyfin 10.11.8, Navidrome 0.61.0, LMS v3.69.0, Lyrion 9.0.2, Emby 4.9.1.80

Please vote for the AudioMuse-AI best functionality

AudioMuse-AI - Where Music Takes Shape

AudioMuse-AI Logo

AudioMuse-AI is an open-source, Dockerized environment that brings automatic playlist generation to your self-hosted music library. Using tools such as Librosa and ONNX, it performs sonic analysis on your audio files locally, allowing you to curate playlists for any mood or occasion without relying on external APIs.

Deploy it easily on your local machine with Docker Compose or Podman, or scale it in a Kubernetes cluster (supports AMD64 and ARM64). It integrates with the main music servers' APIs such as Jellyfin, Navidrome, LMS, Lyrion, and Emby. More integrations may be added in the future.

AudioMuse-AI lets you explore your music library in innovative ways, just start with an initial analysis, and you’ll unlock features like: * Clustering: Automatically groups sonically similar songs, creating genre-defying playlists based on the music's actual sound. * Instant Playlists: Simply tell the AI what you want to hear—like "high-tempo, low-energy music" and it will instantly generate a playlist for you. * Music Map: Discover your music collection visually with a vibrant, genre-based 2D map. * Playlist from Similar Songs: Pick a track you love, and AudioMuse-AI will find all the songs in your library that share its sonic signature, creating a new discovery playlist. * Song Paths: Create a seamless listening journey between two songs. AudioMuse-AI finds the perfect tracks to bridge the sonic gap. * Sonic Fingerprint: Generates playlists based on your listening habits, finding tracks similar to what you've been playing most often. * Song Alchemy: Mix your ideal vibe, mark tracks as "ADD" or "SUBTRACT" to get a curated playlist and a 2D preview. Export the final selection directly to your media server. * Text Search: search your song with simple text that can contains mood, instruments and genre like calm piano songs.

More information like ARCHITECTURE, ALGORITHM DESCRIPTION, DEPLOYMENT STRATEGY, FAQ, GPU DEPLOYMENT, CONFIGURATION PARAMETERS AUTHENTICATION and can be found in the docs folder.

The full list or AudioMuse-AI related repository are:

And now just some NEWS:

  • Version 1.0.2 introduces providers migration, multiple users support and the dashboard.
  • Version 1.0.0 introduces the Setup Wizard for an easy configuration with the web UI.
  • Version 0.9.6 authentication enabled by default. Read the AUTHENTICATION docs to know how to proceed.

Disclaimer

Important: Despite the similar name, this project (AudioMuse-AI) is an independent, community-driven effort. It has no official connection to the website audiomuse.ai.

We are not affiliated with, endorsed by, or sponsored by the owners of audiomuse.ai.

Table of Contents

Quick Start Deployment

Get AudioMuse-AI running in minutes with Docker Compose.

If you need more deployment example take a look at DEPLOYMENT page.

For a full list of configuration parameter take a look at PARAMETERS page.

For the architecture design of AudioMuse-AI, take a look to the ARCHITECTURE page.

From v1.0.0, only PostgreSQL and Redis connection parameters must still be configured via environment variables. All other configuration values are managed through the browser setup wizard and persisted in the database. For compatibility with legacy installations, environment variables are imported into the database automatically on first startup. The Setup Wizard is shown on clean installation as lending page and is also available later from the menu under Administration > Setup Wizard.

Prerequisites: * Docker and Docker Compose installed * A running media server (Jellyfin, Navidrome, Lyrion, or Emby) * See Hardware Requirements

Steps:

  1. Create your environment file: bash cp deployment/.env.example deployment/.env

You can customize the setup by editing deployment/.env before startup. As a minimum, it is suggested to change the default database password, but you can also override other PostgreSQL and Redis connection parameters if you want to reuse already existent deployment:

env POSTGRES_PASSWORD=your-secure-password

  1. Start the services: bash docker compose -f deployment/docker-compose.yaml up -d

  2. Access the application: Open your browser at http://localhost:8000

  3. Run your first analysis:

  4. Navigate to "Analysis and Clustering" page
  5. Click "Start Analysis" to scan your library
  6. Wait for completion, then explore features like clustering and music map

Stopping the services:

docker compose -f deployment/docker-compose.yaml down

Hardware Requirements

AudioMuse-AI has been tested on: * Intel: HP Mini PC with Intel i5-6500, 16 GB RAM and NVMe SSD * ARM: Raspberry Pi 5, 8 GB RAM and NVMe SSD / Mac Mini M4 16GB / Amphere based VM with 4core 8GB ram

Minimum requirements: * CPU: 4-core Intel with AVX2 support (usually produced in 2015 or later) or ARM * RAM: 8 GB RAM * DISK: NVME SSD storage

For more information about the GPU deployment requirements have a look to the GPU page.

Docker Image Tagging Strategy

Our GitHub Actions workflow automatically builds and publishes Docker images with the following tags:

  • :latest Stable build from the main branch. Recommended for most users.

  • :devel Development build from the devel branch. May be unstable — for testing and development only.

  • :X.Y.Z (e.g. :1.0.0, :0.1.4-alpha) Immutable images built from Git release tags. Ideal for reproducible or pinned deployments.

  • -noavx2 variants Experimental images for CPUs without AVX2 support, using legacy dependencies. Not recommended unless required for compatibility.

  • -nvidia variants Images that support the use of GPU for both Analysis and Clustering. Not recommended for old GPU.

How To Contribute

Contributions, issues, and feature requests are welcome!

For more details on how to contribute please follow the Contributing Guidelines

Star History

Star History Chart