Johannes was showing me the G2 system but as he showed, its a bit different for a number of reasons, but in concept quite similar.
(Johannes, rightly isn't cloning the G2, but he does cross-check to ensure Axoloti functionality covers similar grounds)
CC70, we dont want to start 'hardwiring' CC or other midi messages, Axoloti has a lot of different uses, and whilst this might be great for one set of users, it may cause difficulties for others.
(personally Id hate a seemingly random CC doing some behaviour which alters my patch, which I didnt ask for... and I could envisage getting support requests, saying they've connect a controller and every now and then the sound changes unexpectedly... and then finding it was the controller sending CC70 for some reason or another)
I think its much better to provide the tools to be allow this to be possible, and make it explicit.
In axoloti this is now 'trivial'
just create a patch with a midi/in/cc i (70) and link it to the patch/preset object - then save as a AXS, and include in your 'controller object'
looking at the new Organelle, its has an interesting approach, it does respond to things like program change messages to change patches, but it also explicitly allows this to be turned off...
Id be happy with the organelle approach
or the approach we have (with controller objects) where you can just link in functionality you want.. perhaps we should have a 'controller/G2' object which has these 'default midi behaviours' for those that want it.
(probably worth remember the organelle/g2 have a small advantage that it has a display, so its easier to provide feedback, its likely we will do something similar once there is an axoloti remote!)