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.

For those of you who use Grouping there are really only two possible solutions if you are an iTunes user. The first is that Apple fixes the issue. You can always file a bug report at bugreport.apple.com. The second solution is ..... sorry there really is no decent second solution. In order to guarantee that no existing data is lost, every audio file using Grouping would have to have the metadata moved to a different field. All non iTunes, taggers and players which modify metadata would have to be modified to use a different field for Grouping.

The Yate Resources area has a Preserve Grouping download containing two actions which can be used to preserve your Grouping metadata....just in case.

Argh!!!!

Found it.. Thanks.. Answered my own question

I think we should all hang in there for awhile and see if sanity prevails....although I doubt it.

The only semi-workable solution I can see is to have a new option called "Use iTunes Grouping Semantics" or something else just as silly.

If the option is enabled you'd have to run a Batch Processor action once to move all your Grouping metadata to a different non standard field. Yate would then use that field for Grouping which would ensure that the metadata is not blown away by iTunes. It would also cause Yate to store Work Name in Grouping as opposed to its non standard Work field. The Grouping metadata would be imported and exported to iTunes much the same as Ratings. This implementation would allow you to go ahead and use iTunes as in the past. The only problem of course is that the Grouping metadata would not be stored in the usual place. Also changing Grouping in iTunes would not save the new values to the files...much as with ratings.

This implementation would only affect mp3 and aiff files. wav is already handled out of bounds.

Implementing this is of course a pain but it is not insurmountable.

Any thoughts?

Yate v3.14.3 has a workaround via the new Preferences-iTunes-Maximum iTunes Grouping-Work Name Compatibility setting.

There is a new help topic named: iTunes, Classical Metadata and the Grouping Field

the work/grouping debacle by itunes might be the last straw for me. what are other players for mac besides itunes that display the Grouping field? thanks