Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LastGenre plugin not respecting "noautotag" flag on "beet import" #5598

Open
dewey opened this issue Jan 15, 2025 · 0 comments
Open

LastGenre plugin not respecting "noautotag" flag on "beet import" #5598

dewey opened this issue Jan 15, 2025 · 0 comments

Comments

@dewey
Copy link

dewey commented Jan 15, 2025

Hey—

I've asked this question on IRC and since found the reason, which I believe is a bug or at least unexpected behaviour: I've imported my old library as-is with "--noautotag".

Today I ran "beet update" on my library and I saw that it rewrites some genres based on the tags in the files (Which is expected). What's unexpected is that it updates them from a genre to the one in the file itself. I was not sure where this existing genre came from if "noautotag" was enabled.

Screenshot 2025-01-15 at 12 39 47 png@2x

Today I realized that this is happening because of the LastGenre plugin which has this enabled as a default option. The genres match the first result on Last.fm (Including the typical Last.fm inaccuracies "hip-hop" and "hip hop" etc.), so it's definitely coming from this plugin.

auto: Fetch genres automatically during import. Default: yes.

I feel like the LastGenre plugin should respect the noautotag flag based on the documentation of the "noautotag" flag.

Setup

beets version 2.2.0
Python version 3.8.15
plugins: bandcamp, discogs, edit, fetchart, fromfilename, lastgenre, lastimport, plexupdate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant