Album cover is not being added to DB when scanned by supysonic-watcher.
When I view "recently added" after an album had been added to my library via supysonic-watcher a cover are not being loaded. After I run supysonic-cli folder update MyLibrary the cover is being displayed correctly. Will test it once again and get back.
I'm aware, see #77
album art still isn't picked up by the scanner for me. (and like @sprnza, it appears after a folder update). My installation includes 9c58b69. Is there any way I could help you debug this? Thank you
It's fixed for me by the commit btw.
By folder update I suppose you mean the folder scan CLI command.
Regardless of album art, are audio files correctly picked by the watcher?
Is your album art individual files (jpgs, pngs, etc.) or embedded with audio files? In case of the former, do you first drop the cover file(s) in a new folder then the audio files or are there some audio files in the folder when you add the cover(s)?
Do you have something set for scanner_extensions under the base section of supysonic's configuration?
sorry yes, I meant the folder scan command.
Also, my music is managed by beets, and I just imported 4 albums with it. Of the 4, supysonic watcher only found art for 1 of them.
As it was importing, I was watching the filesystem. beets seems to first create a directory for the album, then slowly add the tracks one by one, then finally add a folder.jpg at the end.
But after one of these:
supysonic> Scanning 'Library': 20197 files scanned
Scanning done
Added: 0 artists, 0 albums, 0 tracks
Deleted: 0 artists, 0 albums, 0 tracks
the artwork appeared
(I use a docker version btw - but hopefully that isnt relevant)
I've run some tests but I'm unable to reproduce :( Could you perhaps provide the watcher's logs when this happens?
I found an error but it occurs when deleting files (or directory), not when adding them.
Hello. I recently found and fixed (4bee23ce23f43382ba72cbe22abc38bf06295438) an issue on the watcher about cover art. This could be the same issue you were running into. Could any of you grab the latest master and confirm if that effectively fixed the issue on you side please? Thank you.