Forums > MaxMSP

[sharing is good for the community] – a midilearn for multislider

June 25, 2010 | 9:37 am

Maybe this patch could be useful for someone.
Comments an improvements are welcome.

– Pasted Max Patch, click to expand. –

matteo

———-
matteopennese.com


June 25, 2010 | 9:42 am

couldn’t it be simpler – move a slider -> means midilearn if next received midi thing isn’t learnt yet. this saves you clicking the midilearn button and the less you have to click the quicker you go.


June 28, 2010 | 6:05 am

this should work too, bare-bones:

– Pasted Max Patch, click to expand. –

June 28, 2010 | 9:43 am

Here’s another midi learn method; to use it with multislider, just use a tab object with as many tabs as you have sliders……….

This requires only 2 clicks no matter how many interface elements you want to learn.

- edit – tab doesn’t support vertically lengthened tabs :( you would have to use multiple tab objects…..

– Pasted Max Patch, click to expand. –

June 28, 2010 | 3:20 pm

Also, if you named all your UI objects you want to learn and control, you could use [hover] with a big [route] afterwards (all the scripting names in it), and assign them all with only one initial click that puts it in learn mode. Not sure which would be cleaner patch-wise… :)


June 28, 2010 | 4:32 pm

Yeah, the reason I prefer the tab way is because it gives me a visual mouse-over indication and a label of what midi controller number is mapped to something all at once :P


Viewing 6 posts - 1 through 6 (of 6 total)