With the release of iTunes 12.5, Apple added support for metadata fields to make it easier to organize classical music. New metadata fields were added to the iTunes library for Work Name, Movement Name and the Movement number.
In m4a files, the new support was in our opinion implemented in the best way posible. The new metadata is stored in the files and iTunes reads and writes the data. Unfortunately, no "file" support was implemented for other audio file types. This means that the metadata associated with the new fields could be retained in an iTunes library but was not read or written from the actual audio files. As the new fields were mostly supported by the iTunes AppleScript interface, the values could be pushed and pulled.
In iTunes 12.5.2, Apple made a fundamental change which will affect the iTunes libraries of many users. The Work metadata is mapped to the Grouping field in supported ID3 based audio files. (ID3 TIT1 frame). This data is read and written. What this means is that any ID3 based supported audio file (mp3, aiff) will have its Grouping data appear in the Work field. Whenever you edit metadata in iTunes, you will lose the previous Grouping data stored in the files.
Aside from the general loss of data, this issue also introduces a definitive difference in the way metadata is meaningful in different audio formats. In m4a files, Grouping and Work are distinct data points. In mp3 and aiff files, there is now only really Work support. Grouping becomes meaningless as it is constantly overwritten.
Some people will note that you can still manually set the Grouping metadata in the iTunes library. That is true. In fact you can still programmatically set the Grouping data. However, you cannot save the data in the audio files.
The Preserve Grouping download contains two actions which will allow you to save the Grouping metadata in different ways. Preserve Grouping Metadata in Files saves the current values in the audio files. Non empty Grouping values will be saved to a UDTI named Saved Grouping. Preserve Grouping in Database creates a CSV database where each row contains the Grouping, FilePath and Yate Track ID (if present).
Both actions are designed to be run through the Batch Processor Wizard. When running the Preserve Grouping Metadata in Files action, you must select the Auto Save Files option.
Content List:
Actions: Preserve Grouping Metadata in Files
Actions: Preserve Grouping in Database
Export Sets: Grouping Fix
Requirements:
Yate v3.14.2
History:
2016-11-08 First release.