I am using Cubase Pro 10.5.12 Build 123 running on Windows 10 and I created a macro that works perfectly until I restart Cubase. After every restart the highlighted function on the left side of the picture below disappears from the macro.
I can recreate this simply by adding a new macro with just a single “Process Plug-in” Function. The macro will still be shown in Cubase, yet the process is missing after restarting Cubase.
It doesn’t matter what VST plugin I am using, so far I tried several VST 2.4 and VST 3.0.2 plugins all with the same result.
So far I created a new profile, I erased my %AppData%/Steinberg/Cubase10.5_64 folder, I monitored the “Key Commands.xml” file, unfortunately with no success.
To my surprise after restarting Cubase, the “Process Plug-in” function remains inside the “Key Commands.xml” file under my macro function, as a matter of fact, the file does not change at all after. The unique identifier inside the string “Name” does not change unless I choose a different VST plug-in. So my suspicion that this ID could change after every restart was false. Now I’m not sure what to look for next.
I hope, it’s not a bug and somebody can help or guide me in the right direction.
Hi,
are you not able to see the screenshots I provided? They are right from the macro editor inside cubase.
The Macro does a reverse effect. Reverse, then apply VST Effect, then reverse the newly bounced version.
You can recreate this issue yourself by simply creating a new macro and adding just one function : Process Plug-In (use any VST Plugin, it doesn’t matter which one)
Then restart cubase and you’ll see that it disappears. I just don’t understand why.
I will consider writing a bug report, though I’d never done one.
I am new to forums and I am sorry for not being aware about my post being too densely packet. I was struggling for so long with this issue that I might’ve been a bit over-eager in explaining all my efforts. I really didn’t want this to be a bug, because - so far - every issue I’d had with Cubase in the past was due to the fact that I was simply using it wrong. My long explanation probably also was trying too hard because I didn’t want to be looked upon as a fool who just “didn’t click that box right there”… so to speak.
The purpose is to confirm that it is a bug. If several users can reproduce this behaviour, we would be able to create a bug report so that this could potentially be fixed in a future update of Cubase, to make it even better than already is.
Steve was kind enough to confirm that the macro breaks after a restart of cubase.
Hope, this helps.
My question is, does the bug appear in a real scenario (which makes sense)? Doe sit appear if there are other steps in the Macro (what is Macro made for)? Does it appear, if you add 2 Direct Offline Processes to the Macro (then it’s a real scenario)?
I’m not questioning, this is a bug. I’m just asking, how serious it is.
My question is, does the bug appear in a real scenario (which makes sense)? Doe sit appear if there are other steps in the Macro (what is Macro made for)?
Unless I’m misinterpreting, the original post answers these questions, including screenshots of a multi-step macro.
If this is the only one step in the Macro, there is a workaround for you. You can assign Key Command and trigger the only one process this way (so you don’t need the Macro then). If it crashes even in all other cases (independent how many commands are around), then I can’t see any workaround, I’m sorry.
And of course the relevance of the bug is different in every of the cases.
I’m beginning to feel sorry for starting such a mess in here.
@Martin: Thank you very much for trying your best to help me out with my problem. But unfortunately we are talking at cross-purposes - we seem to have different levels of what we are trying to communicate.
My intention in the OP (original post) was to be as specific as humanly possible. And the problem with complexity is, one could easily misunderstand what was initially simply well meant.
Once again thank you everybody - especially -steve- - for helping me with my problem but also learning so much about how to use forums and life.
Same issue here, the actual reverb processing is gone when I restart Cubase 12. Was this bug ever fixed?
UPDATE: The macro got corrupted when upgrading from Cubase 10 to Cubase 12. However when I added back the Process Plugin step that was lost, it did not get removed automatically when I added it in Cubase.
However when I restart Cubase it is gone from the GUI but remain in the KeyCommands.xml file. When closing Cubase the xml file is overwritten and the processing step is gone!
I first verified the bug and saw that the processing step was removed from the %AppData%/Steinberg/Cubase 12_64/Key Commands.xml file, while it was correct in the Key Commands - Backup.xml file.
Then I added the processing step back in the Cubase Macro and saw that it was added to the xml file. I shut down Cubase 12 and restarted it, and it was still there in the file, but only until restarting Cubase.
So the bug seems to still be there in Cubase 12!
UPDATE and Work Around!
I suspect this is a Windows issue. There is a workaround that I have seen that some are using, which is replacing all “Process Plug-In” steps with a direct offline processing bank and favorite. For example a “Process Plug-in - Roomworx” would then be replaced with at least two steps “Direct Offline Processing - Bank X” and a “Direct Offline Processing - Favourite X”.
More information can be found here: Help solve the problem with macros - #3 by Holm