MIDI notes can be selected normally with the mouse in the Lower Zone Key Editor, but keyboard commands such as Delete, Copy/Paste and Quantize are routed to the Project Zone instead. Delete therefore deletes the entire MIDI Part and Copy copies the Part.
The same commands work correctly when the Key Editor is opened in a separate window.
Reproducible after:
complete Cubase reinstall
deleting/renaming the complete Cubase preferences folder
When I’ve seen this issue it relates to doing anything in the upper zone that takes the focus back there, such as clicking on the timeline, selecting a clip (to change what is in the lower zone), etc. I find it very easy to accidentally do something of that sort when using the lower zone key editor. It’s much tougher to do it accidentally with the full screen key editor (which I pretty much always use for any serious editing, using the lower zone mainly when I want to visually align things with respect to other tracks in the upper zone.
This is why I asked for a repro. I don’t want to correct the OP, and I’m allowing for the possibility that there’s something wrong in Cubase, but yes, it would appear that the lower zone is not in focus.
Maybe a different accent color would help to see which zone is has focus.
I have added the information on my operating system, Cubase version as well as video evidence of the occurring problem. Unless I am gravely mistaken, the lower zone is taken into focus as I hit the delete key, but deletes in the upper zone nonetheless. Help is appreciated.
I also tried something similar on my system, and it works correctly. The video does seem to show the focus has shifted to the lower zone (outline around that zone) when the issue occurs, even still being there after the deletion.
I have recorded an additional video replicating the problem even after deactivating the program preferences. I have also deleted them multiple times while troubleshooting last night, all to no avail. Repairing Cubase by downloading again has also not fixed it. Whether in a previously made or a freshly made project, the problem persists. I can’t really work like this.
It’s not like people don’t believe you, there’s no need to provide ‘proof’.
I don’t know the cause of your issue, I am trying to help you troubleshoot by asking questions and I await each answer. I and @rickpaul both do not see this problem on each of our Cubase installs, which pretty much shows this to be a local issue on your system.
I took the time to watch your video and it ends abruptly before you demonstrated what happens in a new empty project, which would have been my next question.
If you want to work here to troubleshoot, that’s fine, but maybe it would be better for you to contact support.
It pretty much shows the same thing happening. I also can’t open up selected areas in the editor by hitting the arrow icon in the top right of the lower zone. I guess I will contact support as well. Thank you.
I agree contacting support is probably the best option here. The only other thing that came to mind was if there is a Remote Control surface involved where something set up there might somehow invoke a temporary change of zones. I can’t imagine what that would be, though, and I’m guessing the use of safe mode and deactivating preferences might have disabled anything of that sort anyway.
The new information about not being able to open up to the full-screen (or at least popup) editor also seems very odd – almost like Cubase is thinking it isn’t applicable because that key editor is not in use or some such thing. In that context, the only other thing (almost certainly a longshot) that comes to mind is what happens if you close the lower zone, possibly close Cubase altogether, then open it again with the project and unselect and reselect the area you are trying to edit and bring up the lower zone again.
I can open sections with Ctrl+E to open them in the editor and there use copy, paste, delete commands as normal. If I have both the project and lower zone on-screen, it doesn’t work. I use an M-Audio Hammer 88 Pro, and I have it currently unplugged. I could try deleting the entire Cubase 15_64 folder again, taking the MIDI controller out and then restarting the PC and trying to boot up Cubase.
Here’s another piece of evidence: When I try to quantise the notes, it says that the keyboard command (Q) that is linked to quantising is not available at the moment. This has to be some sort of keyboard command routing issue.
Yeah, I’ve restarted a couple times since then. Real headscratcher for me.
The only thing that was different between it working and not working was that I had installed the Softube Saturation Knob plugin with the Softube Hub. I have since deinstalled them both and deleted all Softube files from the PC, but I wonder if somehow the plugin shot something deep inside the Cubase UI. I have little clue otherwise.
I use a M-Audio Hammer 88 Pro that I’ve disconnected today. I have mostly two mice, a KVR switch, a keyboard, the Steinberg connected.
I did run Cubase in safemode where the error occurred as well. It sadly happens both in a plain MIDI track with nothing connected. It happens across all tracks.
It seems that context sensitive keyboard commands that you try to use in the lower zone are only executable in the project zone.
I’ve made a discovery. If I pick out notes in the lower zone but then switch my focus to the Editor/Inspector, then I can use commands like delete, copy, paste and quantise as if the lower zone were in focus. That’s crazy.
