Closed mastermindg closed 7 years ago
Currently, album IDs are not determined by album title alone, but by all album-related tags. See #46 for known issues with this. Best results are usually achieved by using a tagger that assigns MusicBrainz IDs.
Yeah, This issue is a bummer for me too, which I'm trying to fix. Which are the album related tags? Once I know them, I can better fix them. Also does calling mopidyctl local scan
reimport data even if only the id3 has changed?
@paulhayes: AFAICR local scan
checks the file's modification date, so updating tags should be sufficient. Album related tags include album name, album artist, track count and volume/disc count.
Especially the last two seem to give issues with multi-disc albums, especially if track count varies by disc (#46).
Is there any way to stop is using volume/disc count in the generation of the md5?
On Mon, 6 Jun 2016 at 21:07 Thomas Kemmer notifications@github.com wrote:
@paulhayes https://github.com/paulhayes: AFAICR local scan checks the file's modification date, so updating tags should be sufficient. Album related tags include album name, album artist, track count and volume/disc count. Especially the last two seem to give issues with multi-disc albums, especially if track count varies by disc (#46 https://github.com/mopidy/mopidy-local-sqlite/issues/46).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mopidy/mopidy-local-sqlite/issues/80#issuecomment-224072499, or mute the thread https://github.com/notifications/unsubscribe/AAm1T8jg8ACiATOVqlSCivSwt0h-3lMRks5qJH4VgaJpZM4IaPQU .
@paulhayes: Yes, implement #46 ;-) So unless there is any new information on this subject, e.g. issues not related to track/disc number tags, I'm going to close this as a duplicate of #46...
I'm scanning my library trying to fix gstreamer detection issues and new songs that are found are placed in a new Album with the same name as the original. These tracks should all be in a single album.