#beets

Which plugin? That's the question sampsyo. I mean I can't figure out why... Somehow at an uncertain point it stopped before.

Well, you can try turning them all off and start from there.

Right now I am running beets through a bash script that parses every subdirectory and sends it to beets, that way my library seems to be increasing

Well, the problem is one by one, it might even take me days... Hmm, I wonder if beets have trouble reading non-english folder/files.

Nomads: Well, alas, the only way to know what's really going on is to narrow it down… otherwise, we don't really know how to start debugging. :/

Allright, after my bash script ends, I will re-run it and try disabling plugins to find out why. But currently it already added 70gb of music ever since I last wrote here.

One more question. I edited the genres file to have some of the genres, not all and cannonical is also enabled. But currently beet is adding all the genres I removed from the yaml file. Any tips on how I can fix it?

hey all. i'm working on a plugin, and I'd like it to remember the last time it was run (if ever). Is there some way for me to write "last_ran" to the database, or maybe to a file and retrieved later?

hi, can anybody tell me why beets might appear to hang during an import? i'm running the latest version installed via pip on raspbian wheezy on an rpi 2, and it's generally been working great, but after processing an unknown album of tv themes as individual tracks, it's still sitting there apparently doing something, and top shows it's using lots of CPU, but nothing is coming up from the prompt.

my library.db file shows its modification date being updated, but it doesn't seem to be getting any larger

there seem to be a lot of background tasks that don't provide status updates (or at least not prompt ones) ... fetching some metadata, fingerprinting etc.

it's probably not actually hung.

if it's been sitting there for 20-30 minutes after manually identifying about 30 tracks from this unknown album, is that more or less as expected?

cautiousgiant, I'm a new beets user as well. I'm running it on a vps in my dedicated machine and yeah, sometimes the process runs just too long. I was told maybe it's due to a plugin.

It took me ~24 hours to make beets successfully import 60gb of music. More to come... I am observing the process and it seems to wait a lot on some folders indeed.

Thanks, Nomads. I guess I will leave it running for the time being and see what happens.

Using find to see what's been touched, only the state.pickle file seems to have been touched in the last 30 minutes

And do not forget that your rpi2 may be a tad underpowered ^^

Nomads, did you quit the beets process when it seemed to hang, or just leave it running indefinitely?

Actually, on my case I spent 12 hours on waiting one process. Didn't move on. No matter how many times I ran beets, it hang at some point. But I was trying to scan a folder of 300-400gb.

So I decided it might have something to do with the amount of it. So I compiled a bash script to search for every subfolder and if there's any mp3 files in it, run beet import command and skip to next one

Ah, interesting, so you run each folder as a new import

My library is "only" 30GB

Currently, I have a total of 100Gb files recognised at my import folder, before I beet killed itself not recognizing many of what it recognized now.

cautiousgiant, I am trying a library of 500gb ^^

Maybe what I did is killing the multithread functionality, I am not sure and I sure did not want to try parallelizing the tasks. But yeah, basically. If there's an mp3 file, it is sent to beet, otherwise it's skipped.

But then again, I'm a newbie as well. My approach might not be approved here. I'ld say give your beets some time before killing the process.

But beware, I had to re-import my library a few times due to db corruption caused by killing the process