When using an instrument track and creating multiple outputs the track mute functions in an odd way. Normally the track state matches the mixer state, but not in this case. Now the track state and mixer state are 2 separate entities, which is not ideal. Is this considered a bug or a “feature”?
The other thing that creates a problem is that mute commands that communicate active track state are based solely on the mixer, so that it kind of breaks those functions as well.
Hi,
This works as specified.
In the Project window, you Mute the source MIDI. In the MixConsole, you Mute the Audio Return Channel.
Hi Martin,
Thanks for the clarification that this is an intended design feature. That was my assumption but I think there are some flaws with this workflow. For any external controllers, mute state only affects the track at the mixer level, and logical editors deal with the project track state being muted. Also the inspector and track mute state are linked, but the channel left zone is linked to mixer mute state. So this does create a bit of unintended chaos.
Hi,
Correct. All Remote Devices control the MixConsole Channels.
I don’t think so. It depends, if you are controling a MIDI Track or an Automation Track (which is the Audio Return Channel).
This is actually great because you can see both (the Track - MIDI - and the Channel - Audio Return Channel) in one place.
Hi Martin,
I think if I could make a suggestion to the function I would have the track mute and default mixer output link so that mute state would translate at least to the main out, and then mute and other parameters of the remaining outputs could always be combined by linking tracks. Having the track and mixer mute state unlinked does create a bit of workflow weirdness.
Hi,
The problem is that Cubase doesn’t know the internal routing in the Instrument. So it doesn’t know, which MIDI Track is internally ripped to witch Audio Return Channel. That means, it doesn’t know, which Audio Return Channel to link to the given MIDI Track.
Hi,
I understand, but I also think Cubase is making some assumptions in that area too. Since the main output is always enabled, if you select the track in the project and use an external controller to mute the track - it mutes the default output, or the output tied to the left channel zone. So if they’re making that correlation there, it’s weird that they don’t take it one step further to link the midi part of the track and the audio return. Just my opinion though
Hi,
It is enabled, but you don’t have to route any signal into it.
In this case, you don’t Mute the track. An external controller Mutes the Instrument Return Channel in the Mixer, i.e. the Main Out in this case.
You can do this manually in the Inspector. But as this is optional, Cubase doesn’t rely on it.
If you mute the main audio output of an Instrument Track in the Mix Console the MIDI gets muted as well. This becomes extra apparent if you use an instrument with an internal sequencer or other sync properties. I think that behavior is an issue.
Hi,
Even in case, you are using multiple MIDI Tracks rooted to the given Instrument Track and/or multiple outputs on the Instrument? This shouldn’t be the case. This should happen only, if you are using a single Instrument Track.
In my opinion, it shouldn’t happen at all. Here’s why I believe it shouldn’t:
I can’t come up with any arguments why the current behavior would be favorable.
Hi,
To simplify the workflow for the basic use case (beginner users who are not using multi-outs and/or multi-MIDI-Tracks), i.e. a single Instrument Track use case.
As I value your input, would you care to explain what you mean by this as I don’t quite understand.
All my arguments above are based on a use case where a single Instrument Track is used with no multiple audio outputs.
Hi @m_sandler - I haven’t noticed, but are you saying the inspector might have the “M” button highlighted on while the channel left zone has it off/not highlighted (or vice versa)?
That would be very confusing to me if that’s the case …
Thanks!
Hi,
Yes, totally. This is possible, if you use multi-outs or MIDI Tracks routed to the Instrument Track.
Oh, my! Thanks for showing that example, @Martin.Jirsak .
If you’re still there, and had an extra moment, can you please show a screenshot of using multiouts where Left zone “Channel” indicator doesn’t show a “Mute” activation, but the Project Window/Inspector shows some tracks with “Mute” activated ON, and some OFF?
(If that is what you mean?)
Hi,
Easy task… 
Your instrument is using multi-outs and you want to Mute the MIDI source data, but not the output (because ather MIDI track bight be routed to the same output).
Hi,
And this is the other way around…
You Muted the Instrument Return Channel, but you kept the MIDI unmuted. On this screenshot, you can see the Channel is Muted, same as the HALion Sonic 01 “automation”, which is the Instrument Return Channel representation in the Project window. But the source Instrument Track is not muted.
Even though it’s one Instrument Track, think about it like 2. One source is MIDI Track and another Instrument Return Channel. This is how it was working in the past (with the Rack Instruments). You had a MIDI Track and you had an Instrument Return Channel.
Later on, Steinberg decided to simplify it for the simple use case, if you have only one MIDI Track and one output for the given Rack Instrument. This is, how the Instrument Track was born. Later on, the users asked to be able to route MIDI Tracks to Instrument Tracks, which also required multi-outs. Now, we are in this situation. But under the hood, it’s still the MIDI Source and Instrument Return destination.
I hope I bring more light to this.
OK, that is great, I think I understand, thank you.
(I don’t route other MIDI tracks to the same output, but I will think about whether that is something I want to do now).
Thank you for this also @Martin.Jirsak ! I’m not so clear about this one though. If I wanted to mute Output 1 for the mult-iout instrument, but I did want to hear Output 2 … I wouldn’t be able to do that in this instance because the Left Zone has a “Mute” = On state.
Is that correct?
