Key Commands issue: clicking on the ‘click here’ assignment field brings up the message: “Ctrl+A is already used as key command by ‘Edit->Select All’. Do you want to reassign the existing key command?”
I am unable to change or add any KCs, and this behaviour is now happening in Cubase 13 as well.
In Cubase 12 key command assignment is working as it should.
I have tried trashing the %appdata% settings and reinstalling Cubase 13 but the problem persists.
[Windows 11]
Can you post a screenshot, please?
Cubase 13 example posted above, thank you.
Strange… Maybe try to temporarily remove the Ctrl+A from the “Select All” command by navigating to it and then clicking on the trash button, and see if this helps?
Unfortunately not. I can remove it, but then it is instantly assigned to whichever key command I next select when clicking ‘click here’ in the Key field.
I would like to get Cubase 13’s key command assignment behaviour back to how it was before I installed Cubase 14, even if it means manually re-assigning KCs and re-applying my preferences. However, even after uninstalling (both manually & via Revo), deleting the app data, removing folders, removing registry entries, rebooting, reinstalling, the problem persists… any tips on how to fully purge the system of the corrupted version?
Oh boy. This is weird.
If you put the dialog in the state that it will listen to incoming key presses, and I assume Cubase fetches this from an OS function, it seems there is always “Ctrl A” already in that queue. How that is even possible only on your install is beyond me.
@Martin.Jirsak , can you bring this to the attention of a developer?
Preference folder was already trashed. Behaviour bleeds over from C14 to C13. Re-install (of C13) does not help. OS: Windows 11
Thanks Johnny. Just to follow up - I have discovered that if I hold down a key combination and then click on ‘click here’, those held keys are assigned to the command.
It’s obviously not the expected behaviour and somewhat awkward, but is a temporary workaround, and I thought it might be useful info for any developer looking into this.
Just a quick question: After using your above workaround, and please try with another key command than Ctrl A, will Cubase go back to its faulty behaviour if you don’t use the workaround? And if so, will it use the last used key command to insert automatically or still Ctrl A?
Hi - yes, the faulty behaviour returns after using the workaround and yes, it’s still Ctrl+A.
This means that the keystrokes, to be more accurate their “down” events are properly recognized, so once you click, Cubase scans these “down” keyCodes and performs correctly. This is actually the expected behavior.
Out of curiosity, what happens if you DOUBLE click on a track’s name (this should get the whole name selected) and then single click in a random position in this field?
Hi, many thanks for your help with this. The issue is indeed more widespread than just the Key Commands. I’m sorry I didn’t pick this up sooner.
Double-clicking in the track name field selects the whole name as expected but a single click also selects the whole name, as if Ctrl-A is constantly being held.
The same thing happens in all other Cubase text fields I’ve tried so far - e.g. Channel Pre section filter values; Channel Inserts search field; Transport bar locator fields; Project Setup ownership fields.
However, it doesn’t happen in the Cubase Notepad, or when performing File > Save operations, or with any other programs on the same PC.
Would you mind posting here or by pm, zipped, the UserPreferences.xml and secondary perhaps also the Key Commands.xml files from your %AppData%\Steinberg\Cubase 13_64 ? I could probably compare them with mine and even try them.
Hi. I’ve just sent you the zipped UserPreferences (both my previous one and after a fresh installation) and Key Commands files. Many thanks again for your help with this!
Hi, I’ve placed these files in my own app folder. I first pasted the preferences xml. No problem. Then added the key commands. Again no problem at all. All tried with CB 13.0.50.
Great, thank you, that’s useful info. All very strange but I guess I can eliminate the prefs file as the problem now.
Oliver, I don’t suppose you are using any AHK scripts that you have forgotten about? Or any other utility that manages keyboard macros?
I’m pleased to say I’ve isolated the problem. Thank you to everyone for your time and for pointing me in the right direction…
It’s the latest software update of my Tourbox Elite controller, coincidentally installed at the same time as Cubase 14 (which does genuinely have some Key Command issues as I’ve previously reported in this forum).
I’m not sure why it’s only causing strange behaviour in Cubase and nowhere else, but everything is back to normal in Cubase when the Tourbox Console software is not running.
(Hopefully) final update on this: in case anyone else on here is using a Tourbox controller - Tourbox have confirmed that this is a bug in their Console software 5.7.3 and have told me that v.5.7.4 should be out in less than a week, which will fix the issue.
