I seem to have higher CPU averages / overruns on patches where I have all of the IO plugged in on the MetaAIO and Meta Module. Is this expected or could I have something else going on?
Any ideas on how I could test?
Modulation requires computation, as the old saying goes. (Actually I just made that up, but it’s true.)
1 Like
it is a good saying, may I use it?
1 Like
modulating some inputs on a module are more cpu intensive than others.
the best way to test, would be systematically (for modules you are looking at) looking at each input and seeing which yields higher cpu loads.
you could also use internal modulation to check that the cause is really from the MetaAIO compared to modulation generally.
also, whilst I dont have a metaAIO, Ive noticed in similar systems (e.g. Bela), that hardware inputs can sometimes create ‘micro modulations’ , that depending on modulation target can affect cpu load.
simply this is because hardware cv is analog, and can have tiny bits of noise (which some power supplies can be worst for).
that said, this all depends on the dsp code of the module its hitting, and also how much filtering is being applied (metaAIO and modules inputs)
the first tests I mentioned will be helpful to see this is having an impact on certain module inputs.
you could also try taking the metaAIO input into a scope, though to see these micro fluctuations you would likely (hopefully!) have to amplify (digitally) the signal quite a bit.