Screenshots and sample files on the way . . . Watch for an email from etransfer.com.
SongKong ignores track number in Naim metadata?
Haven’t received anything yet.
Thanks for letting me know. The WeTransfer failed. Resent, and this time it said it was successful.
Okay thanks I understand i understand now
So for example in the meta.naim file for Up by Great Big Sea the track The Old Black Rum is the 9th track on the album but it is listed i the meta.naim file as the second file.
"tracks": [
{
"id": "MT0001843150",
"title": "Run Runaway",
"index": "1",
"artist": [
{
"id": "MN0000184208",
"name": "Great Big Sea",
"role": "primary",
"attributes": ""
},
{
"id": "MN0000184208",
"name": "Great Big Sea",
"role": "trackartist",
"attributes": ""
}
]
},
{
"id": "MT0000816359",
"title": "The Old Black Rum",
"index": "9",
"artist": [
{
"id": "MN0000184208",
"name": "Great Big Sea",
"role": "primary",
"attributes": ""
},
{
"id": "MN0000184208",
"name": "Great Big Sea",
"role": "trackartist",
"attributes": ""
}
]
},
But its index value is 9 so we can get in the right order if we use the value of index rather than the order they are listed. In the example files that I have there is no difference so I havent encountered this problem.
Okay I will endeavour to get this fixed for next release - https://jthink.atlassian.net/browse/SONGKONG-2374
Yes, that’s exactly it, Paul. Please notify me directly when the fix is available because I’m holding up my project pending your fix.
For some unknown reason, a significant percentage of my (thousands of) meta.Naim files have the track list sequence not matching the album sequential track order (Metadata lists them 1, 9, 2, 3, 5, etc - but the Index number is correct for each track). I have found this situation in every instance I’ve looked at where SongKong has mis-labeled the WAV tracks after tagging with the box ticked "For Naim WAV files read the accompanying metadata (Melco License Only). The Naim audio server (in my Naim Uniti Core, for example) handles it just fine, but this will be a massive improvement where Naim-ripped WAV libraries are used with non-Naim audio servers.
Okay this is now fixed, please let me know how you get on.
Paul,
That’s an awesomely fast turn-around on the software fix, thanks. I tested a number of un-tagged albums where I know the naim metadata had the tracks listed out of sequence, and it got them all right.
However, it appears that if an album had been previously tagged with incorrect track title metadata, it is not being replaced by the new correct track title ID tags. I tried setting For Songs Already Fully Matched “Update Metadata and FIle Name Only”. No success there. How can I get SongKong to over-write existing WAV ID tags?
In my case, because I was lucky or smart enough to make a copy of the library, I can just delete my old copy and re-do everything. But if someone has run the prior version of SongKong on their library, they will need a way to remove the old tags, or have SongKong over-write them.
Not normally an issue because Wav files are blank to start with and usually would only need to run once but tried it and hit the same problem, do you have Ignore songs previously checked that could not be matched on the Basic tab checked, if so so uncheck and try again, if not please run Create Support Files so i can see your reports and logs.
No, that “Ignore songs…” box was unchecked.
Okay I need your support files then so I can check your config.
Support files are uploading now.
For your testing, Paul, I’m sending you by WeTransfer a couple of albums where the WAVs are incorrectly tagged.
Okay the problem is first we use the meta.naim file to add the album information (e.g Album Artist, Year of Release), then we map the tracks to the right songs and add the track info (e.g TrackNo, Title, Artist). But this second part is failing because we take into account existing metadata in case user has manually entered some data to prevent incorrect mapping messing up existing data, but because the data is messed up from previous run the bad data prevents adding the right data and actually if you click on the Errors and Warnings tab of your report it shows you this.
I have figured out a workaround
You need to remove Title and Track No from the existing data to allow the track match to work, so if you start Fix Songs and add Title and Track No (and Instrument explain later on) to Delete all metadata from these fields
then this data will be removed.
This wont allow the match this time because the data is removed after the Naim match, but if you now start Fix Songs again and remove all those fields from Delete all metadata from these fields it will now work
I noticed there is a minor problem that it re-adds the data for the Instrument field so you end up with the data added twice, we can avoid that we add Instrument to the list of fields to be deleted as well.
Hi, I looked at your errors and warnings for report 7 and found a couple of errors that I have not encountered before
Could you please send me these folders:
F:\Naim Rips - Phil\MQ\Jack Nitzsche\Performance
F:\Naim Rips - Phil\MQ\Lorin Maazel\Wagner The Ring Without Words
so I can replicate and fix issue.
OK, so if I understand this correctly, the way to replace track title errors created by the previous version requires a two-pass process. In the first pass, I set “Delete all metadata from these fields” to “Instrument, Title, Track No”. On the second pass I remove all the fields from the “Delete all metadata from these fields”. That seems straightforward enough - I’ll give it a try.
Re the errors you noticed in my log, the requested folders are on their way to you.
Paul, I have to say, your support is outstanding. Thank you!
Thats correct
Thanks, what is really helping is I ask you for something and you do it or send it and this just makes it so much easier to fix issues, often the main problem is working out what is causing the issue rather than fixing issue, and this usually requires a bit of help from the customer.
When I ran SongKong as described above, it failed after a short time with “Child process existed with Code 1”. I don’t know if this is relevant, but this library has about 1250 CDs in it, and about 15,000 tracks.
That should say “exited”, not existed.
Hmm I dont know, can you try again and if it fails run Create Support Files.
I don’t know about that problem but I have just uploaded new version of Songkong 8.8 Transformer for Windows which fixes the other issues found.
On Windows you must uninstall old version first, then redownload and install, the Build Date in About should now say 11th January 2023 instead of 10th January 2023