Here is the patch from the tutorial...
max4live.info tutorial: In Control: (Launchpad Edition) - Sending Values
Remember, You must be a registered user to see the file.
max4live.info tutorial: In Control: (Launchpad Edition) - Sending Values Patch
Mon, 11/30/2009 - 17:19
#1
max4live.info tutorial: In Control: (Launchpad Edition) - Sending Values Patch
Sun, 12/13/2009 - 14:17
#2
Hey Mike,
I wanted to ask about the "call send_value" function in the tutorial patch. I tried to recreate the patch and was getting errors with the syntax - downloaded the tutorial and it works fine. I did an output to see if I could figure out what it was outputting, and its just passing that exact message down to live.object (so your setting something, and I take it, the path/ID tells it what to set). So why couldn't you just pass the numbers down to the left inlet of the live.object?
Sorry, just want to understand the "call send_value" a bit better - thanks Mike!
Mon, 12/14/2009 - 22:23
#4
Thanks Mike.
I guess what I'm asking for is an explanation "call send_value" function? I understand the other functions of the patch, I just can't find anything on "call send_value", and why you need to preface the numbers (x, y, colour) with it. I take it the live.object is looking for specific syntax, hence why you can't just send the x, y and colour info.
So, you invoke the "call send_value 0 0 1" to light up the first button on the button matrix. Why can't I just send "0 0 1" to the live.object since the ID has already been passed to it. So either live.object is expecting to see something prefacing the button info in order to understand it, or "call send_value" is formatting the info in some way for live.object?
Sorry, totally new to max programming and haven't really done any programming for years. So just trying to hit the ground running here. Thanks again, and hope I've explained myself a bit clearer this time!
Tue, 12/15/2009 - 07:50
#5
@Ypsi Kid
It can be kind of confusing because it really doesn't correspond to some other things in the Live API. The actual, "call send_value" is different depending on what object you are using with the, "live.object".
for the Button_Matrix: call send_value syntax is, "call send_value x y midinote"
fot any other button: call send value syntax is, "call send_value midinote"
The midinote in the button matrix refers to the color you want to light the button with. There are 3 colors you can choose from and a few different intensities. You can find out the colors from the Launchpad Programmers Guide available on Novation's site. In the case of the Nomepad Monome emulator, i chose to use midi note 60 which is green and then midi note 12 which turns off the light.
The problem is that you are going to need to know what the manufacturer is expecting in order to send the value to a device. Luckily, novation has provided that information for you. This format for sending sending values is the same for the APC40 and the Launchpad. The only thing that will change on the APC40 is the midi note that it is expecting.
Mike
Wed, 12/16/2009 - 11:03
#6
Thanks Mike, that was exactly what I was looking for. Makes a whole lot more sense now.
Appreciate the quick reply, cheers!
Fri, 01/01/2010 - 14:40
#7
Can someone make the LEDs flash?
I can't.
I have tried with all the values using a integer box to the set color midi value to the call send_value... message box. I can acces all different brighteness of all the colors, but not the flashing mode.
Any idea?
Sun, 08/22/2010 - 02:37
#8
Hi Mike,
thanks for all your tutorials, they've been a great help.
I'm working on a patch at the moment where i want to light up buttons in the button matrix while in user 1/drum rack mode. They seem to be addressed differently to the other modes... ie if you you "call send_value 0 0 60" it lights up the bottom left button and if you "call send_value 0 1 60" it still lights up the bottom left button.
help?
thanks.
If you are asking why i populate a message before sending the value to the Live object... The reason has to do with the fact that i want to make sure it is in user2 mode before i start monitoring the button matrix. So, when User 2 is pressed. Where the, "select 2" is. That sends the ID to monitor the button matrix to the live.observer and live.object (receiving values and sending values).
Mike