Collection scanner inserts artists/albums with no name and no songs
Bug #603744 reported by
Steve McGrath
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| PyRock |
Triaged
|
Low
|
Steve McGrath | ||
Bug Description
The collection scanner code, when run over my collection, inserts a record into the Artists table with no name, and a similar nameless record in the Albums table. There are no songs in the songs table associate with these records.
The current workaround is to not show artists/albums with 0 songs in the Collection view, but ideally they should not be added in the first place.
Solving this is going to take some serious grinding with the debugger.
| Changed in pyrock: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in pyrock: | |
| milestone: | none → 0.1 |
| assignee: | nobody → Steve McGrath (smcgrath23) |
Revision history for this message
| Steve McGrath (smcgrath23) wrote | #1 |
| Changed in pyrock: | |
| status: | Confirmed → Triaged |
To post a comment you must log in.
On analysis, this bug pops up with a set of files that have no id3 tags whatsover. The conditional that sets artist/album to "Unknown" if tagpy returns an empty string is for some reason not taking effect. Examining the files with tagpy in a python shell shows that it is indeed returning an empty string. Weird. Probably still going to have to break out the debugger, but now I know which files out of several thousand I need to scan to re-create the problem.