Could you provide a wider screen shot? I’m not seeing that MONO switch anywhere on any N12 MIDI channel.
perhaps a typo but midi channels don’t carry audio.so you won’t find a mono stereo toggle..
instrument and audio channels do have that.
1 Like
EXACTLY! This entire issue is about routing within the MIDI engine to get the renderer to see it as a single sourced wave file.
I did come up with ONE WORK-AROUND that’s ALMOST like the desired goal. If you pan ALL the VSTi’s outputs to the left or right, you will get a stereo rendering with a full mono signal printed left or right (depending on where you panned it). Then you can route that track to a mono bus and pan it where you want from the bus. You obviously can’t pan it from the track itself because the right or left side has no information on it. But I was able to get that LEFT PRINTED kick drum to pan to the center.
Not at all ideal. But the closest/simplest (ie: no additional processing required) way to get there. It looks whacked but it works.
Folder/group tracks like in logic:
- folder track contains insert/sends/automation
- auto route to new aux track after creating the folder
- Included tracks auto route to folder aux when drag and drop in/out the folder
- nested option with the same behavior like in logic
Recently Coming from logic to Nuendo I was quite stunned how cumbersome this is in Nuendo.
1 Like
@Keyplayer Still a work around but, have you tried to split the stereo resultant file by selecting the event and using the:
Project>Convert Tracks>Multichannel to mono process? It should be key assignable.
This function should really be in the Audio menu so it gets missed a lot, but alas…
1 Like
Adding of course, that the proposed “folders in the mixer” should be able to sync their open or closed status with the folders in the project window…
Yeah, that’s on my list of work-arounds. But, as mentioned it is:
- After the fact, because you still have to convert the AUDIO signal and…
- You’ll only get half of your data, since you have to choose between the left or right side of the file.
You’re better off merging the left & right sides to mono IN the instrument, then exporting it as a lopsided stereo file with the full BWF on the left or right side.
1 Like
What if you use the dual panner to make a mono signal out of your stereo file?
Fredo
1 Like
Can you use that INSIDE THE VSTi before rendering?
Dunno, but you sure can in the audio track.
Fredo
1 Like
Oh snap, I’VE GOT IT!!!
It takes a LOT of prep work to set it up. But you CAN get a DIRECT MONO MIDI RENDER! 
The most important ingredient for this to work is a MONO OUTPUT! Mono groups won’t work. Once you have that, you can route the VSTi to it. While I don’t think it’s required anymore to route the VSTi to mono itself, it probably wouldn’t hurt to gaurantee the mono rendered export.
Here’s the procedure.
- Go to MIDI PREFERENCES and select STEREO COMBINED PANNER (Dual Panner will also work. Thanks Fredo!)
- Route the output of the VSTi to the Mono OUT bus
- Route the output of the MIDI channel to the Mono VSTi
- Select the MIDI Event, Right click on it to select Render In Place and select the RENDER SETTINGS tab.
- Select COMPLETE SIGNAL PATH.
- Then select Render.
You’ll get a MONO AUDIO BWF that doesn’t go anywhere. So, you’ll have to then route it to any group bus that goes to whatever master out you’re using.
WHY they didn’t put this in the manual, I can’t begin to understand. But, for all of you trying to get this to work, here’s your solution.
1 Like
For this feature alone is the reason I still prefer to produce in Logic Pro over Cubase/Nuendo.
2 Likes
I feel you! This is ridiculous to have to go through all of that just to get this one feature! 
Once you have stems, it really doesn’t matter where you “produce” because from then, it’s just a mix.
1 Like
Isn’t this just a quick way to make a group bus with the added conveniences of automatic routing of tracks in and out of the folder? (sorry if I’m missing something here)
Surprised this is a game changer for some. I rarely use this feature (assuming it’s the same as pro tools), but to each their own!
1 Like
Yeah, me too!
For me, perhaps because I practically raised myself inside Cubase, its very logical:
Groups are for routing signal. Folders are for organizing tracks. Sometimes they converge, sometimes they diverge, and I like that it is this way. I think I’d find it very limiting if my folders automatically forced signal paths.
Besides, key commands folks, key commands. Creating a bus(group) or aux(fx) for selected tracks is one button press away.
3 Likes
Just make it an additional track/folder type
4 Likes
Automate bypass state for hardware insert plugin.
I’ve been using Nuendo since v3 (and Cubase before that) Sharing my top pics I’d like to see, even if some included in N14 update if possible versus N15.
-
2nd pass render (for seamless game audio loop assets)
-
Markers to Video export (similar to audio exporting so multiple new videos can be exported in one click (another need for game audio)
-
Find Video files in pool - Like find selected in pool - (game audio or short form adverts often needs lot of video files in a project so this will help)
-
Right click “to regions” to be able to assign a hotkey to at least cycle through them
-
Automation Capture (we can do this with Snapshots but is heavy demand on large projects and not a clear feature to most)
-
Better save times on bigger project (ideally being able to work in the background without stopping workflow)
-
Mediabay rework so that internal nuendo presets are not coupled with large mediabay libraries. (this can make for all internal presets to load slow)
-
Multi-mono feature built in
-
Project within projects interesting feature in Reaper (similar to how we can have inactivate projects opened but they would be better linked to eachother)
-
More advanced Project logical editor functions (to be able to compete with Reaper Scripting as best as possible)
-
More Automation views - Being able to have more options to quickly view automation, for example something like “Show used automation for specific plugin (only) on selected track”
-
More Backup project options - Specifically to be able to add handles when minimizing files or to leave certain tracks DOP intact. (important because large projects start to slow down sessions so more control to shrink sessions would be very helpful)
-
More options on Initial Automation Point - being able to select what automation points that would be applied (right now it saves too many automation points)
2 Likes