I’m having dificulties processing my files with jaikoz and songkong.
My current workflow: First process all releases through Jaikoz, to make sure all releases are matched correctly and save all releases in a single folder per release, then run them through sonkong, to make sure all releases are complete and the files aren’t corrupt.
The problem is songkong won’t match those releases eventhough all metadata should be correct. Even discocs id’s are present in the tag.
Jaikoz processed files not being matched by Songkong
Please send me your SongKong support files
Done
I havent tracked down the issue but looks like a bug with Discogs processing.
Can you just one folder (e.g /media/Multimedia/Muziek/0_unprocessed/0_SK_unmatched/[ZOOCD-03] Clockwork [Digital Media]) and enable MusicBrainz search and see if that fixes it. (Not in order to match to MusicBrainz but will affect route taken to Discogs)
Okay, thanks for bringing this to my attention, there seem to be two issues.
-
If you have an existing MusicBrainzIds then SongKong will not try to rematch it will just update the metadata for the associated release. However it doesn’t do this for Discogs matches, if a song has no MusicBrainz Ids but does have Discogs Release Url it is just ignored. If you have Songkong configured to search for Discogs releases but not Discogs it wil try and match the tracks to a Disocgs release but it wont just update form the existing release.
-
Although the releases are in the Albunack db and visible to SongKong the Discogs search doesn’t seem to be matching when it should, not clear if it is even running for some folders.
MusicBrainz is very much the primary database for SongKong so that is where the development is focussed but I try and address these Discogs deficiencies for the immediate release.
Issue 1 is fixed in SongKong 5.4, so now SongKong should just update Disocgs release for songs that already have a Discogs releaseUrl even if it was added by another tool such as Jaikoz.
Issue 2 was resolved in SongKong 5.9