This seems to be an age old issue, I found this (locked) post here from Cubase 8 which also describes it. I stumbled upon it recently and was baffled until I found the reason. Time to bring it up again as it has not been fixed since then…
Scenario: Instrument track with a multi out VSTi, e.g. GrooveAgent, with some of the plugin outputs activated and some not:
Now when you Render in Place a part from that track, the first three outputs get rendered, but Out 5 (or anything after the first disabled output) not:
(Oh, and by the way, if anyone can tell my why RIP sometimes transfers the original color to the created tracks and sometimes just the default track color, I’d be delighted…)
The only workaround seems to be to activate all outputs in between and have them rendered as well (resulting in useless empty audio of course).
I highly suspect that this is still an issue in C15, but I cannot test it there as my demo license expired.
If it was reported in C8 shouldn’t it have been fixed by now? Seems like a very simple coding fix … making a list of outputs to render and skipping deactivated outputs. This is the kind of coding project they give 3rd graders.
These are the kind of quality of life issues that cause people to move to other environments. Meanwhile we have 30 new reverbs and compressors that will be forgotten and people will be trying to figure out how to jBridge them 20 years from now because they foolishly used them in a project.
Even weirder, if you activate outputs 1-3 and 5-7 (so only one output in the list deactivated), what gets rendered is 1-3 and 5-6! This is seriously bonkers…
Oh, and by the way, if anyone can tell my why RIP sometimes transfers the original color to the created tracks and sometimes just the default track color, I’d be delighted…
Anyone else is experiencing this? It seems completely random, once every dozen render in place calls or so the newly created track has the default color, not the source track’s color. Sometimes the next render works correctly again, sometimes it also produces the wrong color. I never experienced three in a row, though…
You are right. I submitted the original issue in 2015 and it was acknowledged as a bug and locked by someone from Steinberg. Now here we are… 10 years later???
I reported more issues but never was satisfied with Steinberg support. Therefore I stopped reporting issues and decided to jump in to the forum from time to time to help others when I can.
However some issues were solved over time (like graphics and disappearing issues with the project cursor). But… not this issue. To be honest… I try to work around it. Overall the program has improved so I keep that in mind.
