corrupt beets db: empy albums #5525
odoublewen
started this conversation in
General
Replies: 2 comments 2 replies
-
Apparently, this situation is the result of me using |
Beta Was this translation helpful? Give feedback.
0 replies
-
Can you try using beet update to update the db? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Somehow, I've managed to create two "empty" albums in my beets db. Note that these are self-produced and self-tagged mp3 files. I may have tagged, and retagged, and imported them a couple times before I got everything right. Somehow, in the process of doing that, I've created two "empty" album IDs. In other words, I think the beets database is corrupt.
Here, I have two actual mp3 tracks associated with an album "Vernal Pools".
If I do a
ls -a
I see this:The problem is that album IDs 4672 and 4679 actually don't exist. For example, if I add
$path
to the output format, I get this:I look at line 1409 in the library module and I scratch my head, wondering, is this exception caught somewhere else, or is it simply there to provide a more descriptive error message?
What can I do to fix this? From what I can tell from reading the docs and looking at the CLI, it doesn't seem that this is a common thing. Note that I cannot use the
rm
subcommand to remove the album:It seems like I will need to get into the sqlite database and manually fix it by deleting these two album rows. Can anyone provide any tips?
Beta Was this translation helpful? Give feedback.
All reactions