SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Renaming/moving "Matched to MusicBrainz song only" titles

#1

Hi !
I’m a registred user of SonkKong and quite happy with the way it works.
I’m currently working at reorganizing my collection of mp3, having full albums sorted in a dedicated directory, and singles sorted (in a different manner) in a second dedicated directory.

So far, so good.

However, there is a lot of mp3 that are not sorted, renamed and moved due to the fact that they are “Matched to MusicBrainz song only”.

Is there any way to configure SongKong so that it takes this information for sufficient and allow the renaming of this “single” in my singles collection?

(Also, I have a quite different question but it should goes on a dedicated topic: when removing duplicate, is there a way to say “keep the file from this directory” rather than the file from “that directory”? I would like to suppress the singles that are already present in the “full album” directory)

#2

Not currently, but we do have issue logged for this https://jthink.atlassian.net/browse/SONGKONG-506

I’m afraid that particular option is not available for delete duplicates, to add it please consider that delete duplicates could be applied over many folders so how could I generalize the option ?

Under Advanced Options we can choose to delete files based on the Creation Date so maybe you can do it by having all the files in Singles having a later creation date than the files in albums folder (I think its deletes the ones with the latest date)

#3

Hi Paul,

Thank you for your swift answer.
I’ve just had a look at your JIRA ticket, open in 2014… How likely is it to see it in a close new release? :wink:

Regarding the second point, indeed, I can’t see a way to easily make it selectable (in fact, I knew that when I wrote it ? shame on me!).

So, possibly, an alternative between the “preview” mode and the automated mode would be a manual mode where, for each detected duplicate files, the list of files will appear on a window where the user select which file(s) must be kept and which file(s) must be deleted/moved.
This window should show enough elements (name, size, date, tags, acousticId…) and possibly a button for playing the files, so that the user selects them with full knowledge.

Finally, I would appreciate a way to remove duplicate when AcousticID differ, but not the main tags (at least Artist / Title / remix? ? or this list could be an option as well). Probably the selection should be manual here as well. What do you think?

#4

[quote=jeromeip]Hi Paul,

Thank you for your swift answer.
I’ve just had a look at your JIRA ticket, open in 2014… How likely is it to see it in a close new release? :wink:
[/quote]
I am keen to fix this issue as a few customers have now requested it recently so it will be done soon, but I’m working on Jaikoz and other things at the moment so it will probably be a few months. 9BTW you can already do this in Jaikoz)

Regarding the second point, indeed, I can’t see a way to easily make it selectable (in fact, I knew that when I wrote it ? shame on me!).

That is quite a major change, introducing a whole new level to the GUI system, and also it demands alot of the user, with SongKong the aim is to let the customer set rules and then SongKong can apply them consistently. (BTW the approach of seeing duplicates and then chooisng which one to delete is possible in Jaikoz). So expanding on my Creation Date idea if I also added Modified Date then you could use another tool to easily update the modified date of a set of files and then SongKong wil use this to decide on what files to delete.

[quote=jeromeip]
Finally, I would appreciate a way to remove duplicate when AcousticID differ, but not the main tags (at least Artist / Title / remix? ? or this list could be an option as well). Probably the selection should be manual here as well. What do you think? [/quote]
That option is already available, take a look at the list of different ways you can define what consitutes a duplicate. There are options that just go on metadata and ignore acoustids entirely, and options that are based on musicbrainz ids rather than acoustids.

#5

Hi Paul,

Thanks for these answer. I will have a deeper look on this option for duplicate.

Considering Jaikoz, as it is a “brother” software of SongKong, have you considered a “bundle” offer for the customers who have already buy one of the two? :roll:

#6

Its on my todo list, but if you subscribe to the mailing list we sometimes offer discounts

#7

I will spend some time discovering Jaikoz because the ?delete duplicate? can definitely not be done on “tag” only by SongKong.

E.g. I found 3 files for “Paint it black” by “The Rolling Stones”.

Suprisingly, they are all different. (Well, different acoustic ID, so that is not so surprising!)

One is the classical tune I’m used to hear. OK.
One is a live recording by the Stones. OK but the only difference I saw in tags is the name of the album (no “remix” tag that could indicate “live”).
One is … a cover! But track “Artist” is still tagged “The Rolling Stones”.

So, my conclusion is that the central databases are not fully reliable and my ears are definitely needed!

#8

Well yes simple metadata tags are not as reliable as Acoustids or MusicBrainzIds thats why we don’t recommend them but that is what you asked for. It may be that only some of those songs have actually been matched by SongKong hence accounting for the wrong artist tag in one of them.

But you should try matching on Musicbrainz Ids, this allows versions of the same song but with slightly different audio encodings to be treated as a match.

But for the most accurate results you might want to listen and select yourself, and this can be done with Jaikoz.

#9

[quote=paultaylor]
But you should try matching on Musicbrainz Ids, this allows versions of the same song but with slightly different audio encodings to be treated as a match.[/quote]

I did that with quite good results :slight_smile:

[quote=paultaylor]
But for the most accurate results you might want to listen and select yourself, and this can be done with Jaikoz.[/quote]
Will try. Now waiting for my license… :wink:

Another thing: when activating the forum interface in French, many buttons miss, therefore it’s barely usable…

#10

Oh I dint even know you could use the forum in another language !

#11

I think what is just missing is translated image buttons.
(Quick and dirty fix: copy EN images to FR directory)
(Very Quick and not that dirty fix: disable other languages!)

By the way, the FR translation of SongKong is awful and frequently confusing. Therefore I switched back to English to avoid mismanipulation of the software.
I would be glad to help here (even if I’m not sure to get time for that). Could you share with me the EN and FR resource files?

#12

I did pay for professional translation so I am a bit surprised but thank you for your offer of help, I already have some instructions on how you can modify it.

http://www.jthink.net/jaikozforum/posts/list/7280.page
http://www.jthink.net/jaikozforum/posts/list/7280.page

and if you would like to sen me the changes so I can incorporate them into the main product.

#13

Sorry to hear that you paid for this patchy translation (probably partially made automatically with Google Translate or kind of).

After installing Languish, picking up one sample:

EN: Acoustic fingerprints are essential for accurate song matching, only disable this option in special cases such as if you only want parse amginfo.xml and do not intend to do MusicBrainz or Discogs matching.

FR: empreinte acoustique sont essentiels pour exacts chanson correspondant, seulement d�sactiver cette option dans des cas particuliers tels que si vous voulez seulement analyser amginfo.xml et n’a pas l’intention de le faire MusicBrainz ou Discogs correspondant. :hunf:

Google Translate: empreintes digitales acoustiques sont essentiels pour pr�cises chanson correspondante, seulement d�sactiver cette option dans des cas particuliers tels que si vous voulez seulement analyser amginfo.xml et ne pas l’intention de le faire MusicBrainz ou Discogs correspondant. :hunf:

Real French (one possible suggestion): Les empreintes acoustiques sont indispensables pour une identification pr�cise des morceaux. Ne d�sactiver cette option que dans des cas particuliers (si, par exemple, vous voulez uniquement analyser amginfo.xml sans rechercher de correspondance sur MusicBrainz ou Discogs).

However, some translation are clearly human-made.
E.g. Cat No / N� de cat. : this is perfectly accurate.

#14

Ah, this is my fault as its not practical to go back to professional for every single modification so some are done myself with the help of Google, but most are not

#15

I progress slowly but surely :wink:
At one time, I will need to discuss with you about the context of some wordings in order to propose an accurate translation. I will let you know!