I just tried eCustom 2.1 and CustomField tagger. Thanks to their authors.
Is there a way to edit the custom field name, in addition to setting their value?
It seems the scripts only write values in CUSTOM1, CUSTOM2, ... fields.
I modified the FieldList and FieldListDB arrays in the CustomField tagger script but I had SQL errors trying to access non-existing properties in MM DB, such as LABEL or ORGANIZATION ("PUBLISHER" works obviously).
I am not an expert so I won't go further in understanding and editing the script. I think that MM and its DB would need to be modified internally to take into account any custom field set by users or other software rather than using predefined and software-specific CUSTOM# fields. The sames goes about reading tags from files.
I would like to manage the non-standard LABEL (=ORGANIZATION) and LABELNO (Catalog number) fields in MM and potentially any field on Vorbis comments (and id3 eventually).
In Vorbis comments the LABEL field is:
- Used exclusively by Tag & Rename to handle record label information (including LABELNO), no support of ORGANIZATION
- preferred by dbPoweramp over ORGANIZATION if both fields are present. Some info hidden in specific conditions here
- read/written by mp3tag with a total flexibility, provided that you are aware of conflicts between LABEL and ORGANIZATION across software.
MP3tag has indeed very flexible way (the best? ) of handling custom tags as it allow a total customization of field display, allowing to display these fields separately or setup rules such as $IF(%ORGANIZATION%,%ORGANIZATION%,%LABEL%), optionally associated with id-tag specific mappings of field names.
In this grey area we all end-up using non-standard tags for different reasons and it would be great to see the MP3tag approach in use in MM.
I opened a ticket to discuss my specific issue with the support team.