The built in Apple classical fields are separate from the classical fields used by various other players. This is done as some users populate their files into Apple and other players. Typically the non Apple fields used are Work and Part but a full list of MusicBrainz classical fields is: Cardinal Number, Classical Catalog, Opus, Part and Work. This can be confusing as there are so many classical implementations for different players.

If you're only using FLAC files you can simply remap the Work Name and Movement Name fields to whatever MinimServer requires. (Work and Movement?). If you want to do it this way go to Settings - FLAC/OGG Mappings and edit the mappings for Work Name and Movement Name. If you do it this way you can use the built in fields. ie. change MOVEMENT--NAME to MOVEMENT and WORK--NAME to WORK. Work Name and Movement Name will now map to whatever you set. This might be the easiest way for you to go. Remember that when you change the mappings, whatever you set before will not appear in the fields. They're not mapped elsewhere and will show up on the UD Text editing panel.

Alternately you can create separate fields to represent Work and Movement. Yate has lots of functionality which uses and fills the MusicBrainz classical tags. You can assign the custom fields and an editing panel to display them by importing a single edit panel. On Yate's web resources page go to the Templates section and look for: MusicBrainz Classical Editing Panel and Custom Fields.

Download the file and import the zip file via Yate>Import Settings. Follow the instructions. Once installed you can display the MB Classical edit panel as you would any other edit panel. This edit panel contains the Apple and MusicBrainz fields. More than likely what you want is Work and Part which is also used, for example, by Roon. My understanding is that MinimServer allows you to alias fields. In this case you would Alias Part to Movement. Alternately you can change the mapping for the Part custom field in Settings - General - Custom Fields to reflect MOVEMENT in FLAC files as opposed to Part.

There is no reason for you to use the MB Classical edit panel as you can place the fields on whatever custom edit panel you wish. For example there is a Roon custom edit panel which also contains these fields.

If Movement ends up differing from Part, you can always create a custom field named Movement which has the desired mapping. This field can then be placed on an edit panel.

Basically all of the above simply creates custom fields and places them on a panel to provide easy editing. (It's easier than editing them on the All Tags edit panel). The custom fields, once defined, can be displayed as columns in the main window. What this means is that if you wish you can manually create custom fields named Work and Movement , mapped to whatever you wish, and place them wherever you wish. The advantage to having the MusicBrainz custom fields is if you're going to import metadata from MusicBrainz. Use these fields as opposed to the built in Apple custom fields.

Hi, I just reread your initial post. (I'm working off a 7 hour time zone change and I'm a little fuzzy 🙂

I am struggling trying to add fields for classical Work and Movement to my local library. I intend to populate them by hand as needed in the Yate File List Area of the Main Window. I have run into an inconsistency that makes me wonder if I am still not understanding.

In Yate Help, the Yate Tag Mapping Table shows a field 'Work Name' mapping to Vorbis 'WORK--NAME'. in Settings>FLAC/OGG the field 'Work Name' maps to the FLAC/OGG tag 'WORK'. Are these in conflict? What should the correct tag be?

Settings-FLAC/OGG should have a mapping of Work Name to WORK--NAME ... out of the box. Are you sure about the mapping in settings? Unless you've intentionally changed the mappings you can do a Yate>Reset Built in Items>Reset FLAC/OGG Mappings to get back to the correct defaults.

The File List Header has columns 'Work Name' and 'Movement Name' which I expect from both help and settings.

These are the Apple fields. The FLAC mappings will need editing in order to work with MinimServer.

In the edit panel there is a UDText item (solid black circle) 'MVN' and a text value that I typed in sometime over the last two days. The text value looks like a movement name. But not the movement name I see in the file list header. Can I remove these MVN entries?

You can remove the MVN items from the All Tags or UD Text editing panels. It can also be done by a one line action. Set User Defined Text Item with a destination of MVN and an empty source.

My media server (MinimServer) recognizes indices for 'Work' and 'Movement' which I think should be Yate fields but the fields are 'Work Name' and 'Movement Name'.

MinimServer uses internal mappings of Work and Movement. Yate uses internal names Work Name and Movement Name. (These are the Apple names). Both Yate and MinimServer have to be aligned with the actual low level mappings.

The alignment can happen by making mapping changes in Yate or by defining aliasTags in MinimServer. ie. change Yate's defaults or configure MinimServer. As MinimServer does the work for you with ID3 and MPEG-4 files, all you have to do is change the mappings in Yate for FLAC files.

I don't know which of the Work and Movement tags (whatever they're called) you currently have in use in your files. If you're just starting to populate the tags, it makes it is easier as your don't have to worry about carrying over pre-MinimServer values. If you're tagging classical files you'll probably also need a Group tag in MinimServer which was introduced the same time as Work. This can be mapped to the standard Grouping tag or can be something else entirely. I'd make a new field as MinimServer's interpretation of Group differs from a standard Grouping tag.

I'll document my recommended mapping changes tomorrow. The list is not that long. Hopefully I'll be a little less fuzzy tomorrow.

Thanks for all your comments yesterday and for today's compilation and link/download. It seems like it should doable for me.

I reset the FLAC/OGG Mappings. Field 'Work Name' now points to the correct Name. I made the other mapping changes. I deleted the duplicate 'Movement Name' and 'Movement Number' mappings and removed the '-' prefix. What I have is 'Movement Name' ... 'MOVEMENT' and 'Movement Number' ... 'MOVEMENTNUMBER'. I think/hope that is correct. The panel and custom fields seem to have installed without issue. I will make my Work/Movement changes to the CD flac files that I have been testing with and give it a go. I'm cautiously optimistic.

Thanks again for the responses.

Hmm. Tag aliases in MinimServer can do the trick. However according to their documentation UDTI names which match their internal names always take priority. ie. the Movement changes should have worked. Group and Work as well.

Thanks for the update. According to the MinimServer documentation, anything which directly maps to their internal names should work. The preset for custom field Work should be interpreted correctly.