Key Commands Overview as HTML Page

[Magnus_N]

Select all the code and paste it into an txt editor and save as html file.

Thanks Peakae. I tried that with both Textedit and Smultron, and tried to open in Safari, iCab, and Firefox to open but still just shows page source.

Same for me in Win 10/Firefox...

/Magnus

[ulesto]

Probably MacOS is hiding the filename suffix, so it appears to be .html, but is actually .html.txt

Thanks Steve. That wasn't it, but it gave me a clue. Text Edit doesn't save in plain text anymore as far as I can see (only rtf), so I was just re-saving it as html thinking WYSIWYG. Nope. Had to copy the text from Text Edit into Smultron to remove all the extra stuff and save it there. That worked.

Thanks to fese. It looks great!

Btw, if anyone wants the stripped down txt file, here it is. Maybe it will help you Magnus.

Key Commands.txt.html.zip

(1.89 KiB) Downloaded 153 times

[ChrisDuncan]

Very handy. Thanks, Fese!

[take3]

Thanks for this! For any Mac users, found the default key commands file here:

Right-click the Cubase app file (in the Applications folder) -> Show Package Contents
Navigate to: Contents -> presets -> Key Commands -> default.xml

Copy the default.xml file to another location. Then you can point the html utility to the location you copied it to, to open it.

I made a custom key commands file and can't find it. Anyone know where it is stored? It doesn't show up in the above folder.

[mbira]

This is very cool! Thanks for doing this.

[ulesto]

I made a custom key commands file and can't find it. Anyone know where it is stored? It doesn't show up in the above folder.

It's in the User/Library/Preferences/Cubase 9.5 folder - in Presets.

[mac88104]

Thank you very much !

[Ntac]

Thank you for that!

[galoz]

Great!!! Thanks

[msy]

Hi,
just for fun I've written a small single-page HTML app which can load Cubase's "Key Commands.xml" and display it as nice table which you can then print or export or whatever.
Just double-click on the html page and select the "Key Commands.xml" file in the file brower (usually resides in "%APPDATA%\Steinberg\Cubase [Version]" on Windows, no idea where it is on a Mac).
Tested with Firefox and Chrome. No idea whether it is useful for anyone (or even me). Sadly it is not possible to use localized descriptions, just the english ones...

https://drive.google.com/open?id=1Jl7ag ... MtOjUfVaDJ

Cool! Thanks!

[GregMalick]

This appears to only show Key Commands that have a shortcut assigned.
There are a lot more Key Commands that are unassigned.



Is there a way to display all the Key Commands in a sortable table with their category and shortcut (blank when unassigned)?
That way we could sort by Category or by Shortcut and easily determine what keys are unassigned rather than using the "try assigning until you succeed" method.

[-steve-]

Please read the beginning of this thread.

[GregMalick]

Aloha Steve,

I've read the entire thread a couple times but when I use the page to display my "Key Commands.xml" file, I only get a page showing Commands that have shortcut keys assigned.

What did I miss in this thread?

thanks.

[raino]

Aloha Steve,

I've read the entire thread a couple times but when I use the page to display my "Key Commands.xml" file, I only get a page showing Commands that have shortcut keys assigned.

What did I miss in this thread?

thanks.

That that is all it does?

The xml file you submit only has info about the assigned keys, it doesn't know anything about unassigned keys. The OP is reformatting the xml into something more human readable.

[Larioso]

This appears to only show Key Commands that have a shortcut assigned.
There are a lot more Key Commands that are unassigned.

Is there a way to display all the Key Commands in a sortable table with their category and shortcut (blank when unassigned)?
That way we could sort by Category or by Shortcut and easily determine what keys are unassigned rather than using the "try assigning until you succeed" method.

I was thinking about that too.

If allowing to save as CVT, as comma separated file we could load in Excel or similar spread sheet and enjoy sorting on any column.
Even Google has a service for spread sheet I used a short while, for those not having a spread sheet.

Thanks to fese for his effort with this, really looked for that fixing a list of the commands.

[-steve-]

Check this out: viewtopic.php?p=204659#p204659

[nicky_p]

Thank you!

[garymusic]

Thanks... Really Really useful.

[theRoyal1]

Much appreciated, Thank u!

[fese]

Hi all,
I added the option to converting the KeyCommands.xml to CSV, including unassigned commands. You'll have to copy and paste it from the browser windows, though, "save as..." won't work.
See the first post for the download address.

[-steve-]

I just updated to Cubase 10 a couple weeks ago.

Steinberg: I WOULD PAY REAL MONEY TO UPGRADE CUBASE AGAIN, IF THIS WAS THE ONLY FEATURE YOU ADDED TO 10.5!

Or as people say nowadays... +1.

You do understand that this is not a feature request, but a completed effort by a forum member...

[ChrisTheStranger]

Sorry, I was in another topic (in another tab), responding to something else. Turns out I was posting here!

[galvinstephen]

Good idea. Thank you

[FINgers101]

These are great utilities. thanks

What would be really great as well is if you could go the other way.

Generic remotes are a pain to set up if you have a lot of repetitive commands, and you need to enter each one. If you could work in say excel and then transform into an xml file to import that would be a real timesaver.

You probably already can but my skills are not that great with respect to xml.

[fese]

These are great utilities. thanks

What would be really great as well is if you could go the other way.

Generic remotes are a pain to set up if you have a lot of repetitive commands, and you need to enter each one. If you could work in say excel and then transform into an xml file to import that would be a real timesaver.

You probably already can but my skills are not that great with respect to xml.

It is certainly doable, but you'd probably have to do a lot of error checking or the import won't work.
Personally I have no need for that, but what you could probably do is start in Cubase, then export the config to XML and load it into some editor with syntax highlighing (e.g. Notepadd++). with a little bit of copy+paste and search+replace you might be actually faster than clicking. The XML of that file format is relatively self-explanatory if you have a look at the UI once in a while. Maybe send the resulting file to an online XML validator to be sure you didn't insert any syntax errors...