SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Interaction with MusicBrainz database

I just added this one https://musicbrainz.org/release/55e10969-b484-424a-bb2a-b6645568d9dc
MB only had two tracks matched to work_compositions so I linked all the others. SongKong did not give any work or movement tags for any of the tracks, except for the MUSICBRAINZ_WORK… tags for the two tracks already linked. Just trying to understand why this is the case. Does it require the existence af the MB tags to trigger the work/movement tagging? Why were the two linked tracks not tagged with work & movement - because they were isolated tracks?
Now I have added all the links, I assume all the tags will get added after I run SongKong again, once Albunack has been updated - what is the frequency of this?
Ta.

SongKong can make use of MusicBrainz works or try and parse the titles. It cannot parse these titles since it looks for a ‘:’ to indicate work:movement division. In this case it realizes that the ‘:’ indicates a composer:title division (it checks the value before the : against composer list) and knows it cannot use this. In these titles the division is done using ‘,’, but we do not have handling for this, I think it would be too difficult since ‘,’ is used for far too many things.

Its difficult to say why they were not matched without having the actual files, but check that SongKong did identify them as Classical by seeing if the is-classical field is set. If t his is the case there are various ways to force songkong to identify as classical such as the Identify Classical Releases option.

Currently Albunack is updated monthly because:

  • Discogs data is only available monthly
  • Still making improvements to albunack (such as piano arranger), therefore need time to make changes.
  • Database has to be rebuilt from scratch (not just new data added) because builds additional relationships

But since the MusicBrainz data is available daily I would like to rebuiold the database more often but I need to speed up the database creation and make it a one-click process.

BTW ran into issue with pianoarranger fix but expect that and the partialrecordings issue to be fixed by the end of today.

Is_classical was set. I suspect that Work and Movement were not set as there was no colon in the title. My Mp3tag script did pick up the MusicBrainz tags and create the work and movement for Muso - but just for those two tracks of course.
Now I know how Work and Movement are derived, I won’t bother adding “split title” logic in my Mp3tag script unless I come up with an idea about how to handle commas - they are a pain - in which case I’ll share it. I do think MB could tighten up the style guidelines around punctuation.