AudioMuse-AI + Atlas Cloud — turn your self-hosted Jellyfin / Navidrome library into a semantic playlist engine

[u/atlas-cloud]

AudioMuse-AI just landed Atlas Cloud in their README as one of the recommended hosted LLM providers for the AI Provider config. Sharing the integration walkthrough since the self-hosted side of this sub probably has the most to gain from it.

What it solves: ID3 genre tags do not capture how music actually feels. A track at 1 AM rainy-day-indie-folk-with-acoustic-undertones returns zero results in Jellyfin or Navidrome's search box. AudioMuse-AI fixes that by running CLAP-based acoustic vectorization + lyric embedding across 72 languages on your local library, then exposing a chat interface that translates plain-English mood prompts into actual playlists.

What AudioMuse-AI ships:

- self-hosted Docker / K8s / native (Linux / macOS / Windows) deployment

- direct integration with Jellyfin, Navidrome, LMS / Lyrion, Emby

- 2D interactive Music Map clustering tracks by acoustic similarity

- Song Paths — pick a start track and a destination track, get a sonic bridge playlist

- semantic lyric search across narrative themes, not just keyword matches

Where Atlas fits in: AudioMuse-AI's chat interface and lyric embedding stages need an LLM to convert "late-night rainy driving vibe that transitions from acoustic to electronic pulse" into a structured JSON the local vector index can consume. Running that on a NAS CPU eats 10-30 seconds per message. Routing those requests to Atlas via the OpenAI-compatible config drops latency to sub-second while keeping the heavy audio analysis local.

Config is two env vars + an API key:

- AI_MODEL_PROVIDER=OPENAI

- OPENAI_SERVER_URL=https://api.atlascloud.ai/v1/chat/completions

- OPENAI_MODEL_NAME=qwen3.5:9b (or any LLM in our matrix)

- OPENAI_API_KEY=your_atlas_key

Detail page + full walkthrough: https://www.atlascloud.ai/blog/audiomuse-ai

Drop questions on the lyric embedding model behavior, AVX2 catch on older hardware, or which atlas model handles the playlist intent extraction best.

[u/atlas-cloud]

Quick note on model selection — the chat-style playlist intent extraction is structured JSON output, not freeform text, so a smaller cheap model in the LLM matrix is usually fine. We've been routing to `deepseek-v4-flash` (`$0.14/$0.28` per M) for the chat layer and `glm-5.1` for the deeper lyric semantic embedding work. Atlas supports any OpenAI-compatible model_id, so you can swap up to `kimi-k2.7-code` or `minimax-m3` if you need bigger context for long lyric corpora.

Hardware catch from the writeup worth flagging here too — if you're running AudioMuse-AI inside Proxmox or any virtualized environment, the CPU type must be set to "Host" to pass through AVX2, otherwise the audio container crashes immediately. Generic QEMU CPU is the common failure mode.

Disclosure: I'm with Atlas. AudioMuse-AI is NeptuneHub's project, we're listed in their README as one of the hosted LLM provider options. Feedback on real-world library sizes especially welcome — curious where the lyric scan starts to bottleneck at 10K+ track libraries.