64 i/o availability? (accel/piezo velocity?) (case modification?!?)

  • In looking at this thread (http://post.monome.org/comments.php?DiscussionID=8490) it looks like the kite versions have 8 digital pins available as well as 8 analog pins. Is that the case for the 64 as well?

    Do you need to go into the firmware for this or is it just available through serialosc like everything else?


    Has anyone (gasp) modified their monome to add a function button? or any additional buttons? (or anything else really)
    I'm planning on building my UIs so that one row is less important and I can use the button release as the event trigger, to be able to use that row as function type buttons.

    Lastly, in terms of velocity/gesture type data. I saw this thread here (http://post.monome.org/comments.php?DiscussionID=8448) which talks about using the accelerometer to get velocity data (like in the iPad). Seems like a great idea but apparently the latency on the accel data isn't great. It also makes it useless for attack-based modifications. It could however add some info for modulation/volume (post-attack) based parameters.

    I was thinking the other day if it would be possible to use some piezos mounted across the inside of the unit. Say 4 evenly spaced ones (not at the corners, but a bit in (so kind of in the center of each 4x4 grid). That perhaps taking the data out of that and running it into the ADC (with some filtering/rectifying) could yield some faux-velocity data.
    In the bit of messing around I've done with piezos and Arduinos, I've never noticed any latency.
    It wouldn't/couldn't give you 'per button' velocity, but it could give you some ballpark data to chew on. Maybe with some triangulation it could even tell which quadrant you're in?

    Has anyone messed with or thought about using piezos to sense velocity? Or even piezos + accell data combined/interpolated?

    In general I don't think 'per button' velocity is terribly important, but it would be nice to have an overall 'umph' factor that can control certain parameters (say something as simple as a slight volume boost or velocity layer switch for a sample, or effecting envelope data for synth stuff).

    So yeah, any hotrodded monomes out there?

  • In thinking about it further I thought that the piezos could act as pressure sensors generating some 'aftertouch' type data too.

    I own a few ciat-lonbarde instruments that use piezos as pressure sensors. This is one of them (http://www.ciat-lonbarde.net/sidrassi/index.html). It has regular piezos under metal (or wooden) bars and it gets some very subtle pressure sensing. Mind you it's a single contact mic on a pretty thick metal bar. There's no appreciable movement/flexing on the bar itself. I would imagine the PCB inside a monome would have equal to or greater flexing.

  • wouldn't making use of those extra pins require some new firmware juju? sounds awkward.

    maybe you could create some kind of pressure sensitve "mat" to place under your monome?

    http://www.instructables.com/id/Pressure-Sensor-Matrix/

    http://www.ladyada.net/make/midisense/forcesensors.html

    if you were in the max world, maybe you could poll the pressure senstive mat everytime a button press was detected and attach that pressure data as velocity to whatever you want?

    i imagine the next monome device will be some kind of pressure sensitive device, like the soundplane. maybe. well, it makes sense, to me at least. buttons, knobs, PRESSURE. evolution :)

    this could be worth a look too:

    http://docs.monome.org/doku.php?id=modification:40h_optical_howto&s[]=encoder

  • this is theoretically possible, but will definitely require a lot of firmware tuning.

    firmwares here: https://github.com/tehn/mk

  • working on tilt/encoder/etc mk tutorials now, will be ready soon...

  • I was wondering that about the firmware. It seems like there are available pins for aux i/o on the kit version at least. I would assume the firmware accounts for them already? Don't know and couldn't find info on that on the webpage.

    Having a whole other device would add all sorts of guff. It would be super elegant if it was all internal.

    I came across a couple of posts where tehn was talking about how velocity was technically unlikely though I don't know how old that sentiment was.
    I think that would be great having velocity and/or pressure for each pad, but without sacrificing the binary/button based paradigm. Which is why I was thinking a quadrant or global bit of data to augment the buttons would allow for sufficient gestural control, particularly for such a small area.

  • Do you have to tweak the firmware to use internal tilt/aux inputs?

    Looking forward to the tutorials.

  • i have the tilt/enc firmware written, they use the aux ports. i haven't finished the tutorials yet. you don't have to tweak the firmware yourself, just flash the .hex file to your chip.

    the default firmware makes no use of the aux pins, so that firmware can be easily extended for custom applications.