#beets

Just started using beets; possibly stupid question:

what if I want to query on a single word?

i.e. beet ls boo

will return stuff that has both "boo boo boo" and "boopity boopity" in it

what if I just want the former?

(I suppose I could do beet ls ' boo '; but meh.)

JayPee: "boo boo" works too

but there isn't a easy way to query for a single word, unless you use regex's

JayPee: A regex that matches only the full field would look something like ^this$

hello

sampsyo: irc is simpler to debug problems than twitter :)

so i got an album with artist as ARTIST

i have done 'beet modify artist:ARTIST artist=ARTIST'

and the same with albumartist=

now i want files to move from the directory ARTIST/album to artist/album

but i don't understand how to do it

daks: hey there

indeed, twitter is a poor IRC :)

for sure :)

since albumartist is an album-level field, use:

beet modify -a albumartist=foo

oh

i don't understand why but i'll try

it's a bit confusing; it would be great to find a way not to expose that distinction to users

sampsyo: what do you think about checking if an album's items all contain the same field and then add that property to the album too?

yes, that might be a good idea

we do a similar thing for the `update` command

oh ok it's because the db has information about tracks AND album?

yes

which has no sense for files

BrainDamage suggestion seems good

BrainDamage: it would be great if we could move that logic (propagating item-level field changes to albums) into a function and use it in both `update` and `modify` (and the `mbsync` plugin, which also does the same thing)

with -a beet move does the job, thanks

adding this to my beets-cookbook document

it's a great software but sometimes user interaction is hard

when using beet modify

is beet write necesary after?

depends on your configuration (if you have import.write set, then modify does it automatically)

i didn't change this config, is it the default one?

yes

default queries are case insensitive it seems?

yes they are, but regex aren't (but much much slower)

thanks for your help, going back to library organization

:)

sampsyo: would you have an idea why importing a cd with about 30 tracks would take one hour?

Nope. Do you have echonest enabled?

I have no system or network load, I'm really stumped by this :(

I do have echonest enabled

Uploading to them takes literally forever

yeah, but it hasn't started uploading yet

(And waiting for the analysis results to come back)

Oh?

Any clues in the verbose log?

I'd have to rerun it for that, right?

is running import with -v enough or should I add something else?

hmm, getting connection timeouts from the lyrics plugin. That could be it

Hey all, I've sorted all my music using beets but accidentally reversed two tags (I put $artist - $track when I meant the other way around) - The FAQ and help command says that I should be able to fix this easily by running a beet move $/Music (my destination folder), but I fixed it in the config, did that, and it just chugs for a minute or two, exits out, and doesn't rename anything

Is there something I need to add to it to tell it to process already imported media or something?

stillaftermath : try with the origin folder

or no folder at all

just "beet move"

Oh, beet move might be the trick, it's reporting back that it's moving 2000-and-change items

and nope, negative.

By origin folder you mean the -d switch, as in beet move -d ~/Music?

yes

trying that now

but beet move should do the trick, I use it all the time

Aha! yeah, worked with the -d switch

One more q - The import process is very slow (pausing for seconds and sometimes minutes before returning options or deciding on the course of action) - I'm betting this is due to one or more plugins. My current line is "plugins: discogs fetchart embedart lastgenre duplicates"; any of those known right off the bat to be bad for that kind of thing?

I know musicbrainz itself can sometimes be all bitchy with request throttling and such.

I'm thinking it's discogs because it gets much worse on albums that return a ton of potential matches

I don't know, try without it and you'll see

Yeah will do, just asking in case one of them was a known problem child

Thanks for the help mate

You can try on the same album by reimporting it to see if there is a big difference. Just change the path to the one that is already in your library

Beets won't really reimport it but will update it intead.

instead

you can also set up the musicbrainz vm

and unthrottle your requests, heh