It’s extremely weird. I’ve now gone through all .xml-files in the ~/Library/Preferences/Nuendo 12. Manually deleting any trace of the macros. I’ve used Visual Studio Code to go through all the files. Still, these macros (7 of them) are re-created upon restarting Nuendo.
Even trashing the entire preferences folder will delete all settings, plugin settings, etc. BUT, the macros are still there.
Can you please list the contents of the Nuendo 12_64-folder? I’m on macOS, I need to compare if it’s the same folder.
I removed the entire (what I believe to be) equivalent ~/Library/Preferences/Nuendo 12-folder (that contains the Presets-folder), and even after that, all shortcuts and macros were gone, EXCEPT those 7 macros.
It started with me renaming the macros since I needed to re-categorize them. After renaming I restarted the application, in which I now had the renamed version, and also a copy with the old name that refuses to be deleted.
There is nothing special about them, no common link that I can find. And I renamed 100 other macros that didn’t behave this way.
As I say, I’ve gone through all settings files in the entire settings directory with the application closed. Manually removing all traces of the macros from all .xml-files (only present in Key Commands.xml). Upon restart, Nuendo re-creates the macros and injects them into the Key Command-file again.
Sorry, I didn’t realise you were using a Mac. (Although you mentioned it above.) According to this article, you have chosen the correct programme path.
There are “Key commands (current)” Username/Library/Preferences/Nuendo 12/Key Commands.xml
and “Key command presets” Username/Library/Preferences/Nuendo 12/Presets/KeyCommands/<preset name>.xml
Did you remember to quit Nuendo before editing the XML files? It sounds like Nuendo still has access to the old files, since they cannot be deleted.
Okay, I guess you did:
I had actually created my own “Duplicate Selected Track without Data” without knowing it existed since I don’t use any of the factory macros at all, so I just counted on the fact that I created all of those macros. I was not even aware there were any factory macros. So my bad for not checking that