I’m about to bite the bullet on Roon, and I want to sort out the minimum set of metadata tags for my modest classical collection to ensure (hopefully) a smooth transition into Roon. Is there a mapping of SongKong metadata against Roon metadata documented somewhere I can use as a starter?
Thanks, Ian
So we don’t have a current Roon mapping, the default settings work pretty well, but there is possibly an issue with using the Performer field for Flac files
Its something I am keen to do, just that other things have got in the way.
But why do you specify a minimum set, adding textual metadata to the files adds very little in addtional size ?
Paul,
I was just hoping that Roon would provide the rich metadata once I gave it enough info to “find” the album. I have now run all the albums through SongKong and the metadata is much richer now. I’m happy!
One issue - I’ve sent you the Support Files - on two albums, not all the tracks load into SongKong. When I look at the albums in Edit Metadata, each of the two has missing tracks - they are visible in the OPEN folder dialogue box, but are not listed in the tracks for editing. The report file lists the 6 tracks not loaded, due to “invalid identifier”. Any idea why these few tracks are refusing to load?
Cheers, Ian
SongKong works with Roon in two ways, it makes it easier for Room to identify albums as you describe. But also it means for the albums Roon still cannot identify it will display the better information that SongKong has added. So it is best to add all metadata unless any fields actuaĺly cause a problem for Roon. It also means your songs sre in a better state if you want to use them outside of Roon
I will look at the support files tomorrow.
Okay so they are mp4 files and there is some problem with their data preventing them being read, I assume they play okay, generally the requirements to play a file when you only need to read a file are less onerous than when you need to read a file in order to modify it.
So there are two things you can do:
Hi, thanks for sending the files, Mp4 are stored as a tree of atoms and your files have an extra atom at the end of nonsense data (see last line of output below)
Atom ftyp @ 0 of size: 32, ends @ 32
Atom moov @ 32 of size: 323391, ends @ 323423
Atom mvhd @ 40 of size: 108, ends @ 148
Atom trak @ 148 of size: 194712, ends @ 194860
Atom tkhd @ 156 of size: 92, ends @ 248
Atom mdia @ 248 of size: 194612, ends @ 194860
Atom mdhd @ 256 of size: 32, ends @ 288
Atom hdlr @ 288 of size: 34, ends @ 322
Atom minf @ 322 of size: 194538, ends @ 194860
Atom smhd @ 330 of size: 16, ends @ 346
Atom dinf @ 346 of size: 36, ends @ 382
Atom dref @ 354 of size: 28, ends @ 382
Atom stbl @ 382 of size: 194478, ends @ 194860
Atom stsd @ 390 of size: 32886, ends @ 33276
Atom mp4a @ 406 of size: 32870, ends @ 33276
Atom esds @ 442 of size: 51, ends @ 493
Atom sbtd @ 493 of size: 15, ends @ 508 ~
Atom stts @ 33276 of size: 24, ends @ 33300
Atom stsc @ 33300 of size: 40, ends @ 33340
Atom stsz @ 33340 of size: 154480, ends @ 187820
Atom stco @ 187820 of size: 7040, ends @ 194860
Atom udta @ 194860 of size: 128563, ends @ 323423
Atom meta @ 194868 of size: 128555, ends @ 323423
Atom hdlr @ 194880 of size: 34, ends @ 194914
Atom ilst @ 194914 of size: 124507, ends @ 319421
Atom ---- @ 194922 of size: 86, ends @ 195008
Atom mean @ 194930 of size: 28, ends @ 194958
Atom name @ 194958 of size: 21, ends @ 194979
Atom data @ 194979 of size: 29, ends @ 195008
Atom ---- @ 195008 of size: 162, ends @ 195170
Atom mean @ 195016 of size: 28, ends @ 195044
Atom name @ 195044 of size: 20, ends @ 195064
Atom data @ 195064 of size: 106, ends @ 195170
Atom ---- @ 195170 of size: 188, ends @ 195358
Atom mean @ 195178 of size: 28, ends @ 195206
Atom name @ 195206 of size: 20, ends @ 195226
Atom data @ 195226 of size: 132, ends @ 195358
Atom aART @ 195358 of size: 109, ends @ 195467
Atom data @ 195366 of size: 101, ends @ 195467
Atom cnID @ 195467 of size: 28, ends @ 195495
Atom data @ 195475 of size: 20, ends @ 195495
Atom covr @ 195495 of size: 122978, ends @ 318473
Atom data @ 195503 of size: 122970, ends @ 318473
Atom cpil @ 318473 of size: 25, ends @ 318498
Atom data @ 318481 of size: 17, ends @ 318498
Atom disk @ 318498 of size: 30, ends @ 318528
Atom data @ 318506 of size: 22, ends @ 318528
Atom plID @ 318528 of size: 32, ends @ 318560
Atom data @ 318536 of size: 24, ends @ 318560
Atom purd @ 318560 of size: 43, ends @ 318603
Atom data @ 318568 of size: 35, ends @ 318603
Atom shwm @ 318603 of size: 25, ends @ 318628
Atom data @ 318611 of size: 17, ends @ 318628
Atom soal @ 318628 of size: 67, ends @ 318695
Atom data @ 318636 of size: 59, ends @ 318695
Atom soar @ 318695 of size: 91, ends @ 318786
Atom data @ 318703 of size: 83, ends @ 318786
Atom sonm @ 318786 of size: 77, ends @ 318863
Atom data @ 318794 of size: 69, ends @ 318863
Atom stik @ 318863 of size: 25, ends @ 318888
Atom data @ 318871 of size: 17, ends @ 318888
Atom trkn @ 318888 of size: 32, ends @ 318920
Atom data @ 318896 of size: 24, ends @ 318920
Atom ©ART @ 318920 of size: 91, ends @ 319011
Atom data @ 318928 of size: 83, ends @ 319011
Atom ©alb @ 319011 of size: 67, ends @ 319078
Atom data @ 319019 of size: 59, ends @ 319078
Atom ©day @ 319078 of size: 44, ends @ 319122
Atom data @ 319086 of size: 36, ends @ 319122
Atom ©gen @ 319122 of size: 33, ends @ 319155
Atom data @ 319130 of size: 25, ends @ 319155
Atom ©mvc @ 319155 of size: 26, ends @ 319181
Atom data @ 319163 of size: 18, ends @ 319181
Atom ©mvi @ 319181 of size: 26, ends @ 319207
Atom data @ 319189 of size: 18, ends @ 319207
Atom ©mvn @ 319207 of size: 31, ends @ 319238
Atom data @ 319215 of size: 23, ends @ 319238
Atom ©nam @ 319238 of size: 77, ends @ 319315
Atom data @ 319246 of size: 69, ends @ 319315
Atom ©wrk @ 319315 of size: 64, ends @ 319379
Atom data @ 319323 of size: 56, ends @ 319379
Atom ©wrt @ 319379 of size: 42, ends @ 319421
Atom data @ 319387 of size: 34, ends @ 319421
Atom free @ 319421 of size: 4002, ends @ 323423
Atom free @ 323423 of size: 310814, ends @ 634237
Atom mdat @ 634237 of size: 24546347, ends @ 25180584
Atom +2SÑ @ 25180584 of size: 85331, ends @ 25265915
SongKong trys to traverse the tree to check its valid, if we removed this check then we could read the file but then the risk that we could do damage when we write to the file. There is probably something we can do but would need some thought
Workaround
Use a tool such as DbPoweramp to write the file to a lossless format (wav, flac) and then from the new file back to an Mp4 this should resolve the issue.