Patrick

The RackObject is well documented and has the attribute *chains*, which should contain a list of all the chains that linked to the drum pads.

This seems to be the case, as the list of objects under the chains attribute is representative of what's in the rack. I've tested this by adding and deleting devices on the drum pads.

However, it doesn't return typical *Chain* objects, but *DrumChain* objects.

Nothing about DrumChain objects is exposed- no properties, no children, no functions. Calling getinfo on these DrumChains just returns this:

info description This class represents a drum group device chain in Live.

If this is a change to the API, it's not documented anywhere and it seems it hasn't been discussed anywhere else on the net.

I'm trying to parse across all the devices in my set and this is completely screwing me up. It's a complete stonewall that hides every device sitting in the pads of a drum rack.

Can anyone confirm that this isn't something I'm doing wrong...or otherwise show me how to get access to devices linked to a drum pad? It would be seriously appreciated.

However, it doesn't return typical *Chain* objects, but *DrumChain* objects. 

info id 1974
info type DrumChain
info description This class represents a drum group device chain in Live.
info done 

Can anyone confirm that this isn't something I'm doing wrong...or otherwise show me how to get access to devices linked to a drum pad? It would be seriously appreciated.


drumchains-instead-of-chains-undocumented-change-to-api

Yeah I'm getting drum chains too, but depending on what you want to do I bet there's a way around it. You'll have to make a special case for drum rack devices. What exactly are you looking for? You can still access the devices in a DrumChain by using a path like 'live_set tracks 0 devices 0 chains 0 devices 0'. The first device in the first pad in a drum rack on the first track.

Yeah I'm getting drum chains too, but depending on what you want to do I bet there's a way around it. You'll have to make a  special case for drum rack devices. What exactly are you looking for? You can still access the devices in a DrumChain by using a path like 'live_set tracks 0 devices 0 chains 0 devices 0'.  The first device in the first pad in a drum rack on the first track.


If that shortcut works (I'm not at home to test it right now), that's absolute perfect and just the kind of workaround I was looking for. I've got no problem writing up a special case, so long as there's a way to do it. Thanks for the info, it is very much appreciated.

Basically, it's a little patch for a live performance set that will parse through all devices and reset macro knobs back to their default values.

That way I can jam and develop the set while having a easy way to reset it at the end of the session (as opposed to reopening the saved set, and losing any modifications/improvements).

I'll test it later on tonight. Thanks again for the help.

If that shortcut works (I'm not at home to test it right now), that's absolute perfect and just the kind of workaround I was looking for.   I've got no problem writing up a special case, so long as there's a way to do it.  Thanks for the info, it is very much appreciated.

Basically, it's a little patch for a live performance set that will parse through all devices and reset macro knobs back to their default values.  

I'll test it later on tonight.  Thanks again for the help.


The bypass of this problem using a direct path works like a charm.

path live_set tracks 1 devices 1 chains 0

...returns the same dead end DrumChains causing the problem, but

path live_set tracks 1 devices 1 chains 0 devices 0

...gets the chain of the first drumpad just as expected. The rest will be simple; thanks so much much for the help Evan.

...gets the chain of the first drumpad just as expected.  The rest will be simple; thanks so much much for the help Evan.


"Drumchains" instead of Chains....undocumented change to API?