max for live

a cassiel.com production
« Back to blog
 

@stretta on the process of designing multiple modular #monome applications in Max for Live

http://stretta.blogspot.com/2009/11/maxforlive-monome-integration.html

As a software engineer I'm convinced by the argument, but also have a strong belief in the unique nature of the creative flow afforded by the muscle memory that is employed when gigging with hardware controllers, and which can easily be lost when the eyes and fingers leave the instrument and interact with the computer.

(Disclaimer: I am the author of several multi-page monome applications.)

Posted November 24, 2009
Nov 24, 2009
stretta said...
I don't see much of a difference between pressing a button on the monome to switch functions and pressing the '1' key on an alphanumeric keyboard to switch functions.

Truth be told, if I could wrap my head around shado, I might be less allergic to the creation of multi-page monome apps.

Anyway, I was trying to make the point that, with maxforlive, function switching can be more user-directed and not application-directed.

Nov 25, 2009
nick rothwell said...
I'm sure it's a personal thing, but, for performance certainly, I'm drawn to solutions which don't require being pulled back to the computer - I'd rather be immersed in the device. If Live can be made to do what's necessary completely by keyboard shortcuts (which it can for your track switching), that definitely helps.

I'm not going to present the shado apps as exemplars of fluid interface design: while shado is pretty clean, the sequencers themselves are somewhat baroque: decorative but not that practical. The next shado efforts will head in the modular, component direction.