Please fully document ALL the Key Commands

Cubase
,
#8

+1

Maybe we should make a compendium here on the forum? But how to handle it in a thread, there are hundreds of them!

#9

A wiki-page?

#10

Every journey begins with a single step

#11

Some years ago there was Cubase Wiki (non-Steinberg) but it didn’t really seem active at all. Just did a Google search and it didn’t appear on the first 2 pages - didn’t really expect it to.

#12

Yes that would be great +1. It’s quite slow to even open up the key commands…

#13

Could be, but I literally know nothing about wikis, let alone make one or maintain one. But I am willing to create a thread in which I will be documenting, explaining, maybe offering little examples, or even rating 10 - 20 keycommands per day.

Others could chip in, as I would start from the top, and work my way down the list, posting once per day.

#14

One key command ‘Resolve Note Expression’ is confirmed to not do anything. And doesn’t appear as a an available command on the MIDI list.

#15

“Resolve Note Expression” = “Distribute Notes to MIDI Channels”
https://steinberg.help/cubase_pro/v10.5/en/cubase_nuendo/topics/note_expression/note_expression_notes_to_different_channels_distributing_t.html

#16

Yes please!!! +1

#17

+1. Not surprisingly, this request seems to be resonating pretty strongly.

#18

Not to mention that I have NO idea what the new range key commands are about. Why can’t even NEW features be properly explained?

#19

Thanks for that. Odd that ‘Distribute notes to MIDI channels’ has a key command called ‘Resolve Note Expression’.

#20

Coming to Cubase as a 15+ year user of Cakewalk/SONAR, this was one of the first things I went looking for. All I could find was very spread out reference in the manual that spanned too many pages. I wound up taking them and copy, pasting and tweaking into a Google Spreadsheet that I could easily reference. I found weird stickers online, but it would be fantastic if there were a “Keyboard Shortcut Reference” option in the help menu that produced a PDF, or even a keyboard layout version.

I attached a PDF of my spreadsheet in case it helps anyone. (I had to 7zip it since the forum wouldn’t allow attaching a PDF)

EDIT: Maybe there can be a thread that attempts to capture all the shortcuts, and a separate section for suggested ones to add? I don’t like having to dig into user forums for something so useful, but it’s better than nothing!
EDIT 2: Please note, this is only the shortcuts I found documented in the manual online!! It’s likely not everything - as this thread suggests
Cubase Keyboard Shortcuts - All Shortcuts.7z (82 KB)

#21

Hi,

Did you adapt your Cubase Key Commands to Cakewalk/SONAR version? If yes, maybe you could even share the Key Commands.xml file (if you are willing to do so).

#22

No, I didn’t. I tend to try to adopt the predominant shortcuts of whatever the software is that I’m using… unless it’s just a little strange. A couple changes I made was:

Zoom Tool: Z
Undo Zoom: Shift-Z
Zoom to Project (it’s a macro built-in!): Ctrl-Shift-Z

I can’t remember the others… Cubase’s UI is like a decade old, and they need to improve the experience for customization and key commands… Like making it easier to click a button to “show customizations” or similar. I’m really trying to warm up to Cubase and so far the responsiveness of the the Sonar/Cakewalk/BandLab folks is really putting the Steinberg folks to shame. They just fixed a long-standing bug in Cakewalk/Sonar where the track “interlave” toggle (stereo vs. mono) wasn’t quite allowing stereo effects on a mono track. Cubase, despite it’s massive commercial nature, still requires a whole new track that’s configured as stereo to be able to do that. Kinda lame, IMHO. (I’m really trying folks… :slight_smile: )

#23

























https://www.steinberg.net/forums/viewtopic.php?f=283&t=190409
https://www.steinberg.net/forums/viewtopic.php?f=283&t=192161

#24

+1

#25

+1

#26

+2

#27

Glad to see this is being kept alive. As a former software architect, the absolutely MADDENING thing about this is that there is literally NO reason to not do this. ALL modern development environments allow for developers to document as they go. AND here’s the thing: the developers DO KNOW.

It wouldn’t take -that- long to do this sort of clean up. There are a ton of clean up items that would make power users lives a LOT easier. (Making UI objects consistent, consistent spelling, nomenclature, keywords, etc.) It’s stuff you could assign to an Intern.