Repository navigation
FAQ and Troubleshooting
No. Playlists come from database queries and the rules you set. This project purposefully does not make use of A.I. agents to generate playlist, I believe they are not needed for something this simple and are too resource heavy for most self hosters.
A.I. agents were used in the creation of naviList, with full human oversight and understanding.
The limit is a maximum. A playlist ends up shorter when your library doesn't have enough tracks that match. Check the count shown on each block in the builder. A block showing zero means its starting rule or conditions match nothing, or an artist name doesn't match your library. If you use Popularity or Studio and Live with a tier at 0%, it can also leave fewer tracks.
Unrated tracks count as deep cuts. If you set Deep cut to 0% and few tracks are rated, there's little to pick from. Check the Popularity line on the Services page. It needs a ListenBrainz token or Last.fm API key, and the ratings take time to fill in. See Popularity.
naviList prefers studio recordings, and decides what's live from MusicBrainz data or from the title and album text. A live track with an ordinary-looking title and no MusicBrainz data can slip through. Give it time after a library sync, because the live check runs in the background. See Studio and Live.
The artist name has to match an artist in your library. Check the spelling and try the name as it appears in Navidrome.
Only similar artists in your library count. If you own little of the artists related to the one you chose, you get few. A larger depth, such as Wide, helps. Also check that ListenBrainz is reachable and that artist IDs have been collected. See Similar Artists and Background Jobs.
Add TZ=Your/Timezone to the environment in your compose file, then restart. See Auto-Refresh.
A refresh or Regenerate rebuilds the playlist from its rules. Hand-added tracks are replaced. Turn off auto-refresh for that playlist, or keep hand-picked playlists as manual playlists. See Editing and Regenerating.
Navidrome and naviList need to share a folder. The folder naviList writes to (the Output path on the Settings page) must be the same folder as Navidrome's PlaylistsPath. See Navidrome Smart Playlists.
Open the Logs page, set the level to Debug, repeat the action and look for lines from sync, navidrome or the service's name. The most common causes are a wrong URL, a wrong password and an unreachable server.
In the folder mounted at /app/data, mainly navilist.db. Back it up before upgrading.
Yes. If there's an external playlist source or format you'd like supported, open an issue, or better, send a pull request.
Start
Building playlists
- Playlist Types
- Rules Builder
- Rule Terms
- Similar Artists
- Popularity
- Studio and Live
- Auto-Refresh
- Editing and Regenerating
Other playlists
Reference