I’m having an issue with a strange “render in place” phenomenon:
In my example, I have a 5.1 output and a stereo downmix output. All tracks end up in a 5.1 master group (which is routed to the 5.1 output), and from that group, this signal is sent to a stereo group for a stereo downmix (in my case via a send, but the problem occurs exactly the same way with direct routing). The stereo downmix group is routed to my stereo output.
If I want to run Render in Place on an audio track (in this example, a stereo track, but this applies to all track configurations smaller than the largest output, i.e., smaller than 5.1 in this case) and select “export Channel Settings,” I would expect to get a stereo audio file on a stereo audio track (with the same routing and panning settings as the original track). However, Nuendo renders a 5.1 audio file and creates a 5.1 track that is routed directly to my stereo output. That doesn’t make sense to me, does it?
Furthermore, the “Mix to a single audio file” option appears in the Render in Place window, which, to my knowledge, should only appear if I have selected multiple events on different tracks. It also makes no difference whether I check that box or not.
If I remove the downmix routing, Nuendo renders a stereo audio file, creates a stereo audio track and routes it to my 5.1 group, including panning, just as I would expect.
The same problem also occurs with other routing configurations, e.g., in a 7.1.4 session with downmix groups.
Can anyone confirm this issue?
1 Like
anybody also having this issue or any ideas? 
What version are you using?
RIP has been a PITA since it’s arrival, especially for rendering MIDI tracks. For the most part your rendering will always default to your output. Stereo will render stereo if the output is stereo. 5.1 will render out a 6 line file and so on. What you cannot get, no matter what kind of configuration you use, is get a MONO output. Why they won’t let you select the end result in the settings is a mystery. We’ve been asking for this option for years now.
So, if you can get a stereo render by removing downmixing from the path, count it as a blessing, as you’ve found the work-around you need. Just make a note of the process and forget trying to have any of this make sense! That ship has long since sailed!
If you ever need a mono render, like I do, for Kick, Snare drums or solo wind insruments, you have two options. 1) Render in stereo and route it to a mono bus. Fast but NOT OPTIMAL because you keep seeing a stereo track. 2) Render in stereo and export that rendering as a mono track. Also NOT OPTIMAL, as that is a massive waste of time and it generates dozens of unnecessary tracks.
My work around is to just play the MIDI file and record it back into the project in mono. This will require a 14 sample (YMMV) time adjusment. But it’s the fastest and most accurate way that I know of to get the results you intended/expected to get.
We all hoped, apparently in vain, for this to finally be addressed in N15. As there’s no evidence that this has been corrected, not to mention that now N15 crashes instantly when even attempting to render any file that originated in an earlier iteration, I advise you to take the work-around as a “Win” and move on.
1 Like
Thanks for your answer! I’m using N15 and N14, the issue is the same in both versions (no suprise). You are right, RIP is a pain sometimes… Thanks for your workaround tips!
I am struggling with another annoying bug since Cubase 13 where Cubase/Nuendo isn’t transferring automation data from multichannel instrument tracks to the rendered tracks ( Cubase 13 Render in Place with VSTi -> automation bug ). I hope it will get better one day 
1 Like
