Jonas Barsten

I'm turning on the device activator of device nr10 in track 1 in ableton using the lower part of this patch.

As you see, it reacts and works just like I want it to when I use the "int" and "toggle"-objects connected to it, even when I change the "int" following "live.observer" in the "p device".

But it doesn't react when I trig the message boxes connected to the "set value $1" message in "p devices", all the connected objects react (toggle and int), but it doesn't send the parameter value to the device (nr10) in live.

Beats me. Makes Max crash whenever I click one of those message boxes, which really interferes with my ability to troubleshoot. I can't see anything obviously wrong, though that doesn't mean there's not. But it looks correct as far as my uncrashed computer lets me see.

On the other hand, I have no idea what you're doing with those [counter 0 1] [route] [counter 0 1] [route] groupings. Does that do something I don't know about or have you lost your mind? :)

Request: descriptive titles for posts in the future, please.

Beats me.  Makes Max crash whenever I click one of those message boxes, which really interferes with my ability to troubleshoot.  I can't see anything obviously wrong, though that doesn't mean there's not.  But it looks correct as far as my uncrashed computer lets me see.

On the other hand, I have no idea what you're doing with those [counter 0 1] [route] [counter 0 1] [route] groupings.  Does that do something I don't know about or have you lost your mind?  :)

I'm really sorry regarding the un-descriptive title of my post, as a poor explanation, those where the only three letters left in my head after several hours of troubleshooting, and english isn't event my mother-tongue.

Well, as you might have noticed from my other posts I'm quite new and autodidact when it comes to max, but I really wanted to make this patch, so I had to use the objects I know, I'm totally sure there are other ways of doing it, but the counter/route-groupings are because the midi-signal sent to the patch sends a bang @ press and a bang @ release, I just want one of the signals ... I could have used toggle, do you have other solutions or am I missing something?

I "solved" the problem by sending the message boxes straight trough, with no connection to the "observer".

Changes made in Live related to this patch won't be reflected by the LEDs on my midi controller (launchpad), but sending a "1" to the device activator, will also turn the LED on ... it isn't optimal, but it work ... hopefully also at my gig tomorrow :P

What kind of midi message does the launchpad send? Is it by note-on and note-off, or two note-ons, or what? Do you know?

What kind of midi message does the launchpad send?  Is it by note-on and note-off, or two note-ons, or what?  Do you know?


I had a quick look at the patcher. I'm not sure what it is supposed to do. The 'p device' has three route elements without arguments. The reference states: 'The route object takes a message and tries to match its first argument to the route object's own arguments. The rightmost outlet passes any message that matched no other choice, so you may gang route objects to get more choices.' I suppose it really needs at least 1 argument to do something for you. I think all three should be 'route 0', where input 0 will trigger the left outlet and anything else the right one.

@nneuromulator, the Launchpad indeed sends note messages with information about which button in the matrix and on the right is pressed and there are separate messages for button-down and button-up. Pressing buttons at the top is sent as CC messages, also signalling down and up movements.

By the way, I've written a wrapper for the Launchpad interface, it is at

http://www.maxforlive.com/library/device.php?id=298

I had a quick look at the patcher. I'm not sure what it is supposed to do. The 'p device' has three route elements without arguments. The reference states: 'The route object takes a message and tries to match its first argument to the route object's own arguments. The rightmost outlet passes any message that matched no other choice, so you may gang route objects to get more choices.' I suppose it really needs at least 1 argument to do something for you. I think all three should be 'route 0', where input 0 will trigger the left outlet and anything else the right one. 

@nneuromulator, the Launchpad indeed sends note messages with information about which button in the matrix and on the right is pressed and there are separate messages for button-down and button-up. Pressing buttons at the top is sent as CC messages, also signalling down and up movements. 

By the way, I've written a wrapper for the Launchpad interface, it is athttp://www.maxforlive.com/library/device.php?id=298.


Just to clarify, arguments in route are optional.

"If there is no argument, there is one other outlet, which is assigned the number 0."

Just to clarify, arguments in route are optional. 

"If there is no argument, there is one other outlet, which is assigned the number 0."


So 'route' on itself is the same as 'route 0'.

wtf?