It appears that mapping MIDI remote to key commands (to select tools, for example) does not provide feedback to the controller.
If I map to something like active track mute, I do see a MIDI response back to the controller.
I find this believable, but a bit disappointing. In searching the function browser, I see no way to query the currently selected tool (eg. Object Selection Tool, Erase Tool, etc.).
This could be somewhat mitigated by a custom script that keeps track of the last selected tool. However, in that case, there appears to be no way to discover the initial tool value at startup.
Additionally, manually changing the tool selection from the tool bar apparently generates no MIDI feedback, so there is no way to report the change back to the controller.
Any suggestions? Future plans to extend changes via key commands to report back?
It works as specified. Yes, the Key Commands don’t send a feedback to the hardware.
In theory, you could force the init state (for example set the Object Selection Tool when loading the script or when switching the page). But this might be tricky, as we have 3 versions of the Object Selection tool: Normal Sizing, Sizing Moves Content, Sizing Applies Time Stretch. And you wouldn’t get feedback, which one is currently active.
I agree that I could force an initial state. Provided the control was always initiated from the shortcuts, this would work.
The problem, of course, is that a change using the mouse in Cubase would now cause a mismatch, since there’s no event generated.
Thanks for the verification. I think I’ve run into this situation before! Arguably, features that can be initiated by MIDI control mapping should have the ability to report back an event. Even just forwarding the mapped MIDI if the key command is mapped would likely be adequate for my purposes.
The obvious workaround is to be consistent if using MIDI control of key commands.
I don’t think it’s an easy task. Cubase could just simply return something like “function fired”, but it doesn’t say anything. You would really need to receive the state. And this is not an easy task anymore.
Anyways, I would recommend you to add the optional feature-request tag to your post.