[sharing is fun] Live.API_explorer

[3dot...]

seriously, i can open the max window but it's totally blank.....!
D

serioulsy, you probably have a problem with you Max for Live installation.. (?)
this a standard device, not frozen, without any abstractions or dependencies ; so there is no reason why you couldn't edit it.


MathieU

can't edit either...

[S4racen]

I think there is something wrong with my installation, it crashes when i'm trying to save a patch virtually every time...

Cheers
D

[Surreal]

As I'm becoming more familiar with the Live Object Model I'm really starting to hope that we'll get some objects that will provide a more immediate way to talk to the APC and Launchpad control surfaces. The live.path/object/observer/remote~ objects are fine for adding an extra LFO to Operator or something, but trying to use them to create custom remappings looks like it could get pretty painful.

things like button matrix make me hopefull, i think we should probably just wait for the control surface path for these talks

[charles_2]

Have you been able to do anything with that data?
For example, can you monitor the offset of the red rectangle in Session view?

I was able to call functions "turn_on" and "turn_off" to turn buttons on and off; so far I haven't found anything about the red rectangle, or how to intercept incoming signals. I'd investigate further but I think Surreal is right, there's probably more to come, so for the time being I'm going to focus on what I can do with the existing objects.

[Surreal]

seriously, i can open the max window but it's totally blank.....!
D

serioulsy, you probably have a problem with you Max for Live installation.. (?)
this a standard device, not frozen, without any abstractions or dependencies ; so there is no reason why you couldn't edit it.


MathieU

can't edit either...

Do not double click on the patcher.

[charles_2]

I'm able to open and edit Mathieu's device with no problems.

[3dot...]

yeah me too.. it's a bug I guess....
it happens also with patches I saved...
first time they're open I can't edit...
second time... I can
...weird

[rabouille]

excellent, please post that to www.maxforlive.com, would be great for the community
thx

[natecraypo]

Here's a list of the controls for the APC control_surface object:

Thank you for that. I think we all needed that BIG TIME. I can tell you that control values 60 & 61 are for footswitches. However, I do not think they have a designated control name. I made a post on this here: http://forum.ableton.com/viewtopic.php?f=35&t=144702

Thanks again.

[Hanz_Petrov]

Interesting. The footswitches correspond to the missing numbers in charles_2's list of controls (60 & 61). In fact, the control IDs seem to be assigned sequentially as the control elements are instantiated in the APC40 python remote script - starting with the Shift_Button, and ending with Send_C_Button.

Also, the python code confirms that for some reason Ableton has not assigned Name values to the footswitches (actually mapped as slot_launch_button and launch_button). This would have been trivial to do; might be worth reporting as a bug.

Best,

Hanz

[natecraypo]

mapped as slot_launch_button and launch_button)

cool. thanks.