You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Discogs' "index tracks" are parsed into one single track on MB
But the most common case of index tracks (Classical music) actually should result in each subtrack having an individual track on MB
For instance if Discogs lists:
Index Track Title Of Composition
Part 1
Part 2
Part 3
This should become in MB
Index Track Title of Composition: Part 1
Index Track Title of Composition: Part 2
Index Track Title of Composition: Part 3
While it currently is translated into:
Index Track Title of Composition: Part 1 / Part 2 / Part 3
It's not 100% consistent, as sometimes, the current approach would be correct, but this is far less common.
I think it's worth considering changing this.
Or, as far as it would be possible, provide an option for parse Discogs data both ways?
Or ideally... try to auto detect when what is appropriate by looking at the track positions.
On Discogs:
1.1
1.2
1.3
or
1a
1b
1c
(Or similarly with A1.1 A1.2..., A1a, A1b, ...)
=> This would mean it should become one track on MB
But
1.
2.
3.
=> Should become 3 tracks in MB.
This is actually regardless of the use of an index track or not.
The text was updated successfully, but these errors were encountered:
DoktorSultan
changed the title
Bad handling of index tracks on importing
Discogs importer: Bad handling of index tracks on importing
Feb 2, 2025
Currently, Discogs' "index tracks" are parsed into one single track on MB
But the most common case of index tracks (Classical music) actually should result in each subtrack having an individual track on MB
For instance if Discogs lists:
Index Track Title Of Composition
This should become in MB
While it currently is translated into:
It's not 100% consistent, as sometimes, the current approach would be correct, but this is far less common.
I think it's worth considering changing this.
Or, as far as it would be possible, provide an option for parse Discogs data both ways?
Or ideally... try to auto detect when what is appropriate by looking at the track positions.
On Discogs:
1.1
1.2
1.3
or
1a
1b
1c
(Or similarly with A1.1 A1.2..., A1a, A1b, ...)
=> This would mean it should become one track on MB
But
1.
2.
3.
=> Should become 3 tracks in MB.
This is actually regardless of the use of an index track or not.
The text was updated successfully, but these errors were encountered: