Hi
When using hotkeys (or even nudge buttons) to nudge to the left or the right, it works on the midi parts in the project window but not on the midi events inside a part.
Move left and right works on the midi parts but not the resizing bit.
As show on the screenshot above, the buttons marked with red don’t work on midi events - only the 2 buttons marked with green do. But on the parts all of them work.
What am I doing wrong?
I don’t know what is working out wrongly on your machine but over here things work just fine.
BTW - what you call “midi event” is called “midi part”. The midi event would actually be the note.
Thanks
The image above is what I call a “midi event”. Please correct me, if that is wrong.
Also, I’m not sure what happened. But after closing Cubase and launching it again, the problem solved itself. I can now nudge the length of midi parts.
I am not sure what was wrong in my last session. I’m curious to know what it could have been, though, so I know how to solve it in the future, instead of relaunching Cubase every time, which can be rather slow on my old machine 
I suspect that I accidentally changed something using a hotkey, in my last session. If the problem happens again, I will update this topic by posting a full screenshot here for further troubleshooting.
If you tried to alter the note by clicking on the buttons using the mouse then there is no setting that could switch some of these buttons off. Strange indeed. I am glad to hear that the buttons are working now again.
I already did. The official name is “midi part” (since 1989). No big deal, just makes communication on the forum easier if everyone uses the same expressions.
Strange, indeed.
Thanks for correcting me. You are calling it a “note”. I’m assuming that “note” and “event” is the same thing. At least now I know that the whole container is called a “part” and not “event”.
Might explain why some of my previous topics lacked some replies
Here is a little dive into the MIDI 1.0 protocol.
Whenever midi information is transmitted it happens in form of what we either call a “midi event” or a “midi message”, latter term is mainly used by programmers. A note consists actually of two midi events, start and stop aka “NoteOn” and “NoteOff”, but the key editor depicts those two items as one on the screen. That is much nicer for us humans to grasp.
In Cubase events are usually the ‘smaller’ items and parts act as container, that house events. Midi events must be packed into a midi part container. With audio events that is optional, they can be packed into audio parts but don’t need to.
Some events cannot be put into a container at all, e.g. VST automation events. I mention it because I am a supporter of the feature request to have Cubase introduce VST automation parts. I think that would make handling of automation data easier in some cases.
Sorry for getting a bit detailed and off-road.
I’m glad you explained this.
This sounds like a good idea.
I hope we will get an implementation of a feature like this. I don’t have a lot of experience with automation in Cubase, but what you are suggesting might be a good way of making automation appear less “formless”. It might be easier to deal with visually (especially for less experienced users) it if there were chunks of automation that served a role of reusable presets that could be saved, reused and could give a proper visual feedback on what’s going on.
And this could enable us to make shared copies of automation parts, just like with midi parts, so that when we edit one chunk of automation in a project, any shared copy of that part also takes effect.
That is, if I understand your idea correctly.
An Event is something that outputs data, so an audio event on the timeline, or a MIDI event (note, cc, etc) that is contained within a MIDI Part which is the box you see on the timeline. There are also audio parts, which contain multiple audio events.
