I remember there is a rule operator that allows for a list. Can’t find it now.
Something like qq=(1-4). So qq would output 1,2,3,4 (all four numbers).
I wonder if I can do a preset activate translator, output by number as qq.
And in the rules have this multiple numbers list. So if qq=(50-55) then all those presets would be activated with that one translator.
You need to use a timer. See the attached example.
Note 0 iterates through the ‘Enable’ timer, enabling/activating presets 1-5.
Note 1 iterates through the ‘Disable’ timer, disabling/deactivating presets 1-5
I use the global variable gc for the counter. If the presets are not in sequence you could use the variable gc and map it to the desired preset number you want to disable instead of just using the original value of pp.
Ok. I put the variable in the translator that triggers the timer.
So I put od=78, the first one that will be deactivated.
I put the timer to repeat 24 times. Then in the preset deactivate translator, the pp=od. od=od-1.
So presets 78 to 54 are deactivated with that. I just have to make my math right.
Well I guess this works. A couple translators is better than like 20.
The deactivate preset menu should have checkboxes to have multiples affected with one translator.
Yup. In regards to presets, font colours would be nice. I would make each controller have a colour.
And preset sub groups. The “always active” preset switching feature could be per group, etc.
There could be an preset output to chooses a group instead of presets themselves.
And translator colours. And headings (dividers) for translator groups, that aren’t translators themselves. And outputs that can disable translators without having to use preset switching.
And a rule processing delay operator. So an output can execute before the rule line in question is processed.
And alternating line shading. And background brightness level. And custom font size, column reordering and automatic “resize columns to fit”. Sadly Microsoft still hasn’t figured out how to always resize columns to fit, even to this day.
And stop flags coloured red, with the rest of a translator sequence greyed out when a stop translator renders them useless.
And a lot better variable management. A dedicated variables manager window with a search function, with in use/not in use filters. When creating rules and typing them in the rules they would turn red when already in use somewhere else. Double clicking would open the manager window showing the places they are used. We could also give names to variable groups: (la - lr is ‘browser timer’) etc.
Ok nice. I forgot my top suggestion:
Giving MTP a mouse click and return feature, so we could have mouse click macroes without having to use MIDI Buddy; flooding MTP always with unnecessary messages.
MTP can already track a mouse position. We know that because of the “windows inject events” capture box. It’s just a matter of adding an input and output feature (in the “Mouse” part of it) for “get mouse pos” and “return to pos”.
Actually I might be able to buy a few mods to MIDI Buddy (finally).
I will have to maybe buy one thing at a time, as the CAN to USD currency conversion kills me.
Could I PM you somehow? Use that email, bome@sniz.biz ?
Hi @SuperTRev , thank you for the many many great feature requests! As Steve indicated, some are already registered (and I’ve bumped up their prio), but others are new and nice. We’ll report back here whenever such a suggestion makes it into the product.