C16: No way to convert existing Instrument tracks structure to new Instrument stack

Interested in the new ‘Instrument Stack’ feature, I tried to convert the following structure set up in Cubase 15 to share same midi data with several Instrument tracks, and extensively used in my projects :

  • A MIDI track containing the midi data with an instrument on MIDI channel ‘x’ and 1 to 4 sends using the same MIDI channel X to instrument tracks,
  • 1 to 4 instrument tracks listening on MIDI channel ‘X’
  • I group all this in a same folder

I selected the tracks and chose the menu ‘Move selected tracks to → New Instrument Stack’. The tracks are correctly moved to a new ‘Instrument Stack’ track and converted.

However, the original MIDI track, let’s call it the pilot track, still exists and continues to send its MIDI to the tracks in the stack.

If I want to delete this track and incorporate everything into the stack, and move the MIDI from the pilot track to the ‘Instrument Stack’ track, the instruments no longer receive any MIDI.
The MIDI port that was specified in the original sends seems to be lost during this conversion, and I can’t find where to enter it for the ‘Instrument Stack’ track and its stacked instruments.
It seems complicated, even impossible, to convert my structure to this new functionality.
Disapointed because it seems to be exactly the purpose of this new feature.
There should be a way to select the midi channel to use by the stack to power its stacked instruments.

I’m probably not following your original setup correctly, or maybe something else you’re expecting in converting to instrument stacks. However, trying a quick experiment based on what I thought you meant, after moving 4 instrument tracks set to listen on MIDI channel 2 (arbitrary, other than my MIDI controller puts out data on channel 1, so I wanted something other than that). I set up 4 instrument tracks listening on channel 1), then a MIDI track with 4 sends to channel 2, one to each of the instruments. Here is a picture of that track with inspector values showing:

Next I selected the four instrument tracks and moved them to a new instrument stack:

Finally, I moved the MIDI part from the original MIDI track to the Instrument Stack track:

Despite all the instruments’ being set to MIDI channel 2:

and the MIDI data showing channel 1 in the list editor:

the parts still played back.

Thank you for taking the time to try.
I see your process and can’t find what is different from mine.
Here are my corresponding steps :



then I convert



With the initial midi and its send, it works

But after transfert of the midi data to stack track, no more sound

I tried deleting the original midi track, and checking there was no automation or expression shuting down the output
Only thing I see is that my instruments are, as on this picture, all filtering on the channel number ‘X’

??

Only difference I can see is that you also picked that MIDI track too, @rickpaul showed and said four instrument tracks in the example

Yes because it contains an instrument, my structure was built this way to limit the number of tracks.
May be the other difference is in its individual instruments, may be they are aligned to all inputs ?

I just did a little further testing, adding a multi-timbral setup in HALion Sonic, similar to what you showed in your screenshots, and what @Jari_Junttila said above indeed appears to be the case.

I tried explicitly setting the HALion Sonic main channel, and each instrument channel, to 2 (like the sends for the other instruments), and, after moving to the stack arrangement, there was no sound from the HALion Sonic, whereas there was from the other instruments.

Then I changed the main channel from 2 to 1 within HALion sonic, leaving the individual instruments wherever they’d adjust to, and exactly one (the selected one) got changed to channel 1 and sounded. Then I explicitly changed the other two to channel 1, and now they also sounded.

In my general use of instrument tracks, I am always just leaving any MIDI channel information at defaults, both at the Cubase track level and within the instruments. My controller is set to send on channel 1, so the MIDI data goes to channel 1.

I notice the instrument stacks do not allow setting explicit MIDI channels. However, the individual instruments within the stack are working, they must be ignoring the input MIDI channel setting on the individual tracks – otherwise, I wouldn’t have heard anything in my earlier example since the individual instrument tracks were still set to channel 2. However, if the instruments themselves are “hard coded” (“hard set”?) to specific channels, they will apparently (i.e. based on these empirical results) only receive if that hard coding is for channel 1.

This also likely means that multitimbral operation from the instrument stack MIDI level would not be supported, though you can also have MIDI on individual tracks, that would go to the specific instrument along with any data coming from the MIDI stack level. So, there could be the potential to send each instrument some custom data, be it notes, controllers, or whatever. That’s probably most useful with different instruments in different slots as two different synths (or other virtual instruments) might understand the same notes but not necessarily the same controllers and keyswitches.

Hi @csurieux

Does the same thing happen if tracks are not solo’d when creating the Instrument Stack?

I doesn’t look like that in the picture, just to check.

I’m quick browsing here, so forgive me if I’m barking at the wrong tree. I don’t have 16 yet, but I do often like to move MIDI track parts to an instrument track hosting a multi-channel/timber plugin.

Here’s how I achieve it. Perhaps something similar also applies to these new plugin stacks.

Before dragging MIDI tracks to Instrument tracks, always set the MIDI track’s output channel what it should be first, then ‘freeze MIDI modifiers’. This hard sets the track data to the proper channel.

