search

beetbox / beets

music library manager and MusicBrainz tagger
http://beets.io/
MIT License
12.92k stars 1.82k forks source link

missing: Configuration option to exclude music #1740

Open Joshfindit opened 8 years ago

Joshfindit commented 8 years ago

There are some albums where I specifically don't keep certain tracks. Doing a search for missing tracks, these will always come up and clutter the list.

So, I propose a blacklist: If a track or album is in the blacklist, the beet missing list would simply not show them, or show a +42 tracks blacklisted indicator at the end of the list.

sampsyo commented 8 years ago

Sounds reasonable!

How about a filter configuration option, which is a positive query that music must match to be included? Then you can use the new negation operator in queries to get blacklist behavior.

Joshfindit commented 8 years ago

If I'm understanding correctly, by default it would specify tracks you definitely want to check for, and by specifying tracks with a negation operator, it would flip around and blacklist those tracks?

On Nov 27, 2015, at 7:16 PM, Adrian Sampson notifications@github.com wrote:

Sounds reasonable!

How about a filter configuration option, which is a positive query that music must match to be included? Then you can use the new negation operator in queries to get blacklist behavior.

― Reply to this email directly or view it on GitHub.

sampsyo commented 8 years ago

Yep! The idea is that you would have this configuration:

duplicates:
    filter: ^bar

And then this command:

$ beet duplicates foo

would be equivalent to using the combined query foo ^bar in the default configuration.

Joshfindit commented 8 years ago

Yeah, that makes sense and would fit the bill. Would this allow for wildcards?

On Nov 28, 2015, at 1:35 PM, Adrian Sampson notifications@github.com wrote:

Yep! The idea is that you would have this configuration:

duplicates: filter: ^bar And then this command:

$ beet duplicates foo would be equivalent to using the combined query foo ^bar in the default configuration.

― Reply to this email directly or view it on GitHub.

sampsyo commented 8 years ago

In the same way that queries can... got an example you're interested in?

Joshfindit commented 8 years ago

Re-reading, I see you're proposing adding the ability to 'add' a query to the missing plugin, which is perfect. I can't think of anything I would want to exclude that wouldn't be served by this.

As for an example of wildcards; I can't really think of one except being able to filter out missing tracks from entire artist/band members (like *Yo-Yo Ma filtering out both the artist as well as Silk Road Ensemble, Yo-Yo Ma)

sampsyo commented 8 years ago

Great! And as for blanket queries, that's (thankfully) the default if you don't use a field qualifier.