#beets

sampsyo: does beets support "A" and/or "B" for track names?

err, track numbers?

like, in the database, if not in output files?

sampsyo: did you see my question, here? https://botbot.me/freenode/beets/2016-01-03/?ms...

thanks for the merges, BTW

so, musicbrainz is pretty serious about using unicode apostrophes, em dashes and such

it's messing up my last.fm stats, and since i value correct last.fm stats over the unicode correct-ness of my library i'm looking to normalize the common occurrences to ascii

has anyone else cared about this? i see the lyrics plugin normalizes common ones to ascii when doing searches

looks like the edit plugin would let me change them semi en-mass, but i'm considering working out a plugin to do it for myself if no one else has tackled the same problem

bombtrack: "asciify" exists for path formats

I somewhat presume you can use it in tags, but I don't know

also, yet another reason last.fm is this sad graveyard of music fan enthusiasm

ha, yes. i have zero belief they will ever do anything to "merge" the dupe tracks,

darwin: i'm reading the path format docs, but sadly i don't think it works on tags

bombtrack: they formerly were going to use mbids, and etc... had a mb person on staff with that goal.. and ... it was.. deprioritized

bombtrack: I think you may be correct that a plugin is required :/

darwin: the path templates + inline plugin is basically what i would want, but for tag transforms

might turn it into a weekend project soon

darwin: No, just numbers.

bombtrack: Check out an existing ticket called "formatted modify". This would be an awesome thing.

sampsyo: Starting https://github.com/sampsyo/beets/issues/406

JesseW: I can't think of an example atm, but I have a feeling those queries have existed in the past...

opatel99: Nice!

sampsyo: Have you looked at https://waffle.io/ for the project? The repo is pretty active, and that display could really help out.

I took a look, but couldn't quite see how the workflow would work. Might be worth another try.

sampsyo: non-FieldQuery-s, you mean?

Right.

Maybe SingletonQuery used to work that way, although it doesn't now?

Can you tell me/point me towards more explanation of how construct_query_part is intended to work?

sampsyo: is that because tags only support numbers?

Right. (In at least some formats.)

JesseW: I'd love to write up a more complete explanation -- can I make a note to do that and get back to you?

sure! want me to make an issue for it, or would you rather do so?

Please go for it!

sampsyo: do any formats actually support names, I guess I'm wondering, heh

Hmm. I suppose the free-form formats like Vorbis comments might.

hrm, itunes can as well, apparently

sampsyo: How do I have beet print the metadata for one of my tracks?

The `info` plugin can do that, as can the -f option to `beet list` if you need specific fields.

sampsyo: Is it currently not possible to ^C out of beets?

mid-import

The FAQ has something on that, IIRC

found it. thanks

sampsyo: I will file an issue regarding exploration of support of alphanumeric track names

Great; thanks!

sampsyo: there's your issue. :-)

:)

I wonder if the "beets move" faq (http://beets.readthedocs.org/en/latest/faq.html...) is not clear enough about whether you can move the files first and then just run beets move and it'll be safe

beets random is painfully slow

I'm importing a large boxed set, and it's taking a *very* long time

it's just over 300 tracks

yow

is there a way to supply the musicbrainz id when initiating the import so it doesn't have to do any matching

maybe it's another case of Picard and then beet