I have just checked a couple of the factory presets provided by Cubase 15. They show this behaviour. Does your factory presets work as expected?
Hi,
Could you name some specific, please?
In this case, you might be right. If the presets were created in the corrupted version, they would need to be updated. Therefore I would like to try them.
Hallo,
habe auch ähnliches Problem, mit Velocity werten , im Editor werden alle Werte die ich sonst per Tastaurbefehl auf 100 gesetzt habe , werden auf null gesetzt .
Hi,
Since this is an English-language forum, we would appreciate it if you could please add an English translation to your posts to benefit users and search engine results.
DeepL or Google Translate do a great job and only takes a few seconds
Thank you!
DeepL translated post:
I’m having a similar problem with Velocity values; in the editor, all the values that I would normally set to 100 using a keyboard shortcut are being set to zero.
What kind of editor do you mean? How exactly do you set it (what kind of Key Command do you use)?
Did you see pablo1980s post?
Try Factory preset velocity +10% or Factory preset velocity -10%
Hi Martin, it is happening with the all the user and factory LE presets, I have attached images of two factory presets, and they reset to zero if we modify them and save them again.
it is clearly some kind of bug
Hi,
Could you name one, please? I don’t want to search across 100s presets, which one is using exactly this feature.
Thank you!
I have attached images with two factory presets earlier in the thread…
please look in: Factory presets\Note Velocity
All those presets have their values reset to zero.
All user presets that modify CC or velocity also reset to zero
.
So, couple of tests, hope you can reproduce them:
Deleted all entries, Created new one and Saved
Made one Adding 10 velocity. Saved. Closing and reopening Cubase doesn´t erase the value.
.
Modifying an old User one
Just correct the velocity value, save it, the moment you press save, the value goes back to zero.
.
So it seems that the problem may be with the ones created before 15.0.20, even factory ones?
When you are modifying an old user one, is it using “Velocity” or “Value 2”?
ok, you are on to something.
It is using value 2, so if I change that to velocity, I can save them ok and the value doesnt reset.
this doesn´t happen in previous versions, and the ones that deal with CC reset the values when saving, using value 2 or main value.
Value 2 isn´t available to create new ones when CC is modified.
some things have change in the logical editor and they don´t work as before
Broken for me too!!! ALL LE with volume go to zero………!!!
is a bit weird though that that has changed all of the sudden. Wonder if it’s intentionally?
Hi all,
We’re aware of the issue and are currently investigating how to resolve it. Please bear with us while we evaluate the situation.
Same problem here. After update LE values from Metagid (CC7-10, CC1+5…) are gone to 0. Even if you try to change it manually and save as a new preset fails.
Some preferences are gone too.
Factory presets too so maybe its a Cubase LE presets bug
The Logical Editor used to be hard-coded to work on MIDI 1.0 messages. With Cubase getting ready to also handle MIDI 2.0 the LE had to be changed. This is why the old “Value1” and “Value2” have been replaced by items that actually let you know what they are about. Unfortunately there seem to be still some quirks in this as the editor is not fully transformed yet. The UI could be improved and bugs are appearing. In a previous version there was some other bug in LE that got fixed in the meantime. I don’t quite recall exactly what it was, I think pitches were set to G#8 or something.
I hope they’ll find the cause soon and will patch it out.
i use Random Velocity 60-100 as Key Command , with external Controller
Listen Editor
Appreciated
How naive am I in thinking it’s surprising this bug wasn’t found in beta, or other pre-release, testing?
Not very. I’m surprised as well…
I am also having the issue. But I will point out that the Midi LE command that I made for myself seems to be unaffected. All the Factory are affected though.