After a lot of work, MusicMind for Plex v3.0 is ready.
MusicMind started as a natural-language playlist generator, but it has grown into something much broader: a local companion for understanding, exploring, and rediscovering a Plex music library.
What’s in v3
Docker & Portainer support
This was one of the most requested additions. MusicMind can now be deployed using Docker Compose or Portainer, with slim and full variants, so you don’t have to install all of the Python dependencies directly on your NAS.
Synapse audio analysis
MusicMind can analyze the actual audio files in your library with Essentia and measure:
-
BPM
-
musical key
-
danceability
That data can then be used directly when building playlists. So a request for an upbeat running playlist around 170 BPM can be based on measurements from the audio rather than AI guessing what a track sounds like.
DJ-ify
Generated playlists can optionally be reordered into a tempo arc — building toward a peak and then bringing the energy back down — using Synapse’s measured BPM and key data.
Dig into your Last.fm history
You can now search your own listening history with prompts like:
lastfm: played in december 2023
There’s also an On This Day picker for rediscovering what you were listening to around a particular date.
The Collection
The library statistics side has continued to grow, including views of your collection by era, country, artists, genres, and listening history.
And all the existing MusicMind features remain: natural-language playlists, specific genre enrichment, MusicBrainz artist metadata, listening-context playlists, library gap analysis, compilation handling, and detailed metadata filters.
The basic philosophy hasn’t changed:
Your library, understood — not guessed at.
The audio analysis happens locally. Your music isn’t uploaded anywhere.
Existing v2 users: please read before upgrading
There is one intentional breaking change.
The default database has been renamed from:
plex_music_brain.db
to:
musicmind.db
Do not simply start v3 against an existing v2 installation.
Run the included migration script first:
python3.12 migrate_v2_to_v3.py
The migration renames your existing database, updates DB_PATH in config.py, and backs up your configuration before making changes. It’s also safe to run more than once.
There’s an additional safeguard in v3: if MusicMind finds an old v2 database that hasn’t been migrated, it refuses to start rather than silently creating a new empty database and making it look like your library data disappeared.
Fresh installations don’t need to do anything special.
Full installation, Docker/Portainer instructions, and migration details are in the README.
website:
GitHub:
https://github.com/earthmonkey419/musicmindforplex
Thanks to everyone who has tried MusicMind, asked questions, reported problems, or suggested features. A surprising amount has changed since the first release in June.
Now go dig into your stacks. 
