INFO: SongKong Pro Music Tagger 20% Discount for Roon Users

SongKong 12.2 Introspective is now available, please use DOMINODANCING code for a 20% discount on both new purchases and extending version updates.

This brings significant performance gains, improved Classical matching accuracy, enhanced icons, smoother MusicBrainz release retrieval, and a range of other refinements.

Also I recently came aware of how Anti-Virus software can impact SongKong performance, have a look at this article I wrote to check this is not happening to you.

Includes over 20 other improvements and fixes

SongKong 12.2.1 Introspective is now available, please use DOMINODANCING code for a 20% discount on both new purchases and extending version updates.

This has a number of fixes and Improvements including fixing a regression with file renaming and functions, a fix for Opera Work handling, a fix for Discogs Matching and performance improvements for low powered servers

Does anyone have experience running this on a large library after it’s already been integrated/added to Roon? I would like to use this - as I have more or less relied on Roon to “tag” my digital music collection. The issue is that using these same tracks with some other player like plexamp exposes the issue that the tracks might not be actually correctly tagged outside of Roon. Ideally I don’t want Roon to freak out after using SongKong thinking all of the my music has suddenly changed and it needs to fix them.

So - anyone have experience here?

Not an issue but by design Roon never writes to your audio file tags but to its own db

SongKong will write to you files but has a preview function so that you can see what is GOING to be written before you commit.

Whilst I like SongKong I would be wary of letting it loose to write at will , you may get more metadata than you want

@paultaylor wrote SK so he is best to advise before such a major venture !!