Daniel Jones

Yeah, I did think about "action-less" setters when first designing the API, but I wanted symmetry/consistency between `get`, `set`, `start_listen`, `stop_listen` (plus there are other actions like `/live/clip/add/notes`), so I...

Hi there @mindexxx, First to quickly say that that video was created by a third party, so I can't 100% vouch for its contents, but can help with pylive/AbletonOSC. The...

Hi @nlahmi, could you say more about the steps you'd be looking to accomplish? Would this be something like the below? 1. create a new audio track 2. load one...

I've just had a quick look at the [docs](https://structure-void.com/PythonLiveAPI_documentation/Live11.0.xml). Not exactly sure how this is achieved but I suspect using `Live.Application.Application.View.focused_document_viewProperty`. This won't be a priority for me right now...

I don't think the two are totally inconsistent; `/live/song/get/track_data` returns a record for every clip **slot** on a track, whether populated or not, and `nil` is the best way to...

Let me know if you can provide some more info on this one. Thanks!

Ah! I understand, thanks for the clear explanation. This is because the track index is captured in a closure when creating the listener, meaning that the track ID isn't re-queried...

I've had a more detailed look at this, and have also added a [unit test](https://github.com/ideoforms/AbletonOSC/blob/master/tests/test_clip.py#L89) that can be used to test bidiretional long messages. It populates a clip with a...

I've just tested this (`/live/song/get/track_data 0 -1 track.arm`) on a few different sets and haven't been able to reproduce. Can you confirm what git commit you're running, and whether this...

Oh yes, just tested with the Tutorial set and I do indeed see the same behaviour. I've just taken a quick look, and it looks like it's because the Tutorial...