You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: No music files displayed due to a few failures #61
Hey, I was looking forward to try out Tagr today but couldn't import my music library.
I've mounted two directories from the host /music and /audiobooks - only the music one not rendered in the list although I do see the genres being picked up in filter by genre field.
I could see tagr.db picking up the files and the count is 717 in songs table.
I couldn't find more information in podman logs about what went wrong with the failed files.
Thanks, that narrows it down a lot. "All Folders" queries every song, while the folder view filters by the exact stored folder path — so the path Tagr saved while scanning doesn't match the /music it's asking for when you click the folder. Something's off in how that path got stored.
Could you check:
In "All Folders", click any song that lives directly in /music and look at the file path shown in the detail panel on the right. What does it say exactly?
Or straight from the DB: select folder_path, count(*) from songs group by folder_path limit 20;
Your exact MUSIC_FOLDERS value (quotes, slashes, everything) and the full podman run / compose command, including the volume mounts.
When you click the music folder, the URL of the request in DevTools → Network that starts with /api/songs/ and its response body.
If the stored path turns out to be anything other than /music (a symlink target, a relative path, a double slash…), that's the bug and I can reproduce it from there.
@suitux I could reproduce it with v1.15.0 (the code is the same on main), and the stored path is fine. It's the routing.
With MUSIC_FOLDERS=/music,/audiobooks both root folders have a single path segment. The folder view requests /api/songs/music, and Next.js sends a single segment to /api/songs/[id] rather than the catch-all /api/songs/[[...path]]. That route answers 400 Invalid song ID, so the list stays empty and shows ? files. "All Folders" works because it requests /api/songs without a segment, and deeper folders like Albums/… work because they have more than one. A subfolder named like a song sub-route, e.g. /music/audio, fails the same way.
@offensivedev you can confirm it in the browser while logged in: http://<your-tagr>/api/songs/music returns {"success":false,"error":"Invalid song ID"}.
I've opened a PR with a fix, it's linked above. Until it's released, this works with v1.15.0 (tested): drop MUSIC_FOLDERS and mount both folders under /music, then run a full scan.
The 16 "Failed to read metadata" errors are a separate thing: Tagr couldn't parse those files at all. If you can share one of them, or the output of metaflac --list or ffprobe for it, that would help to find out why.
Thanks for confirming! That matches my reproduction exactly. #62 fixes it; until it's released, the workaround above (both folders mounted under /music, no MUSIC_FOLDERS) gets you going.
Activity
offensivedev commentedon Oct 23, 2026
Update: tracks do show up in
All Foldersbut they don't show up in their directory.suitux commentedon Oct 23, 2026
Hi!
Thanks, that narrows it down a lot. "All Folders" queries every song, while the folder view filters by the exact stored folder path — so the path Tagr saved while scanning doesn't match the
/musicit's asking for when you click the folder. Something's off in how that path got stored.Could you check:
/musicand look at the file path shown in the detail panel on the right. What does it say exactly?select folder_path, count(*) from songs group by folder_path limit 20;MUSIC_FOLDERSvalue (quotes, slashes, everything) and the fullpodman run/ compose command, including the volume mounts.musicfolder, the URL of the request in DevTools → Network that starts with/api/songs/and its response body.If the stored path turns out to be anything other than
/music(a symlink target, a relative path, a double slash…), that's the bug and I can reproduce it from there.Hellraiser28 commentedon Oct 23, 2026
@suitux I could reproduce it with v1.15.0 (the code is the same on
main), and the stored path is fine. It's the routing.With
MUSIC_FOLDERS=/music,/audiobooksboth root folders have a single path segment. The folder view requests/api/songs/music, and Next.js sends a single segment to/api/songs/[id]rather than the catch-all/api/songs/[[...path]]. That route answers400 Invalid song ID, so the list stays empty and shows? files. "All Folders" works because it requests/api/songswithout a segment, and deeper folders likeAlbums/…work because they have more than one. A subfolder named like a song sub-route, e.g./music/audio, fails the same way.@offensivedev you can confirm it in the browser while logged in:
http://<your-tagr>/api/songs/musicreturns{"success":false,"error":"Invalid song ID"}.I've opened a PR with a fix, it's linked above. Until it's released, this works with v1.15.0 (tested): drop
MUSIC_FOLDERSand mount both folders under/music, then run a full scan.The 16 "Failed to read metadata" errors are a separate thing: Tagr couldn't parse those files at all. If you can share one of them, or the output of
metaflac --listorffprobefor it, that would help to find out why.offensivedev commentedon Oct 23, 2026
Yes, I do see /music in the path
@Hellraiser28 I can confirm that
http://<your-tagr>/api/songs/musicreturns{"success":false,"error":"Invalid song ID"}for me as well.Hellraiser28 commentedon Oct 23, 2026
Thanks for confirming! That matches my reproduction exactly. #62 fixes it; until it's released, the workaround above (both folders mounted under /music, no MUSIC_FOLDERS) gets you going.
offensivedev commentedon Oct 23, 2026
Thank you @Hellraiser28; the workaround did the job and a full sync works now!
fix(songs): list single-segment folders such as /music (#61)
Merge pull request #62 from Hellraiser28/fix/folder-songs-61
suitux commentedon Oct 23, 2026
Merged, thank you @Hellraiser28
I'll do a release now 😄
suitux commentedon Oct 23, 2026
There you go https://github.com/suitux/Tagr/releases/tag/v1.16.1
Let me know if I can help with anything