Cubase records/imports things exactly as they were entered. Anything done in the track inspector is a ‘real time’ conversion. Freezing MIDI Modifiers converts the hard data for any events that are selected.

Next, set the target Instrument track MIDI output to ANY.

Sometimes we need to work with a more complicated MIDI track that needs events on multiple channels in the same track for some reason, and doing a freeze could destroy such intent. If this is the case, then you can use MIDI Logic Editors, or the key editor to isolate the events and set the MIDI channel to what it needs to be.

Another common tactic would be to dissolve the track into multiple tracks first (so each set of events for each channel get a track of their own), set the desired channels in the track inspector, Freeze the tracks, then merge them back together to some destination with the output set to ANY. Or you could skip merging back together since you can also stack many parts onto an instrument track, and they become ‘lanes’.

@Michael_Ill and @Brian_Roland, thank you, but these potential causes are not the root of the problem.

The reason is clear: MIDI channel management between the new instrument stack and the included instruments is missing.

In fact, as @rickpaul demonstrated, and I took the time to verify this, everything works correctly when using channel 1 everywhere.

However, if you need to change an instrument’s channel, as is sometimes necessary, you cannot specify it in the instrument slots as offered in this stack.

In my opinion, adding the “Monitor” and “Record” buttons, which are always grayed out in the instrument stack inspector, means this functionality is delivered in an unfinished state.

And with many other imperfect new features and regressions, this version 16.0.5 was released too early, without sufficient testing, and we are paying the price twice over (in terms of update cost and lost time).

OK, I don’t have 16 yet, so I cannot test it. I’m not arguing either. I quickly browsed the thread and felt it worth pointing out.

I do know that even without the ‘stacks’, if I want to move a MIDI part to a multi-timbral instrument track, I need to set the output on the instrument track to ANY, and make sure the parts are hard coded to the proper channels first.

See, if I record using my MIDI controller set to channel 1, that’s how it goes onto the MIDI track. I can redirect to a different channel through the modifiers in the track inspector, the transformation happens in real time, but in the part itself, it’s still channel 1 data.

So, I must freeze the track/part to the channel I want it to be first (so every event living in the part is hard coded to the proper channel). Then I can move it to the instrument track…otherwise it’s going to play over channel 1 (or whatever the output of the instrument track is set for) every time.

I.E.

Say I use my midi controller and record 16 different channels of MIDI diverted to an instance of HALion Sonic in GM Mode. I’ve had my MIDI controller set to broadcast over channel 1 for every track…but simply diverted it to the 16 different Sonic instrument slots by changing the track’s channel output settings.

First thing I must do is set the Channel output in the Sonic Instrument track to ‘ANY’.

Next, I need to freeze the modifiers of each of those MIDI tracks.

At that point, I can drag them one by one onto the Sonic Instrument Track, or I could merge the tracks first, and then drag the new merged part onto the instrument track.

If I didn’t take these steps…

The parts I drag onto the instrument track will all have channel 1 data. So, the instrument is either going to play over channel 1, or whatever channel the output of the Sonic track is set for.

Remembering to set the output on the instrument track to ANY is imperative, otherwise it’s going to one slot/channel in Sonic, and nothing else. Once this is set to ANY, it’s up to the plugins at the end points to manage and play, or ignore given channels.

Sorry if taking these steps still leads to broken results or justified calls for improvements/fixes to Cubase. It’s just a heads up in case it’s useful…

Thanks very good point but a little out of topic and I won’t answer here to avoid changing my original target as too often in these forums, target is:
this Instrument Stack new feature is delivered in an unfinished state.

Sorry, it’s a bit difficult to follow for a few reasons.

  1. I see a bunch of aux sends on that MIDI track pointing a common channel 8 on 3 different instrument tracks. I’m guessing the main output of the MIDI track is also channel 8.

  2. I can’t see in the screen shots how the routings and plugins in the Instrument stack are set up.

What I can gather is maybe you’d like to move that MIDI part to the Instrument Stack and have it play the same thing over 4 different plugins on channel 8?

Hence, my initial questions become…

Are all of the instruments in the stack set to channel ANY?

Has the MIDI Part been frozen, so all of its events are hard coded as Channel 8 events?

I’m not sure how that’s off topic. I’ve always needed to do the freeze part and set the instrument track outputs to ANY before I could work with multi-channel data in instrument tracks.

To my knowledge Cubase has never provided the ability to real-time modify the channels of parts sitting on instrument track lanes like we can with track end points. I’ve always needed to freeze such things first.

I’ll go away now since I can’t try it on 16 today to see what’s really going on in this case. I just wonder what might happen if you freeze that MIDI track to channel 8 first before dragging it down, if possible make sure all the instruments are set to channel ANY if possible, and of course host the relevant sounds on channel 8.

Where I do have experience to some degree, is that I’ve been stacking plugins for over a decade using bidule, so have been working with multiple channels on instrument tracks a good bit, so the post jumped out at me.

Either way, good luck. Sorry I got off topic somehow. No need to reply unless it’s tried and works. I’m off to be out of the way now.

Sorry but please do open another thread with what are your thinking about the Gobal subject of midi management in Cubase especially handling of midi data vs tracks.
And I assure I will answer because I don’t share all your assumptions and I have also some background with midi.
Here my topic is focus on the new Cubase 16 Instrument Stack and its lack of channel management.

… And from your declaration, you even have no Cubase 16.

Please get off my case. I told you I’d go away.

I just tried to help possibly achieve the goal of moving a MIDI track with 3 aux sends over channel 8 to an instrument track, and have the proper things sounding on channel 8. I saw a problem with a possible solution.

If you tried it, and it didn’t work, I apologize for wasting your time.

The topic says ‘no way to convert one track type to another’. I thought there ‘might be a way’. I’m done here. Good day.

If it was insufficient, let it go please. I will. Done…

I’m curious about this comment. In particular, I can understand the need to change MIDI channels in multi-timbral synths used to play multiple parts within that single instrument in general. I could also understand the potential need to change the channel broadcast to an instrument if external synths were supported within instrument stacks (e.g. to deal with limited MIDI connections where different external instruments sharing the same basic MIDI port need to be on different channels), but I don’t think external synths are supported for instrument stacks at this point.

However, I’m not clear on what the need would be in this specific context (i.e. the instrument stacks), which, for simplicity, I might characterize as driving multiple synths/instruments from a single MIDI part (albeit with some potential for customizing the MIDI going to individual synths beyond that feeding the entire stack of instruments). (I should also note that I do see the potential inconvenience factor if just needing to convert setups initially done in another way. I’m specifically asking about the general need if setting up something in light of this capability, as opposed to for converting older workarounds to the lack of this sort of capability.)

This comment relates to the fact that within the MIDI data contained in a ‘pilot’ track, a channel is specified, and the same set of MIDI data can be marked for different channels.

If the main output of this ‘pilot’ track, which contains the MIDI data, is set to channel X, all MIDI data sent to the ‘Sends’ will be updated with that channel X. In this case, there’s no point in having a Send that filters to a channel other than X; the instrument will remain muted.

However, if the main output of the ‘pilot’ track is set to ‘Any’ (any channel), then nothing is converted. This allows a particular Send to filter to a specific channel and thus send different data to the instrument targeted by the Send.
This doesn’t seem possible with current instrument stacks because no MIDI output channel can be specified.

However, I acknowledge that this is a very specific and uncommon use case. :wink:

My current dilemma is whether I should convert all my instrument/channel groups to stacks right now, ignoring the channels themselves. Implementing a stack is much simpler than my current setup (where choosing the send targets is tricky), or should I wait for a possible addition of an output channel to the stack, given that I doubt Steinberg will go so far as to add a channel to each instrument slot?

I’m not sure I understand all of what you described above, but my (quick) thinking on this general question is that, if I were in this situation, I wouldn’t be likely to convert existing projects – if they’re working as they are, why mess with that? For new projects, though, if instrument stacks can work for your needs (there is the take lane/comping consideration, for example), it might be a whole lot simpler to set things up with them, not having to worry about MIDI channels, than having to painstakingly set up sends, make sure MIDI channels match differently where needed, etc. And, if you do need different MIDI data on instruments within the stack, you can always put that specific MIDI data on the instrument-specific track, keeping only the stuff that applies to all instruments on the stack track’s MIDI.

With respect to waiting for the possible addition of an output channel to the stack, do you do prediction markets and bet your results on those? :rofl: I’m thinking the key justification Steinberg would have for doing that was if they decide at some point to support external instruments, in which case that might be mandatory to be able to deal with MIDI hardware setup considerations.

Thus, the key question in the near term would be if using the instrument stacks can make the setup simpler, do everything you require in light of what is and isn’t supported, and thus make any work for incorporating them in new templates and such worth whatever effort is involved.

My general thinking on instrument stacks for my own uses is two-part: For what I’m working on in the near term, it’s unlikely I’ll have any need for them anyway, due to the nature of the music an no real need for layering instruments playing the same parts. If at some point I get back to a type of music that involves synths, and they add track layers to the instrument stack (those are critical for the way I track and comp most of my virtual instrument parts), then the instrument stacks greatly simplify setup, and I can definitely see using them for complex pads where I want to combine virtual instruments from more than one maker. While using something like Waves StudioVerse could do it now, the Instrument Stack setup is really convenient. I’ve never been in a position where I am using the same sort of stack arrangement on multiple projects, so this ad hoc capability of being able to create a stack under an already-familiar interface (e.g. no learning a third-party plugin interface to do a similar job) decidedly suits my workflow.