Continuing my adoption of OSC, there’s one action I was planing on using because I often find myself having to go to the preference dialog to change the “Exclusive Solo” flag.
According to the manual, there is a /Solo/toggle-exclusive-solo action available.
Problem: when I use the following command, it doesn’t actually change the behavior of the SOLO buttons as expected and the checkbox in the preference dialog isn’t affected either …
You have misunderstood (and/or we have not made clear) how OSC interacts with actions.
Even though actions look like an OSC path, they are not equivalent. To access an action from OSC, you need to prefix the action path with “/access_action/”
Ah, sorry I should have read more carefully. Very silly of me.
It works just fine here. You must have some other option set that prevents exclusive solo. One would be that you’re using a monitor bus with solo-controls-are-listen-controls.
Hmmm, well that’s not the case but it did put me on a lead.
I’m not used to using the “Monitoring Section”, I don’t have it activated in my sessions (small setup, audio card with a single output pair, it takes space on the screen for little value in my situation I think)
If I do activate the Monitoring Section, then the OSC action does toggle the exclusive solo flag and it’s visible both on the Monitoring Section button’s LED as well as the checkbox in the Preference dialog !
But if the Monitoring Section is not active, then the OSC action has no effect at all while I expected it to affect the Preference checkbox (which is where I generally go to when I want to change this behavior)
P.s. After re-reading the user guide for the Monitor Section, I guess I could make better use of it …
… which itself another lead. The action in question is defined by the monitor section code, and does not exist if there is no monitor section. This is mostly because the other “nearby” actions like “Solo controls are Listen controls” are impossible without a monitor section, but this one really should defined in the main mixer code, since it does not require a monitor section to function.
I would say that argues against this even being a preference. It is incredibly useful to move between exclusive and non-exclusive solo, and it should not be necessary to go to Preferences to make that change. Which is why we exposed it in the monitor section …
Sure, but that doesn’t address OSC access … which you’ve taken care of with an arguably better solution already. In addition though, kbd bindings require actions, and this one doesn’t exist without the monitor section.