Send me a file with whatever information you can. Links to their information would help. I'll take a look after v3.2 gets out the door.

support@2manyrobots.com

Thanks for the file. The fields are there and available. 🙂

They are stored in exactly the same manner that Yate stores User Defined Text Information (UDTI) fields in m4a files. One would assume that the custom tags are stored with the same approach in mp3, flac, etc. files honouring each formats peculiarities.

They are available now on the UD Text editing panel. You can create them, edit them, get at them from actions, etc. You can map three of them as custom columns in the main file window via Preferences-File List-Mapping and Custom Field Names. The only thing you cannot do, for now, is map them onto custom editing panels.

There a few options on how to handle this. I can support the direct mapping of UDTIs onto custom panels or I can allow you to override the default UDTI mappings assigned to the five Custom fields. Custom fields are really just a convenience to make it easier to access UDTIs in actions and display them on Custom editing panels.

From what I can tell by searching on Google, there are six of these classical custom fields which are used. I can easily bump the number of custom fields. Regardless, it appears to me that the way to proceed is to extend Yate's customization a little further (sigh). Hard mapping your six commonly used custom fields would more than likely cause issues 'hard coding' other apps usage of various fields.

Does this make sense?

Here's a temp[late for the 'prompt' action.

Prompt for Text "Enter a value for Conductor" save text to Variable 1
Import value of User Defined Text Item Conductor (Create) from Variable1

As the action is run stepwise it will set the Conductor in all selected files. If you always load albums at a time you should probably select 'All Files' in the Action Manager as it will eliminate the selection step.

The above action can be modified for any of the other fields by changing the prompt and by changing the name of the UDTI field in the User Defined Fields statement (the 2nd). I did not specify 'case insensitive' as I'm not sure if Audirvania treats the names as case sensitive or not.

A more generalized action which loops (for a while) and lets you enter values for any of the 'six' extended fields can be found at:

http://2manyRobots.com/actions/PromptForExtendedClassicalFIeld.zip

Unzip and import the plist by dragging it to Yate's main file list. You will now have an action named 'Prompt for Extended Classical Field'.

Through each loop iteration enter #-value or Cancel.

If you have actions you'd like to share send them to me with a brief description and I'll post them.

10000 tracks open at once. May be time for batch processing. 🙂

BTW: UDTIs can now be mapped to Custom Edit panels.

If you want to do it in the Multi Field Editor you'll have to map Soloists to a Custom field. If you go to Preferences-File List-Configure Column Mappings and Custom Fields-Custom Field mappings, you'll see "Choose commonly used mapping". You can pick Soloist from the list. Once mapped, you can access the custom field you chose from anywhere.

The only method without a custom field mapping is to use an action:

Copy the Grouping field to Variable 1
Import value of User Defined Text Item with name 'Soloists' from Variable 1

Note that I've used the common display name as I don't know what audio file type you're using. The correct UDTI names are:
ID3 --> soloists
m4a --> soloists
FLAC --> SOLOISTS

If you are not going the 'custom field' route I suggest you create a FLAC mapping of 'soloists' to User Defined Text Info, which will allow you to use 'soloists' without knowing that the FLAC file contains 'SOLOISTS'. (It will still be written as SOLOISTS to FLAC files)

There are now 10 custom fields available so you can use the custom field method described above to define Audirvana's Ensemble, Instrument, Period, Soloist and Style fields. This more than likely gives you the best going forward options. I don't know if you are using m4a files but if you are there is a slight issue. About 50% of the applications out there use Conductor as the m4a UDTI name while the other 50% use CONDUCTOR. These names are case sensitive. Audirvana uses Conductor while Yate defaults to CONDUCTOR. You can change this in Preferences-Audio-m4a-Map conductor to.

Hopefully this gets you where you want to be. 🙂