it is fair to say that this is more interesting for teletype users than er-301 (although judging by a lot of familiar usernames here there is quite a bit of overlap!), particularly because integrating monome grid with teletype is a new thing, so any examples of its practical applications are exciting.
i do want to elaborate a bit more though on what makes it so exciting (and working on grid integrations perhaps the most important part of this work for me is thinking of what is possible with this integration and how far we can push it, and mlr is a really good example of that). apologies for some shameless generalizations that are about to follow.
if er-301 is a “sound computer”, then teletype could be described as an “event computer”. er-301 allows you to create custom sound “modules” where you decide how it produces sound and how it can be modulated. similarly, you can design a custom sequencer with teletype where you decide how it steps through a sequence and what aspects of it can be controlled / modulated (or how about a sequencer that treats a concept of sequence like something that can be changed with control voltage).
teletype is similar to er-301 in that it only has one knob though, so that’s where grid integration comes in handy. and because it’s scriptable as well what this means is that you can build your own custom grid UI, which is tailored to your sequencer. or you could have a UI that changes dynamically as your patch unfolds.
basically, with a er-301/teletype/grid combo you can build a custom sound module, with a custom sequencer and a custom controller. and since teletype can store scenes (internally and on a USB stick) you could have the above mlr style patch, and with a simple recall you could turn it into a 6 track drum machine with mutes and an x/y pad:
or take that and add another 2 CV sequencers:
