Script Tag: More Fields & Edition

Script Tag is a very useful feature.

The idea of a combination of values as a list is very interesting, but I think that separate text segments in midiscript is a little bit tricky.

It would be easier IMO to have some numbered tag fields in the scripted button/dial, so we could have a small list of items directly from e_tagX (entering 1 item per field).

Suppose we have 4 tag fields in every scripted button/dial shown as:

Scrip Tag 1
Scrip Tag 2
Scrip Tag 3
Scrip Tag 4

Then we could get the values like this, and use them directly in the script (no need to build the list dividing text segments with delimiters):

Scrip Tag 1: e_tag or e_tag1
Scrip Tag 2:e_tag2
Scrip Tag 3:e_tag3
Scrip Tag 4:e_tag4

So I could enter the following values to create a list of four items that I can use directly in the midiscript:

Scrip Tag 1: “SELECTED TRACK” (name of the active profile)
Scrip Tag 2: “2” (number of active page)
Scrip Tag 3: “8” (total pages of the active profile)
Scrip Tag 4: “BANKS VOLUME” (name of the previous profile)

This idea would be also handy for users that want to make different class lists per tag.

For instance, a user could use the first field for any list of text (title, values, etc), second list for colors (background, fader, level):

Script Tag 1: “/SC FILTER/HP FILTER 21-500Hz/ENABLED/DISABLED”
Script Tag 2: “111111/424242/656565”
etc.

I forgot to also ask for an action to edit the tag/s fields from the midiscript.

Suppose I have 1 midiscript in 30 different profiles and I want to edit all the 30 tags (for instance I want to substitute the text “BTT-” for “KM-”).

Doing that manually would take more time than adding this code to the midiscript (and then switching the 30 scripts for rewritting the tag):

[(init){@l_tag:#@e_tag#}{@l_tagEdited:changeTheText}{newActionToWriteTheeTag:#@l_tagEdited#}]

More of everything is always better, right? :laughing:

I see what you are getting at, but not in this release, at least. I want to close this release and publish it within a week or so, so I don’t want to add any new features.

I think your examples are a bit questionable.

A list in midiScript is a comma-separated string. The tag can be a comma-separated string. Why divide it into 4 tags and go to the trouble of rebuilding the list in the script, instead of just having the comma-separated list in the tag?

In my view, the tags should have information unique to the button/dial, not the same information in all tags. “BTT-” should be in the script, so you can change it to “KM-” in one place.