I would like to share something I’ve been working on the past few weeks: MGCVM.
MGCVM is a collection of modules for making custom performance interfaces for monome grids in Max. It takes advantage of monome’s decoupled design to link performance actions to a variety of visual animations. Apart from securing a static one-on-one relationship between key presses and LED feedback or a visual representation of the applied musical process, MGCVM allows for coupling these animations to the sounds produced by the performer’s actions.
MGCVM is still in an early stage of development so I won’t be sharing it for now (still too many loose ends and limited to 256 VB only at the moment). I plan on increasing the number of visualisations, which for now are composed for my own performance practice. If you have any suggestions … shoot! Light conditions weren’t optimal when shooting the video below so some animations might not be too clear.
That’s very cool.
I have an idea but no clue how possible it would be. That is to have a “create your own visualisation” module. It would allow the user to input (via the grid) what visualisation they wanted to occur and also define which action would trigger the visualisation. Sort of like a step entry sequencer in music terms but for a visualisation.
This is fantastic! Love the idea of a high-level set of modules that allow people to create their own performance / composition systems with decoupled visualization outside of understanding code. Also it seems like a great toolbox for quickly sketching grid interfaces for those (like myself) who spend most of their time on the control / dsp & need an interim interaction solution.
Tx guys! Been working on some other projects the past few months so didn’t develop this any further. I’ll wrap up whatever I have, document it and put it up on Github somewhere next week.
MGVCM is now up on github! Installation instructions etc are in the README file. I only described macOS installation as I don’t have a Windows machine. Perhaps somebody can point Windows users in the right direction …
Some notes:
MGCVM is optimized for 256 variable brightness grids. Some modules will work fine on smaller variable brightness grids, some won’t work at all. Non-variable brightness grids are out of the picture. As tehn already mentioned, perhaps there are some avid monome/max users among you that would like to help develop this toolbox further (f.i. adding nonvaribright support). Let me know if you do.
MGCVM is still in an early stage of development so there will be bugs. I am also well aware that many things can be patched more adequately so if you spot something out of the ordinary, let me know. Please keep in mind that I won’t be able to grant every request or fix every bug right away.
Were there additional runs of the 2012 256 beyond the initial 50? How many varibright 256 grids are out there? Sorry for the tangent, but I’m eager to try this. I guess I’ll find out which parts work with a 128. Thanks for sharing!
@jasonw22 I know there aren’t that many 256 varibrights out there. I initially created this for my own instrument and performance practice but thought it could be interesting to other monomers, so I’m sharing it. Making it available for nonvaribrights is on my list, then smaller grids. For now, most ‘control’ modules will work on smaller grids (the dynamic faders won’t). Some visualisation modules will work too: glitch, hfreeze, vfreeze, loop, pulsegrid, snake, stutter and VU meter … perhaps not optimal but they’ll work.
