CC Waveform engine controlling several parameters

Hi all,
This is my first post here.
I’ve been incorporating the MC6mk2 and the Ml5 on my pedal board and I can’t say how good it feels to be able to control so many parameters without tap dancing. Those boxes really opened my possibilities in terms of sound quality.
My question is : is there a way to control different CCs on different channels with only one CC waveform engine ?
I need to control dry/wet of a Source Audio Collider pedal and filter+dry/wet of a Meris Enzo and it only works when I use 3 different engines. I can see in the Midi monitor that whenever I change the Collider control to the same engine as the Enzo, no midi data is sent to the collider channel anymore. Is it a bug ? Or is it mental to be this way ? This is such a powerful tool, it would be annoying if I had to use 3 engines just to fine tune different parts of the same desired effect.
Thanks in advance for the replies !

Each running Waveform engine currently only sends 1 CC waveform. So if you start the same waveform engine with a different CC number/channel, the new settings will override the previous setting.

Hi James,
Thanks for your answer. Would it be unrealistic to hope for more waveform engines in the future, then ? Or is it the maximum that the mc6 can handle ?
Thanks again
Have a good day !

Yes, that is the maximum the MC3,6,8 will handle - 1 engine = 1 running CC message, so there are a total of 4 you can use, which means a max for 4 CC streams running at any one time

Ok. 4 at the same time is plenty. I don’t think I need that, but I do need more than 4 different waveform/range combinations for the live set I’m working on.
Actually, I’m sure I can strip down some sounds to use less engines at the same time with better settings and get a couple engines back for different combinations.
Anyway, so fun to play with all this, it takes time to program, but it’s worth it !!

ah ok got it. we plan to add a new message type that lets you update the Waveform shape and min/max values, so it will override the default waveform setting. Maybe in the next update (not v3.9)


That would be perfect !