#beets

jrobeson: Indeed. I'm not sure which way is best, but decoding to Unicode only on Windows might be expedient…

Perhaps inside our `command_output` utility function that most of the code uses for command invocations?

i did find some places that don't use it!

like some places still use check_output, and some places even use list2cmdline directly!

migrating to python3 by default will fix some of this.. nicer utilities there.

Maybe we should start by centralizing those other subprocess calls

(fortunately, it looks like that `list2cmdline` invocation is just used for logging!)

weird, i actually do the same

i just thought if i can't listen them according to their location then i would at least create a playlist

or better use id3 tags yeah :D

do you use beets every day?

I play music from it every day, certainly—but I don't manage metadata with it daily. Maybe weekly.

sampsyo, so what exactly do you want to do next?

You mean about subprocesses and Python 3?

anything beets related

it would be nice to set some targets for the release after this one

maybe we can come to some agreement

Sure, that's a good idea. Maybe it would be worthwhile to brainstorm a list of everything we might want to do, and then pick targets from that list?

sounds like a wikipage

we have a refactoring page, but this isn't about that

although items from refactoring could be placed on the list

i'm going to propose a controversial change... one implemented by travis already actually. whitelist to safelist, and blacklist to blocklist.

how about this? https://github.com/beetbox/beets/wiki/Roadmap

BC of course..

Sounds good. That's just in `lastgenre`, right?

i was thinking that the actual roadmap would be tracked by github milestones, so i'm not sure about the naming

so this is more about picking what goes on the roadmap

that is, i think brainstorming was a more correct thing, with a loose priority ordering

Good call: https://github.com/beetbox/beets/wiki/ReleasePl...

I'll start by dumping in a few ideas…

so how can we prove beta quality?

I don't have a rigorous definition of that—just the point where we're confident asking people to try it out

obviously "works on my machine" isn't a good indicator

i want you to try it! (with a backup though) :)

Oh yeah! I definitely will—I mean everyday users who are OK with some risk

freso is trying it soon i think

will be good to get som test coverage

for py3 issues i mean

yeah, want to add a bullet about that? (I'll stop changing things)

nah, that wasn't for the list, that'sj ust part of making it official

ah, cool

that is, it comes with the territory

find bugs, write tests

OK, any other ideas?

(thinking more about safe/block: I think I like "blocklist", but maybe "genre list" would be clearer for the other one?)

oh! unless you're editing now, I thought of one other major pending feature

what if i just delete a file by hand in my music library folder? will beets remove it from lib also or do i have to do some extra step?

jonasquinn: The `update` command detects that and removes database entries. (It also detects metadata updates you make with other tools.)

sampsyo: does it also detect a new location within my library and set the artist/album/ ?

No, it won't pick up moved files -- it will just think the file was removed.

damn, i need to write a plugin for :D

Yeah, that would be nifty. :) In the mean time, you can try using `modify` to make your changes instead of your file manager.

sampsyo: i tried but some still dont work :/

i do something wrong haha

You might need to add -a for album-level fields?

i did

i got used to beet edit plugin

Ah, did that work better?

no :"(

Weird. If something seems wrong, please do file a bug with full instructions.

sampsyo: i dont know, some maintainers on github said it is wrong to do so

like those issues are not for support but bugs only :D

Well, I disagree. :) If you can rigorously describe the problem, expected results, and actual results, that belongs on the bug tracker.

It might not turn out to be a bug, but it will help pinpoint what's wrong.

And it might be a bug! Who knows?

(I would agree that questions like "does beets support X?" are probably not issue-worthy.)

i ll try after i sleep at least 5 hours :)

Sounds great.

jonasquinn, the way issues like that are definitely project dependent, so it's best to check the existing issues to see what seems acceptable to ask

jrobeson: thanks for the tip with quodlibet, i didnt know about. really nice player. i already used ex falso