No lanes on new instrument stacks?

Hi guys,

very short and sweet:

Am I doing something wrong, or are there really no lanes when using the new instrument stacks?

Hi @James_Heafy ,
short and sweet answer: Yes there are :slight_smile:

Make sure that recording mode is set up accordingly in your project
grafik
(bottom left in your project window)

and also make sure to unfold the lanes afterwards


(track header).

Hi,

Thanks for the answer.

What you are showing me seems to be a track of one of the single instruments inside the Stack. I have lanes there too. I’m trying to activate the lanes on the Stack track itself, as the whole purpose is to have a single track playing all the instruments at the same time. Are you able to get that to work?

Thanks

Ah, okay. Sorry, I thought you were referring to the actual tracks inside the instrument stack.

No, I don’t think that’s possible because the stack track at the top is basically a folder. Maybe someone else has an idea but I am not overly optimistic. Sorry…

@Reco29 Thank you. I dont get it. The whole point of the stack is to be able to play multiple instruments with one track. Using lanes and comping is probably the most important feature when recording, besides the record button itself. I can’t really believe that it’s not supposed to be there.

@Matthias_Quellmann Do you have any idea if this is the way it’s supposed to be? Or maybe a bug? How is this feature to be used?

Thanks

In ā€œTrack Controls Settingsā€ there is options to set control area configuration for all tracks except instrument stacks.

Probably in some futures update we will have the possibility to add lanes, for the moment we will have to drag & drop all those midi take to a instruments or a midi track that have lane.
But it also means that comping directly from instrument stacks is not possible for the moment.

Maybe i’m wrong but it seams to be the case for the moment.

Unfortunately, you’re not wrong, and this omission pretty much makes instrument stacks unusable for me for the moment. In particular, the key reason I’d want to use instrument stacks would be for cases where I want to track parts against layered sounds I’ll actually be hearing (something I want to do in most every instrumental context actually since the feel of the sounds will influence what I play in areas like MIDI note velocity). I’m generally making parts up as I go, so I experiment with tracking multiple takes in looped mode until I feel I’ve got enough raw material, then go back and comp from those take lanes.

I was wondering if it might be possible to work around the lack of take lanes and comping by doing the looped tracking in a MIDI track and routing that MIDI track to the instrument stack track. However, it turns out instrument stacks aren’t available as an output from a MIDI track. (You can use the component instruments as outputs.)

It could be possible to do things the pre-instrument stack way, such as using a MIDI track and MIDI sends to instrument tracks, do the tracking and comping there, then convert to an instrument later and move the comped MIDI data to the instrument track lane for any further editing – or just use a third-party facility like Waves StudioVerse Instruments, for that matter. But, at least in my mind, the main benefit of instrument stacks is simplifying the setup for layered instruments playing the same part since there have always been ways to work around the lack of this sort of facility.

Hopefully Steinberg will address this limitation in the future.

It seems Instrument Stacks are only Group Tracks in disguise?

Well, IS is just a workflow shortcut over an already-possible technique, not a fundamentally new capability. If one comfortable with shared MIDI parts & MIDI inserts, you can do ~90% of what IS do today. The IS just packages that into a more… uhm… opinionated, single-clip workflow with fewer moving parts… but… at launch (ofc), some rough edges make the folder approach feel more reliable for now.

That would seem to be half of it – i.e. the audio routing part and organization (e.g. ability to collapse). However, there is also the half that lets you send the MIDI from a single track (i.e. the instrument stack track) without having to jump through hoops and that lets you do some complex configuration such as note ranges that each instrument within the stack responds to (in the MIDI Modifiers section of the instrument stack’s track) and some other capabilities.

From my perspective, it is (or at last could be if the track lanes/comping limitation was removed – there might be other limitations I haven’t run across since that one is a biggie for me) a significant improvement in workflow over previous methods, and even minor improvements in workflow can yield worthwhile dividends on the productivity front. I particularly like that these stacks can be set up quickly on an ad hoc basis, getting me up and running with a custom stack (and every stack I’d be likely to make would be custom as every project’s needs are different) in the space of choosing the instruments and choosing the presets for each instrument, then doing any tweaking I might want to do beyond that bare minimum, be it within the instruments themselves or note ranges for the various instruments in the stack, or whatever. No needing to configure MIDI sends or, more likely what I’d do in the past, just track to all instruments in parallel (so I can feel what is going on in response to my playing with the sounds I’ll be using) then do any comping and editing on one of the tracks and copy it to the others.

Interesting, @rickpaul… but; the uncomfortable truth is… Steinberg deployed a feature that is architecturally correct but integrationally incomplete; via our evaluation; the design is better than folders; buTTtt… the execution is worse than folders.

Both things are true. The ā€œit’s just a folderā€ is right that you can replicate the core function today without it. The ā€œit’s a workflow-changerā€ is right that the end state will be meaningfully better. The question is whether you can live with the current gaps, & for some creators the answer is yes, with one or two workarounds.

So, for some; use folders if you need reliability right now. Use IS if your workflow is layered a few things, set key ranges, play, move on & you can tolerate the rough edges.

I was hoping to be able to use the new Instrument Stacks, feature to provide separate instruments for performances of both the left and right hands, within the same container but it seems instead to be geared more towards having multiple instruments sounding together simultaneously, rather than allowing separate editing for individual parts of a unified instrument.

