Ok. I thought 4 control chain devices where supported, that’s why I bought a second footwitch and I was planninbg to buy a third one (I still have space on my pedalboard 
)
But for the moment it doesn’t work with 1 footwitch 
The Mod team have done a great job. Mod devices are wonderfull but pretty unusuable for a guitarist without a footswitch controller, except for geek guitarists that love tweaking effects on a screen like I do.
But when I’ve build my pedalboard with the web editor and I have exactly what I need I don’t want to need a computer anymore. Just plug and play.
That why control chain footwitch is exactly what a guitarist need with this device, footwitches with screens to have more interaction. Even more with a Mod Duo X that have no footwitches at all.
So for me stability of the control chain devices is the most important.
We understand. RC2 already brought some needed fixes for Control Chain, now we need to see about a few others.
I am a little confused about what actual issues remain.
Since you say.
But for the moment it doesn’t work with 1 footwitch
but before you said
Hi! I have tried a simple pedalboard and just one control chain footswitch and I don’t have the same issue. The problem occurs only with pedalboard I have made with 2 control chain device.
In any case, so far I see:
- CC devices number is not consistent (that is, what is considered foot #1 and foot #2 is random during boot). We have a potential fix for this, pending something we need to do first.
Workaround for now - boot the unit first, connect one footswitch at a time, and then (re)load the pedalboard. - Using 2 CC devices is unreliable, at least with a Duo. This happens more on a Duo than other units, mainly because of its weaker CPU. We have something in the works that will reduce the amount of data sent over the wire for list-type addressings, which will helps this a little. Then we need optimizations on top to try and make it just not happen at all.
Workaround for now - less cpu-intensive pedalboards
For crashes on web gui usage, this is something we actively work on and investigate. I see your pedalboard has some odd data inside, leading to presets not being loaded properly. So it gives me a starting point for fixing a few more things, thanks.
Sorry for the mistake. I said the problem occurs only with pedalboard made with 2 footwitches because I was too enthusiastic. Later I load the pedalboard I made for testing issues with only one control chain footswitch and it had the same issue: led status are not correspoding with footwitch leds.
Concerning the footwitch connection issues I’ve even tried two footwitches with a very light pedalboard that use only 24% CPU and I had the same issue after pressing 10 times footwitches every seconds.
But I just realised that it happens mainly when using the second footswitch of the control chain and it disconnect mainly the first footswitch of the control chain! Can it helps you in your investigations?
Okay, I understand better now. Is this the pedalboard that you shared here?
hmm yes. so might be the issue is not on the Duo side, but on the footswitch.
The pedaboard I shared is the only one pedalboard I use. It’s a big one, too big for the Mod Duo I mean because I must run it at 256 frames buffer size.
I have the same issues with this one but I didn’t use it for testing. I made a very simple pedalboard with 8 plugins, EQs, one comp and big muff, tube screamer and a gate. No wiring.It use only 30% CPU. So I think you can reproduce the issues with any pedalboard you load.
Do you think one of my footswitch can be faulty? I bought one on Mod Device website and the other on Thomann website. I think they are exactly the same one, aren’t they?
Do you think it could be a ethernet cable problem or a power issue or is it a firmware problem?
I dont think it makes a difference.
some little news, I am able to reproduce the footswitch #2 disconnect when foot #1 is used on a Duo X. So for sure this issue in particular is not happening because of lack of CPU.
can also reproduce web gui changes not matching the right footswitch addressings with your pedalboard, very weird!
I’m not alone! 
And pehaps you will see I can’t assign Zacomp preset to Mod Duo knobs… But pehaps it woks with Mod Duo X…
Yes, it works fine on Duo X.
One bug is already fixed - the led/assignment of the footswitch not matching when changed via web gui.
Updated the footswitch firmware to 0.4.1
Do you know how to update those?
Still investigating the other issues.
Great! Yes I know how to update footswitch. I’m going to try this new firmware.
Thanks!
So I’ve tested the 0.4.1 firmware. Now the led in the web editor and led footwitches are matching when I change the effect state in the web editor. 
But led state are still not matching when loading a snapshot.
Hello! Now every time when DuoX starts, I have really loud digital noise. It appears when my volume is +12 on the stereo gain plugin (at 0 still present) With RC1 it was fine with these settings. And now I’m not able to roll back, my DuoX not recognizing RC1 file. Just in searching file mode forever. And CV parameter mod output sometimes not showing in the drop out menu in CV assignment, need to click a couple of times.
PS: I know that +12 is a lot, but the crux in the really huge amount of noise. Way more than before)
This is +12 photo_2021-03-16_23-40-09|690x363
This is 0 photo_2021-03-16_23-40-29|690x366
Low frequencies are pulsating, high is constant.
UPD:
Looks like on boot up system gain somehow set to maximum, even if I have +12 and then rotate +- 1 back-forward sound like +12 is much quieter than it was on the boot.
UPD2: After i re-saved DEFAULT pedalboard, this problem disappeared.
Now i somehow have fixed everything.
Just wanted to confirm that the update fixed the caching issues that led to visual glitches with Firefox 78 ESR. Thanks!
I have found new bug. When on tablet I’m able to change anything except on/off. Tried different browsers.
Thanks for reporting! And for the video! It makes it easier to see the problem.
Can you tell us the model of the tablet you are using, the software version, and the browser?
Huawei MatePad 10.4
MDX connected via OpenWrt router. Didn’t changed anything, just updated to 1.10rc2. Before update worked smoothly.
Android 10 / EMUI 10.1.0
Tested with latest vertions:
Opera, Chrome.
Also tested with my phone. Same problem.
Android 9
Chrome
Something that went unnoticed until now.
This touch-mode navigation is not officially supported, one day we need to go through the possible actions and make it generally better…
For now I added something that makes this work again, tested in a setup similar to yours.
Coming in RC3 later today