Audirvana displays extended fields for Conductor, Ensemble, Solist, Instrument, Style and Period.
With the exception of Conductor, the fields are viewable in Yate as User Defined Text Information items.
For ease of use the fields, other than Conductor, can be mapped to Custom fields. This will make them easier to access in actions and will enable them to be displayed on Custom Edit Panels.
Unfortunately there are two common mappings used for the m4a field mapping for Conductor. By default Yate uses CONDUCTOR and Audirvana uses Conductor. If you want Conductor mappings to be mapped as in Audirvana you will have to select Conductor for the Preferences-Audio-MPEG-4-Map Conductor to option. If you select the Read both, you can not make sure that Yate reads the conductor metadata regardless as to how it is stored in the files. Choosing the Audirvana Plus item in Preferences-Audio-Common Application Presets menu will set this and various other Audirvana Plus compatibility settings.
if you want to ensure that conductor is saved as Audirvana expects, you can run a simple one line action through the Batch Processor and re-save all your files. The Force Save Files sample action is provided which you can use.
If you open the Custom Panel Editor, you can import the AudirvanaMapping.plist file via the Import/Export function button. This will result in a Custom Panel displaying the Audirvana Plus extended fields. The custom fields will be created at the same time.
Content List:
Custom Edit Panels: 1
Custom Field Definitions (smart)
Requirements:
Yate v4.6
History:
2015-02-09 First release.
2017-05-03 Removed redundant CONDUCTOR -> Conductor action.
2018-04-03 Update for v4 custom fields.
2019-02-09 Updated to reflect the current A+ extended fields and to supply APE mappings.