how to communicate with control surfaces

Learn about building and using Max for Live devices.
amounra93
Posts: 432
Joined: Sat Jan 24, 2009 8:16 pm
Location: Arcata, CA
Contact:

Re: how to communicate with control surfaces

Post by amounra93 » Thu Mar 18, 2010 9:49 am

Beautiful :)) That will help quite a bit...thanks for taking the time and documenting all that.
http://www.aumhaa.com for Monomod and other m4l goodies.

Hanz_Petrov
Posts: 119
Joined: Sat Feb 06, 2010 2:39 pm
Contact:

Re: how to communicate with control surfaces

Post by Hanz_Petrov » Sat Mar 20, 2010 4:48 pm

So here's an example of how to manipulate the "red box" using Max for Live:

Image

In this example, a simple call to the SessionComponent set_offsets method is used to move the box origin to (2,2). Of course, the controller script needs to have instantiated a non-zero SessionComponent to get the red box to show up in the first place.

Hope this helps.

Hanz
http://remotescripts.blogspot.com/ - an introduction to the Framework classes

amounra93
Posts: 432
Joined: Sat Jan 24, 2009 8:16 pm
Location: Arcata, CA
Contact:

Re: how to communicate with control surfaces

Post by amounra93 » Sat Mar 27, 2010 1:32 pm

I named the session component in your script and can browse to the particular function, but I'm getting an "invalid syntax" when I try to make the call. Is there something else you did to get this to work?

EDIT::

Nevermind. I must have mucked about with the script and broken something. I went back to your original script, named te session component, restarted live, and it works now no problems.
http://www.aumhaa.com for Monomod and other m4l goodies.

Muzik 4 Machines
Posts: 769
Joined: Thu Oct 22, 2009 9:35 am

Re: how to communicate with control surfaces

Post by Muzik 4 Machines » Sun Sep 18, 2011 6:13 am

Hanz_Petrov wrote:So here's an example of how to manipulate the "red box" using Max for Live:

Image

In this example, a simple call to the SessionComponent set_offsets method is used to move the box origin to (2,2). Of course, the controller script needs to have instantiated a non-zero SessionComponent to get the red box to show up in the first place.

Hope this helps.

Hanz
i'm trying to build a m4l device that would take a program change, send a note(to call scene) and then set the red rectangle centered at current track with the top row of buttons on my apc being the row of the scene i just called (maybe i can even completely ignore the note thing if the live api allows to select and play scenes)

any guidance you coul give me would make my life so much better :)

julienb
Posts: 1843
Joined: Sat Oct 29, 2005 1:15 pm
Location: France
Contact:

Re: how to communicate with control surfaces

Post by julienb » Sun Sep 18, 2011 6:46 am

Muzik 4 Machines wrote:
Hanz_Petrov wrote:So here's an example of how to manipulate the "red box" using Max for Live:

Image

In this example, a simple call to the SessionComponent set_offsets method is used to move the box origin to (2,2). Of course, the controller script needs to have instantiated a non-zero SessionComponent to get the red box to show up in the first place.

Hope this helps.

Hanz
i'm trying to build a m4l device that would take a program change, send a note(to call scene) and then set the red rectangle centered at current track with the top row of buttons on my apc being the row of the scene i just called (maybe i can even completely ignore the note thing if the live api allows to select and play scenes)

any guidance you coul give me would make my life so much better :)
python script would be an easier way to do that.
Julien Bayle
Art + Teaching/Consulting

Ableton Certified Trainer
Max Certified Trainer


Structure Void / Ableton Certified Training Center

Muzik 4 Machines
Posts: 769
Joined: Thu Oct 22, 2009 9:35 am

Re: how to communicate with control surfaces

Post by Muzik 4 Machines » Sun Sep 18, 2011 7:02 am

arent the python scripts solely for the control surfaces?
are they able to intercept the program change from the ESX on my traveler midi input(along with some genuine controls from my BCF) and use them to control the scene launch and rectangle moves?

i'll dig into that, that's really the only missing link in my whole setup at the moment (well that and the apc40 that will make my 20 becomes a behemoth of an apc80 with the apc64 script)

i have the whole set setup so it takes all 16 tracks at all time, no horizontal scroling ever, but with the 150 r so scene limit in the overview i need a way to navigate my 1000+ scene live set (256 esx pattern taking each a minimum of 5(or 10) scenes for variations/sections so calling the pattern(which is also the drum soundbank) for a scene would play that scene on an 8 bars quantize(ie, change scene at the same time the tribe changes pattern) and bring the apc's grid with the top line being the base pattern and having all my variations for each tracks available, like the MC505 megamix function (

in a perfect world changing pattern on the tribe would move the rectangle and select the scene, but not force play it, so when times come to change pattern i already have the drums sounds of the new pattern in, i can bring every track of the new pattern in turn, replacing tracks from the playing pattern(and having mutes that remains, like the 505, unlike the tribe)) and then unmute the tracks

anyway i'm digressing on my methods which is probably boting the crap out of anybody reading this :lol:

i'll go learn about python and live now

Post Reply