Open an LE or PLE preset via a standard menu and key command without applying it

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?

1 Like

Hi,

You can call the Project Logical Editor Preset as a command the very same way, as it was in previous Cubase versions.

Could you please describe your Macro exactly (which steps are in; maybe a screenshot)?

Hi Martin

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.

Here is another user with the same issue: Project & Midi Logical Editor access changes in V12 - why?! - #2 by fese

@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.

Significant loss, imo.

4 Likes

Hi,

Thank you for the explanation, @Steve.

What is the use case, please? Why do you want to open the preset in the LE/PLE window and not to apply it immediately? Do you want to edit it?

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

2 Likes

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.

Any plans on updating this or restoring this functionality to the logical editor?

Yes, please fix this!

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.

2 Likes

+1 For this, essential function when working with CC and conversion presets. Also for creating a preset to replace parts of Track Name.

Yes, of course.

Aside from the hobbled functionality now, the new LE is causing crashes, please can we have our macros back!

Really? I have not seen that, nor read a report of it. How do I reproduce it?

Sometimes it crashes just by calling it up with the setup menu.
Cubase 12.0.52 apple silicon.
Next time it happens I’ll post a crashlog.

1 Like

Another reason to have it back the way it was previously is that iOS Apps like Metagrid now can’t access the PLE presets via menu commands (nor can a Mac app like Keyboard Maestro) - often used to create shortcuts.
Now, I have to use a more cumbersome ‘Generic Midi Device’ method where I first create a midi shortcut macro to access the PLE and its presets, and then link to that in Metagrid.

1 Like

Just to preciser the comment. The list of presets had been available via the Project (PLE) and MIDI (LE) menu, and now they are not.

I agree, it’s a big loss.

1 Like

Yes, and the generic remote is deprecated so may not be a viable option much longer.

I can’t understand why they changed something that many of us have come to depend on, while adding no additional benefits. Seems like it was done without much thought.

The developer of Metagrid or someone at Steinberg needs to hold off on that depreciation until there is a way for Metagrid, as well as some other apps, to somehow use the Midi Remote. There is a Midi Remote beta for Metagrid, but it doesn’t seem to work when I tried it last.

Plus, I have hundreds of Generic Remote commands. I fear once there is a working Midi Remote for Metagrid, I’m going to have to manually spend a lot of time doing the conversions.

This topic is about the PLE and LE. Please stay on topic.

Cubase 12-2024-05-15-162531.ips (290.4 KB)

Attached crash log from attempting to use an LE command.

In my opinion, the logical editor has been totally hobbled, not only has there been a great loss of functionality but stability has gone down the tubes,