#beets

DjSlash: thanks! that's incredibly nice to hear

I'm happy the style has led to something we can all use

i think i can help narrow it down soon. i will try to parse the log file and move everything that was skipped so when i try to re-import it won't re-attempt to import those and hopefully hit the problem area sooner

i guess that will only work if the problem is a certain album or track

is it normal that when resuming an import it tries to import previously skipped tracks/albums?

ses1984: no. but I suspect you're seeing the last few albums, which hadn't finished the import pipeline when the process stopped

hi, i imported some albums and i am using tomahawk as a player but some of then dont have Year

when i search beet ls year:2014 it lists them

any idea why this could be happening

is there some beet ls --verbose command to see all the tags?

can i also list genres in my library

sampsyo i dont think it's just the "last few albums". every time i resume the import it tries to import every single album that it skipped before. not necessarily in the same order. but thousands of them.

so now i run a little script that parses the log file and then moves albums that beets reports as skipped to a separate directory

i have not been able to zero in on a particular album that freezes the import process either. yesterday i let an apparently-frozen import wait for several hours before terminating, then when i tried to re-import it seemed to freeze at the same place but then proceeded after about 20 minutes

nickn: check out the --format flag on the list command

sampsyo: hi, yeah i just did

seems fine

i suppose Tomahawk is being weird