Hi Paul,
I’ve got several folders with – I assume – full album tracks, yet not recognize as a release.
Where should I look to understand why it’s not matching?
E.g.
https://musicbrainz.org/release/ead2d201-4fcd-4918-8254-394ccc614383
NB : I found a previous message from me where I didn’t respond in time! Sorry!
I’ll do better this time!
So when we try and find a match for a set of files we try various different methods. At at the end of the day it may not find a match for a number of reasons. It may be because the grouping of files doesnt actually represent a album, it maybe that the album (or this version of album) is not in MusicBrainz or Disocgs, it maybe there is some issue with your track lengths or existing metadata that is preventing a match. So is not until we have exhausted all possiblilities that we know we could not find as match, but at this point we dont have a record of all the different attempts we tried and we cannot report the reason for no match, however maybe could improve this.
But for now, the best thing to do would run Match to One Album against the album and see what potential matches come back if the one you want is returned select it and hopefully that will then work
If SongKong does not return the required match or after accepting the match doesn’t allow it you could could go to Preferences:Support:songkong_debug0-0.log and select View Details. Go to the end of the output and then back a bit and you might be able to read the log and see what the issue was.
Then to hopefully force a match regardless:
Now I see for the example, you gave you have added the release to MusicBrainz, note newly added releases will not generally be found by Fix Songs because not yet in Albunack (although maybe found via acoustid match) but they can be found by Match To One Album
But also have you just added a duplicate to MusicBrainz because it has same barcode as a release already added ?
Note Add to MusicBrainz decides if we add a MusicBrainz tab based on two things:
But it doesnt check on MusicBrainz to see if release already exists because that would mean essentially running Fix Songs as part of Add To MusicBrainz making it much slower and it would mean that if SongKong incorrectly thought release was already on MusicBrainz it would prevent adding of release to MusicBrainz. But of course if a tab is added then within MusicBrainz there is a Release Duplicates tab that should show potential duplicates that need to be checked.
Hi Paul,
Thanks for your previous reply. I will try and let you know because I have several samples of [a] albums not recognized or [b] albums split as different releases (e.g. some tracks go to album 1, other to album 2… when coming from one single album).
Regarding discogs: it was my very first submission to discogs made from SongKong. I tried it because I saw that my album was not recognized, and since it was recent, I thought it may be missing.
I felt clumsy facing questions from Discogs during my submission, and I may have made some mistakes…
What should be the right routine with SongKong before attempting to submit to Discogs?
Unless you have disabled Fix Songs:Basic:Only allow match if all songs in grouping match to one album that should only happen if said album is a boxset, in which case it is possible for indiivdual discs to be matched to different albums but not just tracks within a disc. Perhaps you can run a Status Report and then Create Support Files
Okay, its MusicBrainz rather than Discogs
After having a failed match it is fine to run the Add to MusicBrainz task and assume at that point the album is missing. However when you go through the Add New Release it should list any release groups with similar names
and there should be a Release Duplicates tab that indicates possible duplicates and these should be checked before deciding to submit as a new release.
Hi Paul,
Just for letting you know that I’m currently working on my library.
When I’ll detect a curious behavior, I’ll create the support files for your expertise.
Thx.
