so very broadly speaking… what I’ve done is
a) add support for Push2 for Norns running on a raspberry PI
Norns has quite a few patches for it, including sequences , samplers and synths.
these can be written in a combination of Lua and Supercollider.
my push support :
- emulates monome display, monome grid (128)
- acts as a midi controller
- has native support for graphics… so you can go beyond the normal norns mono 128x64 display with your own patches.
b) Orac with Push2
I wrote Orac, and it supports Push 2 and midi controllers, can run on a variety of platforms including rPI.
Orac is a kind of virtual modular, that has full midi control,
it includes a variety of modules including sequencers , fx , synths, midifx, utilities.
again, users can create their own modules to use inside Orac - these modules are written in Pure Data.
note: Orac does not currently allow you to really tailor the UI to the push specifically, as its focus was on cross-platform compatibility.
however, this is an area im reconsidering, but not made any firm decisions on.
both Orac and Norns support multiple external midi devices.
Orac probably doesn’t have the conventional sequencer (module) that you are thinking of.
Norns might or if it doesn’t there is no particular reason you could not create one.
in some ways, this is why ive been considering writing other apps for rPI/Push, ones that are a bit more dedicated to a particular task… things like Orac/Norns are very flexible, but sometimes it can be easier to write applications when they are focused, as you don’t have so many other things to take into account … also the UI can be really tailored to doing one thing really well.
that’s why I think @marcustrinyo approach is interesting.