Roald Baudoux

One has to switch the audio off then back on to have the MC object's number of channels updated. Is it the expected situation? Could it be updated immediately without this off/on cycle?

One has to switch the audio off then back on to have  the MC object's number of channels updated. Is it the expected situation? Could it be updated immediately without this off/on cycle?

One has to switch the audio off then back on to have  the MC object's number of channels updated. Is it the expected situation? Could it be 

mc-number-of-channels-updates-only-upon-audio-restart-is-it-normal

Bump. Running into the same issue. Is this expected behavior that the number of channels can't be dynamically changed or a bug?

According to further reading in the documentation, it appears to be the normal situation. Maybe one could create the maximum possible number of channels and send a zero signal to unused ones according to the situation, but it doesn't seem to be a very CPU-efficient way of working.

Yes this is normal. The maximum number of channels is 1024 and on my laptop uses about 23-25% CPU, so yeah gotta make some decisions about how many channels you want.

Take a look at the [mc.voiceallocator~] and [mc.noteallocator~] and their use of busy maps to turn voices on and off to save some dsp, if you do use a larger number than you really need "just in case."

Objects with @chans 0 will also accept the number of channels running to them, so you could use that to your advantage when your patch gets complicated and you wanna change the number of channels.

MC number of channels updates only upon audio restart. Is it normal?