Buttons on MOD Duo X not always triggering when simultaneously using the rotary knob

Contribute Bug Reports
#1

Description

I have pedal boards in the MOD Duo X with normal effect plugins like e. g. paranoia distortion. I trigger the effect by holding one of the buttons on my MOD Duo X (momentary on) then i adjust a parameter by turning the rotary knob. Often the button press or release is not registered when I am simultaneously turning the knob. So the effect is either not activated when pressing the button or not stopped when releasing the knob.

When I am not turning the knob, the button presses and releases are registered flawlessly.

A similar behaviour shows when using:

  • different effect plugins with different parameters
  • different buttons or rotary knobs
  • “latching” button mode instead of “momentary on”
  • endless encoders instead of rotary knobs
  • when MOD Duo X is not connected via USB

I do not have a MOD Dwarf or MOD Duo. So i can not tell if they show a similar behaviour.

How to reproduce

  1. Create a new pedal board on the MOD Duo X in the web UI.
  2. Add any effect plugin (like paranoia distortion)
  3. Assign a button to the “on/off”-parameter of the effect. Press “Advanced” and select Mode “Momentary On”.
  4. Assign a rotary knob to a parameter (e. g. “Mangle” parameter on the paranoia distortion)
  5. Constantly turn the rotary knob left and right while simultaneously pressing an releasing the button
    → Sometimes the effect is not activated when pressing the button and sometimes the effect stays activated after releasing the button. The LED also indicates that the button has not been pressed or is still pressed after releasing.

Expected/suggested solution

I expect the LED and effect plugin to always enable when pressing and always disable when releasing the button.

Additional information

MOD Duo X

  • release: v1.13.5

  • Operating system: Ubuntu studio

  • System version: 24.04

#2

Hello @indigoM,

I did some testing using a MOD Duo X and Shiroverb:

As you can see, I couln’t reproduce the bug.

Then I went ahead and thought that it was a bug with the paranoia distortion:

Although before recording the video, I had some glitches that made me think that you could be right, then it just went totally normal.

Do you have some more details?

1 Like
#3

Interesting!

Thanks for trying to reproduce the bug.
Sometimes it takes a couple of tries before the problem occurs.

What additional infos would be helpful?

Is there any way for me to gather more intel?
Like debugging/monitoring the incoming button events?

#4

It’s hard yes, but, for example:

  • Do you have some beta plugins in your pedalboard?
  • Is this just a visual glitch, or does it happen with audio?
    (On this, I believe from what you wrote that happens with audio as well)

Last, I suggest you try to downgrade your MOD OS, test it and if it doens’t happen, try to update again and test again.

#5

No, i just realised it even happens with the “new pedalboard” init patch with just the default Gain 2x2 pedal.

So the level parameter is already assigned to the right endless encoder.
I just have to assign a button to the ON/OFF parameter. The more excessive i move the knob to the right and left the less likely the button press seems to be registered. In those cases I even notice the level indicator on the MODs screen to be lagging behind a few seconds.

It happens with audio and visuals both on the mod screen and on the web app.

That’s a good hint. I tried going back to 1.8, 1.9 and 1.10.
On 1.10 the problem is still present.
On 1.8 I could not recreate the problem with the default pedal board.
1.9 does not seem to boot and is stuck in the splash screen.
After going back up to 1.10 or 1.13 the problem is present again.

1 Like
#6

That’s a really weird one.

I would suggest you go to the Dangerous settings of the WebGUI and try to reflash the controller.
Hopefully, that will help. Let me know.

#7

I reflashed the controller successfully.
Unfortunately, nothing changed regarding the buttons.

Any suggestions for debugging?

#8

Not really one that I can think of now.

Is your MOD Duo X LE edition or “normal”?

#9

The version without power switch.
Is that LE?

#10

Yes.

1 Like
#11

Yes.
Anyway, I happened to get access to an LE unit right now. I tested it and I couldn’t replicate the issue.
So that sounds like something related to your device.
Is it possible that you have some hardware damage? Did the device fall or something?
Although that still doens’t sound like the reason.

Have you tried to do a factory reset, etc?
I would do a backup and try to clean everything from the device and check if it fixes the issue.

#12

Thanks, I really appreciate you going the lengths to test it with an LE unit!

Not that I know of. Also it still looks like its in perfect shape

I just did a factory reset and deleted all data but the problem is still present.
I don’t know anyone else with a MOD Duo X (LE). Otherwise I would try to replicate it on their device.

#13

Would you be able to try again to install previous versions?
After the factory reset, maybe the 1.9 would work.

#14

OK, now I can not install 1.8 anymore but 1.9 runs.
Unfortunately the problem still occurs on 1.9. But I feel like it happens a lot less frequent than on 1.13.

Other than that there is no “momentary on” button setting so i can just use “latching” on 1.9.

If there’s really no way to debug on the machine I will try to get my hands on a MOD Duo X (non-LE) and continue experimenting.