NEW: added management of custom field values independent from Tag Panel fields

[ohrenkino]

I do not see that any data is

@Sergius

moved to the "Tag Panel"

but you create a list of values that you can take as reference values that you like.
This is no replacement for actions of the the type "Format value" - this was the suggestion in the old days if users asked for pre-defined values for certain fields.
see e.g. this thread for the old way to get pre-defined values:

User Defined Values

The work around that I'm using is similar to your master record - template idea. I created dummy mp3 files, one for each value that I wanted to show up in the drop down box and then made the files read only so the values wouldn't change. So now when I want to tag some actual files, I select the dummy files along with the ones I want to update and all the values I need show up in the drop down box. I'll do anything to avoid typing. It would be nice if I could provide the values in an …

I still wonder what the workflow would look like that needs to move values.

[Sergius]

Thanks @ohrenkino for the link. I'm going to write the same thing the user did back then… I don't understand it 100%.

I see it's from 2010. I know that "Custom Field Values" didn't exist then; you could only add data to the Genre tag, I think…

@ohrenkino

I still wonder what the workflow would look like that needs to move values.

ohrenkino, I don't have your expertise in this area; I'm very limited on this subject…

[ohrenkino]

@Sergius

you could only add data to the Genre tag, I think…

That would have been a catastrophe if you could have added data only to the Genre field.
What users requested was a list, preferably filled with user-defined values, like the predefined, standard genre list and to be able to select from these values.
The only way to achieve that those days was to create a collection of actions of the type format value.
Now, with the function to select values from exactly such a list of pre-defined values, all fields may behave like the formerly only the genre field.
This feature has been around since 2023.
New is only that now the list of user-defined values is independent from the presence of a field in the tag panel.

I still wonder which problem you have with this separation and which workflow you have in mind that might benefit from the added management of custom values but apparently does not.

[Sergius]

Hello @ohrenkino,

Thank you for the information. I appreciate your help and @LyricsLover's help with this.

I submitted my request to Florian, and I'm very happy he wrote to me about it. I'm waiting to see what he decides regarding this feature request.

[Florian]

@Sergius

Example: The field EYE_COLOR_LEAD_SINGER is only written to the "Field Values" section. I can't use it to write to my audio file. This field, it seems to me, must be located only in the "Tag Panel" for the data to be written to my audio file.

You can use it, both directly via Extended Tags or if it's configured as a column in the File List. It doesn't need to be added to the Tag Panel, only if you want to edit it from there.

@Sergius

Yes, a kind of button that adds the new field EYE_COLOR_LEAD_SINGER from the "Field Values" section. Along with the "Custom Field Values" data (Green, Blue, Black), it would then that adds to the "Tag Panel" if that data no longer exists in the section.

While this seems to be a nice quality-of-life enhancement from some users, I currently don't want to add this. You can simply select the same field name when adding the field to the Tag Panel.
And as soon as you add a field to the Tag Panel, all the custom field values associated with that field are instantly available. There is no need to copy the custom field values.

[ohrenkino]

@Florian

While this seems to be a nice quality-of-life enhancement from some users

In a way I have the impression that this goes into the same direction as this suggestion:

Neue Elemente erzeugen in Tag Panel und Dateiliste direkt aus Erweiterte Tags

Welche wären das konkret? (Ein Screenshot aus MM und Alt + T in Mp3tag vom gleichen Song wären hilfreich). Sogar die selbst-definierten Felder in MM lassen sich in Mp3tag verwalten, z.B. mit COMMENT SONGS-DB_CUSTOM1. Guckst Du auch hier:

which means: add the tag panel and filelist element creation to further dialogues that list field names, e.g. the custom value list and the extended tags dialogue.

[Sergius]

Hello @Florian,

That's great! I just did some testing, for example with the "Start Time" label. With many field values, I removed the "Start Time" label from the tag panel, but it remained saved in the field values.

In the tag panel, I added the "Start Time" label, as you instructed: all the associated custom field values ​​instantly appeared in the "Start Time" label in the tag panel. It works perfectly!

Great job on this new "Field Values" command!

This allows me to test custom labels with field values, which I can then remove from the tag panel after my tests.

I can label my audio files normally, and when I want to do a test, I add my test label to the tags panel, which then displays the field values, because the test label is still saved in the field values.

Thank you for keeping my request "on your wish list," if I may put it that way, for the "Field Values" section and the ability to copy tags to the "Tag Panel."

This could prove useful in the future, especially for users with multiple tags in the "Field Values" section. They could then copy these tags to the Tag Panel if they aren't already there.