feature request: select from predetermined tag set for custom fields

[Zerow]

@mp3tagz

[...]
What about the case where a collection has 10,000 Artists and just as many albums? How long should the dropdown list be? To some extent, I think you're missing the point of this feature request in two ways.
[...]

Well I would for example put such things in the ARTIST tag field, to be chosen from:

 feat.
 feat.  &
 vs.
 interp.
 interp.  cond.Especially the >> interp. << would be usefull to me because for me it stands for interpreter / interpreted by, and sometimes I write this down wrongfully [as for example >>interpr.<< or >>intepr.<<]; and that creates problems further on. And where I am in Tag Panel I have the pointer somewhere on Tag Panel and it would be quicker for me to choose something from the drop down tag field  menu than from Actions. Especially that is true when I add a completely new stuff and I go from field to field, one by one [and so the pointer needs just a small movement]. And if there were drop down menus I bet I could use them with keyboard, thus utilizing something more than just the Tab button on it during such work

It is all those little adjustment that make the overall time spent in Mp3tag less tedious and save hours of your life in the very long run

@mp3tagz

[...]It's been said that the best workaround possible is to use Actions. But then this makes working with mp3tag very tedious, because now I have to constantly maintain a growing list of actions just to have well-formed tags.
[...]

So I am not the only one? So I am not imagining things; how they can be better that is?

@Zerow

[...]
Because maybe the user is tagging some specific files / body of work, not necessarily musical, that requires only few options?

Or for example deals with a specific period of time mostly and so a list of something like 10-15 years would cover the area of interest in regards to the YEAR tag field?

@ohrenkino

So we are back at the point where the most feasible solution is to create the required number of actions.
[...]

I have 47 entries under the Action button. Few of them contain sub-menus on purpose and some of them group in a such sub-menu things that are rarely used by me but still have to be done with an action

Most of those rarely [and some of the frequently used] are added to some sub-menu because they need to be put somewhere, so that they do not create a 48th, 49th etc. entry under the Action button. Because 48 entries would fore me to scroll the list- and that takes time and is simply a drag, going all the time up and down through such list. And on top of that I have some issues with list exceeding the vertical space of one screen: /t/18377/1

Everything that I could move to tag fields from Actions [adapt sub-menu in Actions to a form of a drop down list in Tag Panel would be of help

@mp3tagz

[...]
The answer has been a staunch "no!" since 2009, which has likely driven users away. I would respectfully ask Florian to reconsider.
[...]

I just do not comprehend this. Tag for GENRE can be pre-defined as an option and it is an A-OK approach / feature; but the minute someone signalizes the obvious extension of that feature to the rest of tag fields, or at least to fields like DISCNUMBER or YEAR, it is viewed by some of the experienced users as a useless overkill. How come? Because "there are just 256 pre-set values for genre as they are defined in the ID3 standard"? [Request:Pre-defined menu's]

So if somewhere in the 1990's creators of ID3 would decide, that the YEAR field should also be populated with values ranging from 1914 to 2014, because [I'm totally speculating here] they knew of the oldest recording to be from the year 1914, then today in Mp3tag this field also would have a ready to use drop down list; that could be supplemented by user with new values [1913, 2015 etc.]? And then it would be OK to have this option for YEAR, and to be able to turn such menu off [as it is now possible for GENRE tag]? And so, we would have an argument in this discussion, that those only 101 pre-defined values for YEAR and 255 values for GENRE are manageable and useful- but for other fields such option would not have a sense to implement it, even if it would be entirely up to user how strongly such lists would be populated and with what?

Well, for me those 256 genres seem like a big number and I am stunned that they did that at all. But then again when I look at them in the Tag Panel, that quarter of thousand of variables is easily [alphabetically] manageable. So I can easily imagine that I could create a list with 2000 positions, that would cover all off my primary artist [that are the main performer of at least one song / composition and thus have a folder of their own on my musical drive]. I am not saying that I would or should, but I wish I could

You can filter your files by using the Filter Box and you can "filter" them with a column with a proper values set for it. Depending on your needs and skills, you use the first method, the second or both- whatever you like / need / can. So why it is a blasphemy for some to imagine that some users would make some usage by implementing multiple simple format value "actions" [i.e. drop down menus] in the Tag Panel?