MB release blacklist

I’m tagging my extensive J.S. Bach collection and frequently beets pulls in a huge Complete Bach Release

I have standalone recordings that were aggregated into this release but I do not have the whole box. This release gets eventually eliminated, but it does take time.

What I’m looking for is a blacklist to ensure that beets does not consider this release, an opposite of --search-id. Does such a flag exists ? Or is there perhaps a trick that will accomplish the same ?

As an alternative, what would be the best spot to hard code exception in the source code ? I can manage basic python.

I don’t think we currently have such a thing. I think the place to “filter out” matches, if you want to get your hands dirty, would be the beets.autotag.hooks module, which is where data sources are all aggregated—so it might be possible to hack in a check for a given ID.

1 Like

Thanks, will try and report back.