Since the new logical editor has been implemented, it is no longer possible for certain types of dynamic macros to execute, for example I had a macro assigned to a key that would open a specific logical editor preset and change CC values in 2 fields.
Since the menu item has been removed, I now have to use the setup menu every time to adjust the preset, and its not possible to open the setup with a specific preset pre-loaded for editing, adding several unnecessary steps, please can we have the ability to open presets from the menu list again?
Yes, you can execute the preset with a key command, you cannot however open the preset in the editor like was possible before via the dropdown. The only way to do this now is via the setup menu item, in this scenario you have to choose setup & type in the preset name to load it, adding 2 unnecessary and difficult to automate steps.
I have several macros that need to open the preset first, and then update variable fields, this is no longer straightforward.
@Martin.Jirsak this topic is about a function that is now missing:
The issue is that previously, if you had a preset that you want to open and adjust slightly before applying, you could
open the LE or PLE
hit the key command shortcut for that preset, and
the preset would open in the LE or PLE
This is what @method1 means when they say “dynamic macro”.
Since the redesign for C12, this no longer happens. Now, the user must fumble about using the mouse and keyboard to manually select the preset for editing.
Hi, yes the idea is to open the preset and edit it.
For example, a preset that copies 1 cc value to another cc value.
Instead of having multiple presets for each value eg preset 1 - copy cc 1 to cc 2, preset 2 copy cc 1 to cc 11 etc… which leads to making hundreds of presets, you can just have one preset and change the values, then apply. All of this can be automated, or rather, could be in previous versions, this functionality is severely diminished in the new system
I see there was an attempt to address this in the latest update, however all the new implementation does is move the menu selection that was there in the 12.0.30 iteration one step later.
It doesn’t address the issue at all, which is that it used to be possible to directly open a specific preset in the editor with a key command or other trigger.
It was a very common way for LE/PLE users to work, because we don’t create presets for every single variable of difference… We create a few presets around common averages for hotkeys, and then we create a macro that prompts the P/LE editor then loads the preset so that we can enter in exact variables.
I would imagine, if no other P/LE user has complained about this yet, it’s because they haven’t realized it yet.