Custom fields tab
Custom Fields allow you to control how custom fields on tags are read and mapped to a specific field.
Change the display name to specify how the name of a custom field should appear in Helium's tools and views.
You can map a custom field to a specific tag field/frame by entering the name of the field in the Map to Frame text box.
When a field is mapped, its contents will be mapped to the custom field when reading tags.
This can be useful to enhance compatibility with tag fields not natively supported by Helium.
Custom field mappings operate only at the tag level, meaning the mapping is applied when tags are read or written.
In most views in Helium, the data presented is read from the database rather than from tags directly, for performance reasons.
The exception is the My Computer views, which always work with tag information directly and will apply the mapping when reading files.
Mappings are also applied when loading data into the tag editors. If a mapping was applied when files were loaded in the tag editor, it will be applied to the custom field when saving.
To work with aggregated or mapped fields using database data, use the Custom Columns available from the Columns tab.
Columns tab
Custom Columns allow you to create up to tencolumns with fully dynamic content. The templates used for these fields will apply the rules from Tag to Filename to render the content.
Release types tab
Release types allows you to configure the names of the five custom release types.
Release type tag-frame mappings tab
Release Type Tag-Frame Mappings allow you to control whether and how the value of a specific tag frame should be converted to a release type during reading.
Example:
A file contains a TXXX tag-frame named "releasetype" (key) with the content "Maxi / Single."
To remap all TXXX frames matching the key and value "Maxi / Single" to Helium's release type "Maxi," enter "Maxi / Single" (without the quotes) in the Value field for the "Maxi" release type.