#beets

i haven't got any farther because i've been hung up on phrases in the docs like,"option (b) makes sure all your songs’ tags are exactly right from the get-go" ... "So instead of a chore, try thinking of correcting tags as quality time with your music collection"

i think i should import -qlW everything and play with beets a bit, then import the rest after i get a handle on it

i have some ideas for automating the import process for my garbage library so maybe i'll fork beets and play around with that

maybe something like specifying some filters like "if condition then action" so you can do more automatically/in quiet mode

the interface is also a little chaotic for me. when it's asking for input i have to scan quite a while just to see where i'm supopsed to start reading to figure out what beets is showing me

hi

I have no idea what your meta commentary means

about hung up on phrases

in general the process one should use while using beets for the first time

1) make a copy of a small but representative subset of your music collection

2) point beets at it in quiet mode

3) see if results are acceptable

4) if so, point it at whole music collection

5) manually tag things that aren't tagged in quiet mode

sampsyo: oh, i had not seen it, it's excatly what i was looking for :) thx !

:)

ses1984: sounds like you have interesting ideas. If you have specific suggestions about the UI or automation, we'd be glad to hear them

over this thanksgiving weekend i will try to play around with some stuff on my own

the main enhancement i would like to add is that when using the autotagger, it would be easier for me to see what i'm looking at if the screen was cleared between requests for input

so that you only see what's relevant to the current question and nothing more

what do i have to do if a plugin needs another python modul that is not in the official dependencies? i write a plugin that updates a plex server on database changes

derwin: you're suggestion for how the process works in general is very clear and it would be nice to see something like that in the getting started guide

or maybe i just should see if i can solve it with urllib

oh i see

there is something in the setup.py

i think i might have run into a bug. twice i have tried to import a section of my collection and it seems to reach a point where it stops working and just hangs there. i tried to interrupt with ^c and it hung for an hour before i terminated the process. i've skimmed issues in github searching for import and did not see anything like what i just experienced

also, i was wondering, when resuming a previously interrupted import, it seems like it re-attempts to scan/tag things that were previously skipped, is that normal?

regarding my other ideas, like filtering import questions so that more things can be imported in quiet mode, it looks like there already has been some small discussion on the topic, issue 758 and 1077 for example

i will have some spare time over this holiday weekend so i'll see what i can hack up

xsteadfastx: Yeah, the solution for that kind of thing is just to put it in the docs. ("Remember to `pip install ...`)

i think it happened again...i'm importing a section of my library and i have got no output from the import process in over an hour, i'm sending logging to a file that also has not been written to in over and hour,

and python has been stuck at ~125% CPU usage for that time

ses1984: Can you narrow it down to a specific album/song?

Or, failing that, to a particular plugin?

Or get the surrounding verbose output for one of these hangs?

More detail could help us repro.

sampsyo: others and me probably are going to tell this often many times after this, but I really like your approach. Hang on to that as long as you can, it's a really healthy approach.

(I know, I've said similar things in the past)