The very short version
Tagging scripts in the context menu isn't sorted properly. It would be nice if they were. Just like they are in the "tagger" itself.

The not so short version
Close to a year ago musicmusic announced:Something I find very understandable, especially considering the steady progress of UI Columns.

The ability to run tagging scripts from the context menu is a great addition. And this is something I missed in earlier versions.

But, to me, foo_quicktag wasn't just a replacement for the missing context menu integration. It was more of what the name suggests, namely a component for doing some quick tagging(*). It had the advantage of being able to add sub menus/groups to the context menu, something that made it alot more scalable. I would say you push the limits of the current scripts integrated in v.0.9, when you exceed 30 scripts or so. Even below that, it requires a sensible use of prefixes (to names) to group related scripts.

In addition to the scalability, foo_quicktag's sub menus had the advantage that you could add the most frequently used actions to it's own group, and this group could be moved out to the first level of the context menu.


(*) Examples of how I differentiate between the two, when it comes to area of application:

foo_quicktag

• add rating (%trackrating%)
• add discnumber (%disc%)
• set genre (hard rock, heavy metal, metal, gothic, death metal...)
• set sort_genre (my own crude categories like HARD, PUNK, RAP, POP, for use with e.g. Album List and Playlist generator )
• mark as singletrack and such

for short, editing that constitutes of assigning a simple value.
My foo_quicktag had 87 entries.

tagging scripts

• guess tags from filename/path (quite a few different versions)
• format from other fields
• replacements

for short, editing that require more advanced processing/parcing.
My old masstagger had about 30 scripts.


All this boils down to the following simple question:
Would it, in some way, be possible to add support for sub menus to scripts?
I personally consider this more optimal than a recompiled foo_quicktag, as it reduces the number of "required" 3rd party components one needs to keep track of.


Thanks for taking the time to read this.

It really could be extended beyond that. Just add the ability to create menu items in the UI, and you've solved more problems even than the ones you mentioned. You don't have to be able to create your own commands, just be able to reference them. It can't be that difficult to add the ability to select a function from a list, it's implemented all over the place (browser, album art, status bar, play lists, trackinfo, album list...), this would only be carrying that feature over to the menu editor. I honestly don't see why it wasn't like that from the very beginning.

if you could add the masstagger scripts as individual commands in the current context editor it would work perfectly. the ability to create groups is already there, but every masstager script is constrained to a single flat group.