Closed exislow closed 4 years ago
Hi! The metasync
plugin doesn't work as an importer metadata source. You explicitly invoke it by typing beet metasync
. Does that do what you expect?
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I habe configured several meta sync backend in beets. Especially I need a backend that can provide the
key
andbpm
information likebeatport
and / oraudiobrainz
. But everytime I try to import my music it seems, thatmusicbrainz
is the only backend beets considers.How can I tell beets to rely on more / other meta backends especially for
key
andbpm
information?something like this happens
Running this command in verbose (
-vv
) mode:Setup
mbsync
in config.yaml it still uses MusicBrainz as meta backend)My configuration (output of
beet config
) is: