Does MIDI Remote API support folder tracks?

Cubase
1

When a folder track is selected and your controller operates Mute/Solo buttons, these buttons should affect all the tracks included in the given folder, shouldn’t they? Unfortunately, this expected function works only via a mouse or a keyboard, not via external controllers. I ran against this issue with CC121 using the factory CC121 driver, as well as with my own MIDI Remote API script for Roland FC-300. When a regular audio/MIDI track is selected, Mute/Solo buttons work perfectly, but for a folder track, these buttons cannot be operated via the MIDI Remote script at all.

Do you observe the same?

2

Of course.

Folder tracks are not part of the mix console channels. MIDI Remote handles these channels. I recall you had assignment to the mMute value of the selected track. You can alter this to the command Edit→Mute, it basically does the same thing without the limitation correctly observed :slight_smile:

3 Likes
3

Thank you for this advice, however, I will rather let it as it is because with a command binding I couldn’t reflect the Mute/Solo state of the currently selected channel on my controller LEDs.

4

I understand. Note however, that we can always grab the value, even when no real control is involved (i.e. no actual MIDI binding), for example:

var customMute=surface.makeCustomValueVariable("customMute")
//Just for getting the mute value, no MIDI binding involved

page.makeValueBinding(customMute,selectedChannel.mMute).mOnValueChange=function(device,activeMapping,value,diff){

    setLight(device, CTL_PEDAL_1_LED, value * 0x7f);

}
2 Likes
5

Thanks so much! This is, indeed, a clever solution :+1:t2:

6

I’ve come to the conclusion that it would be better for me to create a link group for the tracks I want to control together rather than trying to control them via a folder track. Anyway, thank you very much for the Custom Variable trick! I wasn’t aware of this feature :grinning: