-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
[Feature] Distinguish albums by some other tags (e.g. releasetype) for same mb release id #465
Comments
Hello! Maybe this can help you: Line 103 in a7f4672
Only the first encountered track MBID is saved in the database. Otherwise, we could simply try to not merge them, since I guess there are in different folders? |
hello, that settings is already false in my lms.conf... infact the tracks are not hidden, but they are merged in the same album. So I have track 1 two times, track 2 two times, etc... This instead
looks more desirable :-) |
Yes, I meant to set it to true to hide your duplicate files, but you won't control which files are "selected". |
Thank you... let me know if you need some testing! |
Hello, I am encountering this situation: I might have two "version" of the same album, with the same musicbrainz release id, just because one is the result of a format conversion. This tends to happen for me with dsd files. which are not natively playable on every dac I own. So for convenience I tend to store a pcm version of the same album.
I am currently getting away by selecting, when possible, different MB releases, but this might be wrong especially when there is only one release for that album, or only one that relates to that SACD release.
One solution might be to add the release type as a criteria for distinguishing an album from one of it converted forms.
Does this sound possible?
I have explored the option of changing the album title somehow, but this did not work: once there is a mb release id in the tags, those files would be mixed in the same album anyway.
Thank you
The text was updated successfully, but these errors were encountered: