Cubase 15.0.20 Major Bug - Logical Editor Presets

[Pablin_Drummer2]

Oh. I have this problem too…what a shame…

[BrunoDSL]

Statement still stands.

[AndrewGComposer]

having the exact same issue can confirm. My set midi to 127 velocity command now sets it to 0.

I have also talked with other composers having the same issues. Hotfix please

[milk_meat]

I’ve noticed if you open the XML file for the preset(s), it will have the correct setting. You can even change the setting in the XML file, however when you open it in Logical Editor it will show the value as “0”.

[masterofnone]

hotfix please! ty steinberg

[RickF]

+1, Yes please Hotfix asap!

[awesomeaudio]

hopefully fix the inability to call a P/LE script into the editor without executing the script to input values as well…

This has been a major workflow set back for P/LE since the new P/LE… track renaming, MIDI values, etc…

[Pablo1980]

yes! this!

You could recall a LE script into the editor with a keycommand, it was a much better workflow.

[awesomeaudio]

It’s honestly as much of a major problem as this new bug.

I don’t understand how it hasn’t been fixed yet, unless something changed in the code/UI access/focus that can’t be undone/modified.

[Johnny_Moneto]

@awesomeaudio

hopefully fix the inability to call a P/LE script into the editor without executing the script to input values as well…

Huh? You can’t load P/LE presets without them getting applied immediately?

[awesomeaudio]

Not via keycommand, no.

The old behaviour prior to new PLE, was you could create a macro

-Open PLE Editor
-PLE Script Preset

The editor would open first, thus negating the ability to execute a P/LE script via a command, thus the PLE Script Preset in the macro would get called into the editor… then the user could enter the appropriate variables, and then manually execute the script.

[rockdude9k]

@awesomeaudio

It’s honestly as much of a major problem as this new bug.

100% agree. I had to immediately roll back. P/LE’s are how I use Cubase, and are integral to my workflow.

[awesomeaudio]

@Johnny_Moneto

Three Important Functions In The Classic Old PLE, Missing From The New PLE - Cubase - Steinberg Forums

@awesomeaudio

3.) Calling a PLE Preset/Script into the PLE Edit Window - without executing the script:
(pretty much everyone who uses PLE, including some of the factory scripts, depend on this behaviour… So I consider it an issue.

https://europe1.discourse-cdn.com/steinberg/original/4X/5/4/4/54491e5a005b03e9de6c3dc35c50f69f9be84423.mp4

• Important for (before the script executes):
  • Entering rename text
  • MIDI variables
  • Edit variables

Currently, it’s not even possible to call a script via command into the PLE Edit Window at all.

[awesomeaudio]

@rockdude9k

100% agree. I had to immediately roll back. P/LE’s are how I use Cubase, and are integral to my workflow.

You’re using an old version of Cubase then?

[rockdude9k]

Yes, I’m the OP and explain how to roll back at the top of this post.

[Jon_Patterson]

Same logical editor issue here with my M2 studio

also, I am unable to hide channels if they are in the left zone of the inspector. Right click, hide selected channel does not work unless it is in the far right zone

[awesomeaudio]

@rockdude9k

Yes, I’m the OP and explain how to roll back at the top of this post.

Gotchya, I thought you were referring to the other old behaviour vs new behavior I was talking about when you said rolling back, which would be more than few versions ago before the new PLE.

[Teo]

I had an Extract function that was very useful in extracting different drum parts to separate channels, now that has stopped working as well.

[Johnny_Moneto]

Can you post a screenshot of it?

[awesomeaudio]

Really hoping this bug can be hotfixed asap,

I have a lot of complicated LEs, so won’t be upgrading.