Smilzo
Fractal Fanatic
The routine should check the total load of the CPU when the channel is activated; if there is room then activate, else leave bypass on and warn the user.This would be dangerous because you could create a preset that is under the maximum threshold and then when you change the channel you go over the threshold and get audio dropouts.
Thinking about it, more than channel it should be a block bypass feature. If I wish more block in a preset but I don't use all togherer, and I am aware that "loading" the block will take a little bit of time (same as preset change)... than an option in the bypass type could be interesting. The difference with preset change is that only few block could be "unloaded"... for example if I switch between a multitap delay with controller to a hi-quality reverb, but I don't need them on at the same time, and I am at 85% CPU... I don't need two identical preset with just one different block.
Obviously there is audio dropout danger. But if the firmware check the CPU level, and stop the user to activate both block, than there is no audio problem.
The metablock should be a nightmare. I want to know where and what effect are on the grid!