Two Chocolate MIDI foot switch are usable together?

Hi,

I bought one M-Vave Chocolate MIDI foot switch and got another Chocolate PLUS today.
Is it possible for two Chocolate MIDI foot switches to work together on MOD Desktop?

Both are recognized on Manjaro Linux simultaneously, but only one can be configured on MOD Desktop.
I checked the two with midisnoop and found MIDI signals are sent. But MIDI Display plugin on MOD Desktop couldn’t detect only one source. MIDI learn only works on the same source.

I also tested on MOD Dwarf, but the result was the same; only one switch was recognized.

What I have are Chocolate and Chocolate PLUS. Is that the cause of the problem?

I use a cheap USB hub with two Chocolate devices without problem, don’t know about the Chocolate plus.

OK.
Thanks for your information.

@Inqb8tr-jp I have one Chocolate (normal version), I believe that you can change the MIDI channel on the app, eventually, this will help you.

Thank you for your reply.

Everything works on MOD Dwarf, but on MOD Desktop.
The last time I examined the Dwarf, maybe I checked the WebGUI of MOD Desktop.
Sorry.

So MOD Dwarf works fine.
I sshed to the MOD Dwarf and checked the output of cat /proc/asound/cards or lsusb, but there weren’t any difference on my Manjaro’s MOD Desktop.

I hope multi Chocolate foot switches can be available on MOD Desktop.
I pasted the MOD Desktop’s log for your information.

Starting jackd using:
-R -S -n mod-desktop -C ./jack/jack-session-alsamidi.conf -d portaudio -r 48000 -p 128 -d JACK::system
jackdmp 1.9.22
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2023 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
/usr/lib/libjack.so.0 loaded successfully!
Internal client system_midi successfully loaded
Internal client mod-midi-merger successfully loaded
Internal client mod-midi-broadcaster successfully loaded
Internal client mod-host successfully loaded
port_name "system_midi:SINCO MIDI 1 (out)" already exists
port_name "system_midi:SINCO MIDI 1 (in)" already exists
JackPortAudioDriver::Render paOutputUnderflow
JackPortAudioDriver::Render paInputOverflow
JackPortAudioDriver::Render paOutputUnderflow
JackPortAudioDriver::Render paInputOverflow
port_name "system_midi:SINCO MIDI 1 (out)" already exists
port_name "system_midi:SINCO MIDI 1 (in)" already exists
Jack::MidiBufferMixdown - invalid source buffer
port_name "system_midi:SINCO MIDI 1 (out)" already exists
port_name "system_midi:SINCO MIDI 1 (in)" already exists
port_name "system_midi:SINCO MIDI 1 (out)" already exists
port_name "system_midi:SINCO MIDI 1 (in)" already exists
port_name "system_midi:SINCO MIDI 1 (out)" already exists
port_name "system_midi:SINCO MIDI 1 (in)" already exists
port_name "system_midi:SINCO MIDI 1 (out)" already exists
port_name "system_midi:SINCO MIDI 1 (in)" already exists
port_name "system_midi:SINCO MIDI 1 (out)" already exists
port_name "system_midi:SINCO MIDI 1 (in)" already exists
port_name "system_midi:SINCO MIDI 1 (out)" already exists
port_name "system_midi:SINCO MIDI 1 (in)" already exists
port_name "system_midi:SINCO MIDI 1 (out)" already exists
port_name "system_midi:SINCO MIDI 1 (in)" already exists

I could find the setting for multi Chocolate MIDI foot pedals for MOD Desktop on Linux.

The key point is connecting MIDI entries to the midi-in of MOD Desktop on qpwgrach.

I checked “Enable system MIDI” of “MIDI Setting” on MOD Panel, which enables one MIDI foot pedal without qpwgraph’s connection, so I had forgotten the connections.

I appreciate your support.