hope you enjoy it
yeah, sample rate is very difficult, this has been discussed before, and its non-trivial - and also you want to keep the axo code optimised. (its not like a PC/Mac, where you can afford to have extra processing code)... that kind of the issue here, we dont have the spare cpu cycles to do the downsample/upsample.
@johannes - totally agree.
I wonder, if it could be an option for 'advanced development', for when your almost using axoloti as a 'bare board' perhaps even just document how it could feasibly be done.. rather than have it in the patcher UI?
e.g what changes are needed to switch? are there changes required to the firmware, and a recompile?
Im thinking a complete hack really, but it could be useful in some cases, like this, where the board is essentially only going to run one custom object....because there will be no CPU left to do anything else anyway
(this is all probably better discussed here)
as I say, doesn't really solve the MI case here, as many might want to combine the objects with other things,
and at the end of the day, Im not trying to create a 'standalone MI elements board' - you can do this by getting a small eurorack case and an MI elements