I think physical controllers are over, but I am making a kinect thing, so I am biased :)
We have a "tradition" of things like this, including but not limited to jazzmutant lemur and monome. Thing about this is you can do 1000 things with them, but you want to do thing # 1001. In my project I try and go for as much flexibility as possible while maintaining simplicity.
QuNeo and Kinect mentioned in the same thread. Interesting. The only 2 new interfaces offering unique creative possibilities. Launchpad and the other "me too" examples are glorified typewriters, nothing new, but some players can and do use them in ways that is redefining what an instrument is (cassiel f.e.g.). When remote gesture sensing offers a comparable level of intimate expressive control as an FSR then we will be breaking new ground.
It appears that, in designing for ordinary gesture capability there is a trend towards repetition and imitation. Designing for extraordinary ability generates real innovation: skoog, audiocubes, magicflute. This is a blatant generalization though.
Thanks! Great stuff and super helpful. Drum pads work perfectly. But on the other sliders, qu.parse is only outputting on/off (0/127) and pressure - no information on position. Any chance that could be added?
Beautiful & much appreciated. Only a couple remaining problems:
* The horizontal sliders are in reverse order top to bottom (easy to fix)
* The rotaries always go at the same speed no matter what is actually happening, and thus they end up at a different setting when you lift your finger (don't know if that's fixable)
This fixes the hslider thing. If you want to get positional data from the rotaries, you need to turn "location" on in the quneo editor and forgo the "direction" option. The sliding one way before the other something that quneo does for some reason. I checked with midiparse.
Unfortunately we can't have both direction and position for some reason. Personally I'd rather them function like endless encoders as opposed to knobs. What I wish, and have suggested, is that they'd implement a message to set all this stuff via midi. It would be nice to have different configurations of drum and grid mode pads etc.
Unfortunately we can't have both direction and position for some reason
Sounds like the uncertainty principle at work?
I tried changing the rotaries to "location" in the editor, but I'm not getting location, just constant counter-clockwise movement. Is there a trick to getting location to work? (but I probably agree with you that endless encoders are nicer anyway)
Its all abstractions. open it up and look. qu.parse and the help file are intended to work with the presets I included. You won't get location to work in the helpfile because those widgets are designed to take inc/dec messages. If you change the cc number of location to the same one direction is set to, you'll notice that you get the correct messages anyway.
personally I think more would be overkill for these pads: you will not be able to set values finer than that due to the way the pads and sliders respond: it's not that delicate a control. I find with both the softstep and the Quneo it's great to have the pressure sensitivity but it's hard to control it finely: it's cool to make variations in a parameter but you wouldn't use them to, for example, very finely set a delay time, filter cutoff or position a sound or image.
Audio Matt, Thank you SO much for sharing this. I'm fairly new to MAX and this not only is HUGELY useful in bringing the info in to my patches but also helpful as an educational reference. You seriously ROCK hard.