Daniel Jones

I've just looked into this. Weirdly, I can't find a property for this within API (at least, according to the reverse-engineered [docs](https://structure-void.com/PythonLiveAPI_documentation/Live11.0.xml)), but this would be quite an anomaly as...

Going to close this one as it appears to be not possible given the current Live API, which I'm a bit baffled by...

Funnily enough, you raised this at the precise moment that I also need this feature so I'm working on this as I speak. Should be done later today!

OK, I looked at this and unforunately it's a larger refactor than I have time to do right now as i'm on a project deadline. However! You can achieve the...

Hmm, this would happen if the audio input device of SignalFlow has fewer than 8 channels. If you set your system's default input device to (say) BlackHole 64ch, this should...

Hi @leolabs, Thanks for the thoughtful comments. This is an approach that I've thought long and hard about in the past... With this approach, namespaces would then become closer to...

Just looked into this, and listeners are sends are not yet implemented as send levels are handled slightly differently to most track params - needs adding.

Hmm, I wonder if this is actually an internal Live issue!? The LOM documentation says: ``` "Fire the selected scene, then select the next scene. It doesn't matter on which...

It's a good point, but the `fire_as_selected` method is specifically an object method that requires a `Scene` to operate on... so it can't be called without a target! Instead, I've...

Hey @Coupe70, just checked this out, and yes, you can do this to achieve the above: ``` >>> /live/view/set/selected_scene 0 >>> /live/scene/fire_selected >>> /live/view/set/selected_scene 2 >>> /live/scene/fire_selected ```