Ahoy - I can’t give a full appraisal of the idea, but I would recommend mesh as a good starting point. The interface to record / playback is obviously grid oriented, but the actual source and destinations are just generic OSC messages – indeed you can use it to capture arc messages just as easily as grid. This dumb behaviour makes it at once immediate but also frustrating in terms of hung notes and such things. This always seems to be the curse of building software that is too flexible, rather than tightly configured to a particular device.
That being said, mesh could easily be expanded to achieve your goals. One difficult issue is that you generally need to run the looper in series with your OSC signal flow. If you try and run it in parallel I think it creates a conflict when trying to create two OSC hosts looking at the same port (ie. you can’t). This of course is frustrating when you just want to use your device directly without the looper (having to change ports). Again, the process is quite fluid with the monome due to the dynamic port generation of serialosc, but I have a feeling soundplane doesn’t follow this metaphor, and would require manual editing when switching.
Anyway. Cool idea! I’d love to see that bunch of code extended to meet other’s needs. Also not that the sequencer data was just time stamped events in a list, so should be easy enough to dump into a text file for saving.