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

Different releases incorrectly considered duplicate #5250

Open
raimundomartins opened this issue May 20, 2024 · 3 comments
Open

Different releases incorrectly considered duplicate #5250

raimundomartins opened this issue May 20, 2024 · 3 comments

Comments

@raimundomartins
Copy link

Problem

I'm trying to import both https://musicbrainz.org/release/3e475b92-6217-43cf-8557-e0c11bc96091 and https://musicbrainz.org/release/0701e066-6823-4987-946e-ad04a972bb0c but when I try to import the second one it is considered duplicate. Catalog number is different and they have different tracks, but I'm not allowed to have both albums in my library.

Setup

  • OS: void-linux
  • Python version: 3.12.3
  • beets version: 1.6.0
  • Turning off plugins made problem go away (yes/no): no (even worse, now autotagger can't even match the release!)

My configuration (output of beet config) is:

lyrics:
    bing_lang_from: []
    auto: yes
    bing_client_secret: REDACTED
    bing_lang_to:
    google_API_key: REDACTED
    google_engine_ID: REDACTED
    genius_api_key: REDACTED
    fallback:
    force: no
    local: no
    sources:
    - google
    - musixmatch
    - genius
    - tekstowo
directory: /srv/music

import:
    from_scratch: yes
    write: yes
    copy: yes
    move: yes
    detail: yes

aunique:
    keys: year albumartist album
    disambiguators: albumtype label catalognum albumdisambig releasegroupdisambig
    bracket: '[]'
per_disc_numbering: yes

paths:
    default: '%lower{$albumartist}/$year %lower{$album}%aunique{}/$disc_and_track %lower{$title}'
    singleton: '%lower{$artist}/%lower{$title}'
    comp: VA/$year %lower{$album}%aunique{}/$disc_and_track %lower{$title}

musicbrainz:
    extra_tags: [year, label, catalognum]
    genres: no
    searchlimit: 5
max_rec:
    missing_tracks: strong

match:
    ignored: missing_tracks
    preferred:
        media: [CD, Digital Media|File]
        original_year: yes
    ignored_media:
    - Data CD
    - DVD
    - DVD-Video
    - Blu-ray
    - HD-DVD
    - VCD
    - SVCD
    - UMD
    - VHS
pluginpath: [~/beet-plugins]

plugins: inline discogs chroma fetchart lyrics acousticbrainz web frompathname
item_fields:
    disc_and_track: u'%01i%02i' % (disc, track) if disctotal > 1 else u'%02i' % (track)
discogs:
    user_token: REDACTED
    index_tracks: yes
    apikey: REDACTED
    apisecret: REDACTED
    tokenfile: discogs_token.json
    source_weight: 0.5
    separator: ', '
fetchart:
    quality: 90
    auto: yes
    minwidth: 0
    maxwidth: 0
    max_filesize: 0
    enforce_ratio: no
    cautious: no
    cover_names:
    - cover
    - front
    - art
    - album
    - folder
    sources:
    - filesystem
    - coverart
    - itunes
    - amazon
    - albumart
    google_key: REDACTED
    google_engine: 001442825323518660753:hrh5ch1gjzm
    fanarttv_key: REDACTED
    lastfm_key: REDACTED
    store_source: no
    high_resolution: no
    deinterlace: no
    cover_format:
chroma:
    auto: no
acoustid:
    apikey: REDACTED
web:
    reverse_proxy: yes
    port: 8004
    host: 127.0.0.1
    cors: ''
    cors_supports_credentials: no
    include_paths: no
    readonly: yes
pathfields: {}
album_fields: {}
acousticbrainz:
    auto: yes
    force: no
    tags: []
@RollingStar
Copy link
Contributor

@raimundomartins
Copy link
Author

It doesn't make much sense to me to keep that in a separate option from aunique since the latter will never kick in without changing the former (especially because the former is not currently available in most distributions).

It worked, but I had to install the developer version, that flag isn't available in 1.6.0.
However, it did not disambiguate the path of the albums like I expected with the %aunique{}. Is my usage incorrect (I couldn't find a clear example of how to use it)?

PS: It turns out it was not disambiguating between my import and whichever one of these I have, but it now put in the same directory the ones I said in the OP, which are two singles in the same release group.

PPS: Despite the criticism this software in a life changer, thank you very much!

@RollingStar
Copy link
Contributor

My config has an example of aunique, but it's many years old. YMMV. https://gist.github.com/RollingStar/86e041338df295afbbf77a9027903068

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