ID3 tag mapping for Lyrion Classical

[kr]

I have been experimenting of late with music in DSD format saved as .dsf files, which use the ID3 tagging scheme.

I have not found a way of using either SongKong or Jaikoz to tag .dsf files for Lyrion Music Server when the GROUPING field is set. The LMS documentation states that LMS follows the itunes field/ tag mapping

TITLE            -> TIT2
WORK          -> TIT1
GROUPING -> GRP1

My test case is an album which is not detected as an opera-type by SK (correctly, as the MusicBrainz entry does not sub-divide the movements) but I would nevertheless like to do this by hand. (FYI It’s the Bach Mass in B minor, BWV 232.).

When I add the GROUPING field, this gets copied into TIT1, not GRP1 as I need for Lyrion compatibility. Changing the “Copy Work to Grouping for MP3” flag does nothing to help. The tutorial on the field->tag mapping on this site implies, but does not explicitly state that this is hardcoded.

I’m not sure at this point whether this is a request for advice on how to do this, or a support request for a change/enhancement, bit I’m sure you will advise. Could the scripter help?

The tagging works well for .dsf files where no GROUPING is involved, by the way.

[paultaylor]

Okay so back in the day the ID3 TIT1 field had a dual purpose, it was sometimes used by Classical music to store the Work, and was also used for grouping songs in others way, most typically as a extension of Genre allowing multiple genres to be stored, within iTunes it was called the Grouping field.

When we added more advanced Classical support to SongKong and Jaikoz we added a user defined WORK field to store the Work, matching what MusicBrainz Picard does.

Then, at some point iTunes added better support for Classical and decided for ID3 that TIT1 field should only be used for Works not genre grouping, and there was no longer any way to populate the itunes Grouping field from outside iTunes. That is what led to the Copy Work to Grouping Field option being added to SongKong. But maybe confusing in hindsight because for ID3 it copies to the TIT1 field which is generally considered Grouping field but no longer is by Apple, Apple considers this as Work field

Then later on iTunes/Apple Music added support for a new ID3 custom field GRP1 that is now read into the iTunes Grouping field instead so that iTunes Grouping could be updated from outside of iTunes again.

SongKong does not currently support this GRP1 field.

However the good news is a couple of weeks ago I fixed this and added an option on the Preferences:Save tab and it will be in the next release of SongKong within a few weeks