SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Matched releases being moved to unmatched folder

Hi-

I have two discs that come up as matched to a MusicBrainz release. but which on file rename are being moved to the unmatched folder. Don’t know what’s going on…

Thank you!

You can see they both match (green)
Screenshot 2025-03-29 at 10.21.08 AM

But, when I run rename files, they go to the unmatched directory… have only run on preview right now.

Support files uploaded!

Thanks
John

Bit of an obscure one this, but the problem is the songs do not have a Mb Track Id, to be considered matched to a MusicBrainz release SongKong expects the files to have a Mb Release Id and a MB Track Id

image

Are these albums that were already matched by MusicBrainz Picard or some other tool?

Actually, although it would not usually happen in practise I think the inconsistency between Report Filters and Move Folder is confusing and a minor bug, so I have raised issue to modify Move Folder so that is does not require MB Track Id only MB Release Id

1 Like

Ah, so I figured out how to force it. I thought that if I just went through Match To Album, and then hit save, it would get that it should save an album if it hadn’t. But it doesn;t. I need to force it to save. Which I manage to do by replacing the artwork - though I know I can go to a different tab and hit “force save”. Somehow I feel like it ought to save when I hit “Save”! But it works, and those are now release matched too.

Not quite sure what you mean, but the metadata should be fixed so that Mb Track id not missing.

What I’m saying is that it won’t save automatically if I just match to the correct music brains release and then click save. I have to force it to save somehow. Otherwise the music brains release is not updated. I’m not sure why it’s just one of those strange characteristics where the software is not doing exactly what I intuitively think it would based on the interface.

Maybe because nothing has actually changed, if no fields have changed then it wil not save, perhaps another support file will make it clearer.

Is there any way to strip all the match metadata and force it to start again? I guess I could use metagrater and use it to pull all the fields that start MB or Discogs? Or is that not a great idea…?

Sounds like a bad idea, what issue would you be trying to solve there.

Ii is usually best to try and solve one issue at a time, so I’m trying to work out this Save issue for that please need the following information.

  • Clarification on what tool you used previously to match some of these albums to MusicBrainz
  • Support files showing the force save (when you send suppoort files for each task it shows upoto the last 5 reports only)