At present the disablement of tracks is only available as toggle. I would like the absolute commands so I could build disabling tracks into a macro for projects with multiple VSTi’s or heavy guitar amp plug-ins when I only need to record one at a time.
Hope that use case is clear. And no I don’t want to use ‘constrain delay compensation’.
There are many other functions that would benefit from separate on/off absolute commands.
Agree 100%.
(It would also be fantastic if we could read the value/status of all such functions via MIDI Remote.)
I agree too.
Functions involved in the mixer level (instrument/plugin slots) can be exposed. Interested to know more about this. One or two examples would do 
Until something like this is added, here’s a suggestion:
I presume that you have some macros, ples, whatever, in order to select the tracks you want, without caring if they are disabled/enabled, and this is why you actually want the absolute command. IF this is the case, here’s a PLE to absolute disable:
This deselects tracks which are already disabled, so when the post-process enable/disable command will now act as a disable, since it will be performed just on the enabled tracks. For enabling we can do a similar PLE.
Any part of Cubase really.
Inspector sections, Zones (Left/Right/Bottom), Options in the Key Editor such as Step Input e.g., folded state of a Folder Track, currently active Quantize value, Preferences that are currently available as Key Commands…
The list is long.
I see. This is not to be expected by the MIDI Remote at its current state, since what it basically handles are a) the mixer and b) the transport. I’ve seen your requests in the past, and I think that what you’re asking should be provided as an extended PLE scripting tool, giving the ability to query everything. The MIDI Remote API could be a candidate for this, especially after some latest additions, if the above maps are added. Totally doable.
The perfect recipe for the present time. I had no idea disable was available as a Property. This helps me achieve what I want.
Thanks!
I think it is an excellent candidate for several reasons. The foundation is already there. Being able to access more (all?) functions and statuses in Cubase would be amazing for controllers and surfaces (Metagrid Pro e.g.).