IS is the right tool for layering; unfortunately, it’s the wrong tool for splitting. No patch will change that; it’s the architecture, not a bug. For left / right hand work, the folder method isn’t a legacy workaround, it’s the correct tool.

Hi,

I just use 2 instrument tracks and then feed the audio to the same output.

I can edit the notation of the left, and right hands individually, which is great for changing velocities, in situations where notes from either hand are sounding simultaneously, but to be able to do this within a single container that is not a folder, would be awesome for my workflow, at least.

Hiya!

Hmm… it seems you’re not asking for a new capability; you’re asking for a cosmetic / organizational improvement; one-track header instead of two, one place to look in the project window, ect.

IS won’t help; & to… ā€œwould be awesome for my workflowā€; sure… butTTtt… the cost of building it; & maintaining it across every integration point - duplicate, freeze, archive, MIDI inserts, comping, ect. is high, & the benefit is organizational rather than functional. Steinberg will never prioritize it, & that’s fine, because your two-track method already does the job.

I don’t think this can be said or asserted with any degree of certainty, since it is a new feature.

Steinberg’s history does.

Steinberg often do things that end users don’t expect, which tend to have a mixed reception, with some detracting while others are broadly supportive, and even more looking for ways to improve a particular feature; this I believe is one such instance.

Agreed. For the music I’m working on at the moment (fairly traditional country, albeit with virtual instruments instead of real guitars, lap steel, fiddle, etc.), and probably through most of the first half of 2027, I’d be unlikely to use instrument stacks (which I think of as synth stacks) anyway. However, if I did want synth stacks, the lack of track lanes and comping capability would be a dealbreaker for my specific workflow. Perhaps I could find a workaround that would help, but, at least for the moment, that’s irrelevant.

Depending on what you need on this front, it might work. Specifically, if a simple key range split would be sufficient for distinguishing left and right hand parts, this should be feasible – check out the MIDI Modifiers section of the instrument stack’s Inspector view. If you need a varying split, there might be some workarounds that would simplify it somewhat. For example, find a compromise split point at the main track layer, then copy the MIDI from the instrument stack to the lefthand and righthand instrument tracks within the stack and edit out the shifting parts from the main stack and the non-shifting parts from the individual instruments. Seems a bit hairy to me, but no moreso than doing the same thing with a keyboard split in something like a virtual organ.

On the other hand, if you’d do this with two different MIDI channels (e.g. with two controllers sending on different channels), then the Instrument stacks wouldn’t likely do that. A workaround there might actually be to have the different controllers transpose their key range so they aren’t actually overlapping, then put the Instrument Stack split in a position between the two ranges and have the individual instruments transposed to match the two controller ranges. That could allow for editing both parts on the instrument stack’s MIDI track.

Just grabbed 16 specifically to test this.

I’m able to work with different channels on instrument tracks hosted in a stack if I bypass the stack lane/input and route directly through the instrument tracks. The trick in this case is to set channel output to ANY on your instrument tracks in the stack, and make sure the parts/events are hard coded to the desired output channel.

I.E. If you lay down some tracks in a MIDI channel first, be sure to ā€˜Freeze MIDI Modifiers’ before moving them to an instrument track.

If you’re recording directly into an instrument, or a stack, be sure your MIDI controller is hard set to the channel(s) you need (and possibly route continuous controllers directly to VST parameters with track quick controls or whatever). If you’re doing keyboard splits or something into a stack, use MIDI Transformers to set up your splits in each instrument track and arm them just like you would if they were hosted in a regular folder, or group folder.

Here I have multiple channels playing through a stack with one multi-timbral Sonic instance, and one Groove Agent instance. This is to demonstrate that instruments at the endpoint of these tracks are responding to the correct channels…independently if I skip routing through the top of the stack.

Example 01.cpr (2.5 MB)

If piped through the stack this does appear to be the case. The top of the stack converts everything to channel 1.

One can still set up Track Input Transformers, MIDI Insert transformers, and route controllers through the individual instrument tracks within the stack instead of piping it through the stack. In effect, one can still treat the stack like a regular ā€˜group folder’.

So, if all of the plugins in the stack work over channel 1, then one can use the MIDI Modifier of the stack to do note range splits and velocity based layering. It can some in handy for making quick splits and layers from multiple plugins that all receive over channel 1, or are in omni mode.

If I route input through the top of the stack or host parts on the lane like so (I just drug everything to the top):

it all goes to plugins in the stack over channel 1 no matter what I try here. In fact, if I open a MIDI Monitor in any of the instrument tracks in the stack, I see nothing come through, even though I can hear the plugins play (whatever they host on channel 1, but nothing else).

I agree it would nice whatever goes through the top of the stack also followed the routing and mods set up for each instrument track. It seems to totally bypass those and get fixed at channel 1 throughout the stack.

So, the good news is we can lay multi channel lanes or use multi-channel controllers and continue to work a bit with multitimbral stuff through plugins hosted in a stack, as long as the parts live directly on an instrument track, the events are hard coded to the desired channel, and the instrument track’s outputs are set to ANY. We can still route, transform, mod, and arm instrument tracks for controller input individually just like we do for instruments hosted in folders and group folders.

The possibly confusing news is any controllers routed through, or parts living on the top of the stack track only seem to be able to work over channel 1 of plugins hosted in the stack.