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

secondary album type overrides primary #3663

Closed
minusf opened this issue Jul 9, 2020 · 1 comment
Closed

secondary album type overrides primary #3663

minusf opened this issue Jul 9, 2020 · 1 comment

Comments

@minusf
Copy link

minusf commented Jul 9, 2020

It seems that the secondary album type overrides the primary:

primary MB release type: album
secondary MB release type(s): soundtrack

I have a custom path for soundtracks and this particular release ends up in soundtracks.

Wouldn't it make more sense if preferring the secondary type must be explicitly encouraged using preferred under match:, or something similar?

Setup

  • OS: macos
  • Python version: 3.7.8
  • beets version: 1.4.9
  • Turning off plugins made problem go away (yes/no): no

My configuration (output of beet config) is:

directory: /sonoteque

format_item: $artist - $album - $title - $length - $track
format_album: $albumartist - $album - $year

paths:
    default: '%lower{$albumartist/$original_year-$album/$track-$title}'
    genre:anime: '%lower{ost-anime/$album-$original_year/$track-$title}'
    genre:game: '%lower{ost-game/$album-$original_year/$track-$title}'
    genre:classic: '%lower{$composer/$album-$original_year/$track-$title}'
    albumtype:soundtrack: '%lower{ost/$album-$original_year/$track-$title}'
    comp: '%lower{various/$album-$original_year/$track-$title}'

match:
    preferred:
        media: [CD, Digital Media|File]
        original_year: yes
    ignored_media: [Data CD, DVD, DVD-Video]

import:
    from_scratch: yes
    move: yes
@sampsyo
Copy link
Member

sampsyo commented Jul 9, 2020

Hi! We don't currently use the primary and secondary album types. You might want to take a look at #2294 and #2200 for the backstory on why these log messages appear, but #2200 is the place to discuss how we might actually use this data.

@sampsyo sampsyo closed this as completed Jul 9, 2020
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

2 participants