Thank you so much!
It sounds like the script is saying the xml file is corrupt, somehow. I suggest you open Cubase, and open the Key Commands dialog, and save your current key commands as a preset.
Then, load that new preset, then quit Cubase, and run the script again.
In saving the preset Cubase will write the file correctly. Let us know if that works.
Thanks, that worked! and thanks for the utility!
Great! Thanks go to others, I just moved the post and stickied it!
Thanks , very useful !
What a fantastic utility thank you so much
Does’t work here.
Did you follow the installation instructions in the readme.txt file? It looks like you didn’t put the script in the ‘User Settings Data Folder’ but ran it from a Temp folder.
This is brilliant, thank you so much!
ran the script as per instructions in Win10 on C9.5 . it asks which app to use to open the file and i get the result (see images)
Is there a way to make this read a user keycommand preset instead of the default?
Does this work on Mac?
I don’t understand why after all of these years something like this ins’t built into Cubase. Export key commands to a text file or .CSV file.
So simple it would be but no
To be fair, you can simply copy the contents of the Presets/Key Commands/ from one user prefs folder to another and the presets will appear in the Key Commands drop down menu.
For anyone having difficulties finding the folder in Windows 10, its:
(That’s the folder were the Key Commands.xml file resides). You need to copy the “Cubase_ShowAllShortcutKeys.vbs” into that folder and then double click it. This will create two HTML files with a list of key commands, which you can then read or print for reference.
Question: If I want to have my own custom preset key command file exported to an HTML file, would I copy the contents of that file into the “Key Commands.xml” file and then execute the vbs file again? Is that the idea? Actually, I think a better way would be to copy my own preset file into any folder, rename it to “Key Commands.xml” and then execute the script… I think that should also work!
Thanks for sharing.