(Not sure if Bug -->) Mute/Solo on Mixer send CC7 0/127

[Lytz1]

So what is a bit strange and I don't know if this is by design or not
is that all mute & solo buttons send the same controller CC as the volume fader.
(by default: CC7. if the volume slider is assigned to a different CC, then they also send a different CC)

They do this in a toggled fashion: 0 & 127. You press one solo or mute button and the CC7 is send on ALL ports/channels,
which messes up everything that is connected to the ports and responds to the CC number in question(!)

If this is NOT by design, it would be good to disable this, as using the Volume CC7 from the mixer to control
external synths/host/etc volume - is very nice. However, as soon as I press mute or solo, everything (!)
on all outputs/ports/channels that respond to CC7 gets messed up.

Best,
tL.

[Lytz1]

Another idea if this is hardwired by design:

If possible, let the mute/solo button remember the actual set CC7 volume data
and don't let them toggle between 0-127.

(i.e. Volume CC7 is set to 95, so mute and solo toggle between 0 and 95.
That way we don't end up with every synth, channel or other things that
react to CC Volume on 127-max volume.... Not good...Messed up some mixes already
and I didn't know at first what is going on...)

Thanks,
tL.

[Jerm]

(i.e. Volume CC7 is set to 95, so mute and solo toggle between 0 and 95.

I believe this is how it works but I will verify.

[Jerm]

Yes that is how it works. You need to be sure your mixer levels are set properly before using the mute and solo buttons. You can do this either by manually setting the mixer channels volume. If you record CC 7 into the MIDI track assigned to a particular MIDI channel you will need to play it back to set the mixer channels volume.

[Lytz1]

I believe this is how it works but I will verify.

Alright, please do that. On my end, it really toggles only between 0 and 127 on all channels.
I can see all the faders jumping in Apple Mainstage to zero and max Volume all the time
when I click any solo or mute button.



Maybe they need to be "initialized" first to a specific value? But I don't see how that would make sense.
Would result in zero flexibility if CC7 needs to be written to a track to prevent solo/mute
jumping around 0/127... So I think something might be indeed wrong.

[Lytz1]

Yes that is how it works. You need to be sure your mixer levels are set properly before using the mute and solo buttons.

Hmm. Okay, so every fader in the template needs to be initialized first to prevent this. Correct?
I will check this out. If it only needs to be done once, then that's ok.

[Lytz1]

No, I am sorry. No matter what I do, I end up with all faders 127 (+6db) after clicking any solo or mute button.

I didn't test this with "printing" Volume Automation to the channel though. I am sure this works,
but I can't automate every fader of a template. Too much work and obviously it is impossible to mix
as all faders are "locked" in position.

Well, too bad then. Would have been nice to do this in Metro directly.

To be on the safe side, I'll send you an animated gif to your email so that you can confirm that this is really the default behavior.

[Jerm]

The animated.gif is helpful, I will take another look and let you know.

[Jerm]

It looks like you are using IAC buss. You must be very careful with MIDI thru or you will create a feedback loop. I first set up a similar scenario whereby I was sending MIDI data through the IAC buss and recording the data in Metro LX while moving faders and pressing mute and solo in the mixer of Metro. With MIDI thru on, all kind of errors resulted but when I turned MIDI through off. I got the exact expected results in Metro LX. If you want I can show you the results from the event editor.

[Lytz1]

It looks like you are using IAC buss. You must be very careful with MIDI thru or you will create a feedback loop. I first set up a similar scenario whereby I was sending MIDI data through the IAC buss and recording the data in Metro LX while moving faders and pressing mute and solo in the mixer of Metro. With MIDI thru on, all kind of errors resulted but when I turned MIDI through off. I got the exact expected results in Metro LX.

Aaaah, I see. Thanks a lot!

There indeed was the "Automatic Midi Thru" ON in the switches menu.
That solved it. I just looked at the transport bar
and it was saying "Midi Thru: off" Well, that's the manual one. I understand now.

Thanks again,
tL.