NEED HELP CREATING VU METER WITH LAUNCHPAD
Alright so let me start this off by saying i am a total noob when in comes to M4L.
and before anyone begins to think i should read the tutorials about sending midi out commands to the launchpad please believe me when i tell you I've been at this for about 2 weeks now and I'm pulling my hair out trying to figure this out.
essentially i need the device to read the input from the specified channel and display via the column on the launchpad.
now I realize this is probably a simple design but for the life of me i can't figure it out.
i can get the input from the channel confer the db to a positive number but when i try to route that number to a midi format nothing seems to connect to work.
i also know that within the midi format i have to specify a channel the data etc just completely lost.
PLEASE HELP
thanks
rawkboyz
post patch.
(topic titles in capitals always are a good idea.)
hey sorry for the caps and getting back to you a little late.heres the patch so far. when i send that midi command outside of m4l it activates the light on the launchpad however inside m4l i can't double click on the midi out to even access the launchpad I'm sure I'm either missing a bit of info or something thanks for the speedy response
ironically, I didn't look at your patch, since what you now said seems to imply that you didn't adjust the output of the midi track that device is sitting on in live correctly. Did you configure that track to output to the launchpad?
i got it to work with sending the output of the audio device to an input of the midi device and then out to the launchpad. Must have missed that in the tutorials,however after all this trouble comes to find out that it causes an incredible amount latency trying to run 8 different vu on that launchpad.possibly shed some light on the situation?
on launchpad threads i can't resist. i did exactly this thing for the nocturn led rings recently, but i think it's way more elegant to use the live api to get the values of the input volume meter of the desired track. this way you only need one midi device on a dedicated track set to output to launchpad.
you need to limit the rate of output messages so the launchpad can handle it. if you got the first launchpad model you're even limited to usb1.0 speed.
check [speedlim] [qlim] to limit rate [change] to to avoid unnecessary repetitions. O.
11Olsen is correct in saying that you'd be better served by using the API.
The added bonus is that you don't have to mess around with midi at all, you can communicate directly with the launchpads button grid from a M4L patch (although you must be in user2 mode for it to function properly).
You can use function calls to the button matrix after assigning it to a live.object to light the pads.
And you can observe the Volume of tracks with a live.observer, although it's a tad slow, but with the resolution of a launchpad column being 8, it shouldn't be too big of a deal.