SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Wrong tags due to wrong acoustid

Hi,
in my collections are some mistagged songs with the following characteristics: the file has a valid musicbrainzid, discogsid and acoustid.

if i select each file by hand and update it to ONE musicbrainz album it changed to the right one. if i want to submit the new result jaikoz says that’s impossible because there is a valid album.

is there a way to fix all broken files or have i go trough the collection by hand?

thank you

When you say Submit the new result which action do you mean ?

submit the pairing musicbrainzid, acoustid to the server.
sorry for being unclear

What exactly does the error say please (word for word)

Steps to reproduce:

  1. Select mistagged file with a valid combination of musicbrainzid, discogsid and acoustid.
    the musicbrainzid points to wrong datarecord, based on the content of the file. let’s say it points to the psy-song, while the content of the file is a mozart-recording
  2. rightclick on the file and select Action->Match to release->match to one musicbrainz release
  3. analysis starts and ends with a successful match the musicbrainz database
  4. now the file is tagged in the correct way (e.g. with mozart)
  5. click on “submit musicbrainz/acoustid pair to the server”
  6. a messagebox appears “Found 1 Acoustid for AcoustId Fingerprings \n Submitted 0 new fingerprints because they are unknown or link to a differenz recording. \n Finished Submit Musicbrainz/Acoustid for 1 songs”

my central question is how can i fix all files which are mistagged in this way without doing step 1-4 by hand for each one. if i rerun the automatic detection it will tag the file wrong (because of the wrong song/acoustid mapping?)

The reason why you get this message is just because that acoustid has already been linked to that recording so there is no reason to resubmit it, you can check this using View Online:View this AcoustId at Acoustid

So I dont think there is an issue is there, or are you saying if you just match all the songs in one go they get matched again to the wrong songs. If so the best thing to do is ensure that the bad metadata is removed from the file, and also ensure you clear the MB Recoridng Id if you actually want Correct Metadata from Musicbrainz to rematch.

Also, matching has been improved in Jaikoz 5.0.0 Prerelease so I would try that.

http://www.jthink.net/jaikoz/jsp/beta/start.jsp

is there a possibility to run

  1. rightclick on the file and select Action->Match to release->match to one musicbrainz release
  2. analysis starts and ends with a successful match the musicbrainz database
    for each file automaticly?
    because if i select all files they are matched to the same album

I’m sorry I don’t understand what you are trying to do, could you please explain in more detail what the problem is and what you want to do.

to fix my collection from the “bug” described in this post, if to run steps 1-3 for each file. is there a way to automatize it?

[quote]
Steps to reproduce:

  1. Select mistagged file with a valid combination of musicbrainzid, discogsid and acoustid.
    the musicbrainzid points to wrong datarecord, based on the content of the file. let’s say it points to the psy-song, while the content of the file is a mozart-recording
  2. rightclick on the file and select Action->Match to release->match to one musicbrainz release
  3. analysis starts and ends with a successful match the musicbrainz database
  4. now the file is tagged in the correct way (e.g. with mozart)
  5. click on “submit musicbrainz/acoustid pair to the server”
  6. a messagebox appears “Found 1 Acoustid for AcoustId Fingerprings \n Submitted 0 new fingerprints because they are unknown or link to a differenz recording. \n Finished Submit Musicbrainz/Acoustid for 1 songs” [/quote]

But match to Release is for matching a group of songs to a release not a single track, you can automate the tasks you want to do in the autocorrecter but I still don;t understand what you are trying to do, and what the problem is.

Could you try explaining it again rather than just reposting an earlier post.