CC control for Solo/Cue button.

[RobertX]

Both Solo/Cue and Speaker On are binary controls, but Solo/Cue doesn't have an editable range, while Speaker On does. Any reason for this?

When the fader is at zero I want to disable the track and enable cueing



Sorry for the retina display graphic that destroyed the world.

[madlab]

I don't really see the point unless you have multiple assignments and want to reverse some. Nevertheless, I sometimes find that the way the mute and solo buttons work is a pain when you design a remote interface with Lemur for example.

[RobertX]

I must be doing something wrong with routing then.

I have a UA Twin Solo, routing Master Out to stereo 1/2 and cue to virtual output 7/8. When I cue something, the behavior is as you'd expect it, but if the cue is on and the track is enabled it clips the master output by a fair about. If I disable the cued track's channel, cueing behaves exactly the same except there was no clipping.

My idea was to assign Solo/Cue a 0/0 value to enable it with the fader down, and 1/127 for Speaker On so it's enabled for any position other than down. If Cue/Solo had an editable range I would have gotten away with it.

[madlab]

Don't know the Twin solo but as you mention virtual outputs my guess is this is just a virtual port and the signals to 1-2 and 7-8 are sent to the master output, hence the clipping. Maybe you have some setup on the sondcard interface that would make the master and alternate outputs exclusive ?