Chris Gough

I'm looking at creating a list containing all the devices in a track and in the first chain of any racks along the way, then using callbacks to flag changes then re-test.

I've come up against the liveAPI callbacks not being deleted when resetting the code. from what I've read there isn't a way of deleting them, but i will have to just take note of what ones I've dropped along the way as to not duplicate the liveAPI callbacks? is this correct?

I've tried coding this in traditional max and got as far as the list but creating a bank of observers along the way was tricky, so switched to javascript for a bit more control. I'm having to learn javascript along the way so any pointers would be great!

observe-track-and-chains-for-changes-using-javascript-best-way-to-implement

Yes, it is correct that you have to manage these yourself

I'll create an array of used paths, then check against that before creating a new callback.

yeah, it's a bit of a pain... i have an API to manage all of this stuff, but I haven't worked on it in a while due to other projects... I'll be coming back to it over the next few weeks as I integrate my other projects into Live...

yeah, it's a bit of a pain... i have an API to manage all of this stuff,  but I haven't worked on it in a while due to other projects... I'll be coming back to it over the next few weeks as I integrate my other projects into Live...


Hello. I saw your topic. Were you able to track changes for example in chains / drum rack, I mean changes in device parameters regardless of its position in chains?

Observe track and chains for changes using javascript: Best way to implement?