Thanks for answering, my English is from Google’s translator. Sorry
Let’s see if I explain myself.
I connect my M-Audio keystation Mini 32 to the USB port of the Mod Duo X, select, in Banks a pedalboard Synth, for example Synth Acid, and I have no sound.
In System, Pedalboard Nav Midi CHN I have selected all the channels and I have no sound
Curent Pedalboard only shows Save State and Reset State.
But if I connect the 2 MIDI ports of the Mod, to the 2 MIDI ports of the RME sound card, and the M-audio to a USB port of the PC, configuring the Mod as an external instrument in a Daw, it works fine, I can even pedal new on the Mod Devices website.
In short, my controller keyboard (which does not produce sounds) is active connected to the midi out and midi in ports of the Mod. Connected to the USB port, it does not work.
To see if everything was working properly, today I tried to connect a M-Audio air Mini 32 to my DuoX.
Sadly it did not work either, which is odd because it does work fine with the MOD Duo.
Probability there is something going wrong with the DuoX in combination with these specific keyboards (might be some drivers).
We will investigate things further and address this in a future update soon!
Hello
I am going to buy a new midi controller keyboard. I like Arturia KeyStep, but I can buy another one tested in Mod X.
What midi controller keyboard have you tried working on Mod X?
The nice thing about the Keystep though is that it has DIN-MIDI as well, which will work (and in the future with the CV’s too ). Since its working on the MOD Duo it should be able to get working with the MOD DuoX as well, again its most likely a driver issue (luckily there is @falkTX performing his Linux magic we will be addressing this soon! ).
oh, then it might be that the Keystep does not fall under this ‘Arturia DuoX bug’, good to know!
Since we do not have one here to test I did not want to make any promises we can’t keep
Late to the show… Just testing an M-Audio Axiom mini Air 32 via USB to my Mod Duo X and it does not work.
Was having a browse at the shell (not novice to linux), but couldn’t find an lspci -v to check the kernel detects it… did execute an lsusb before and after connecting it… sees the hub, not the Keyboard it seems… I can see this is a minimal linux built on busybox… just curious about the dev tools available here
PS: where is the main log for checking these type of things at shell level?
I got myself an m-audio keyboard just to be able to test this, and I can reproduce the issue.
Tried a couple of things, but nothing that made a difference.
Will continue investigating…
I have the smallest akai mpk keyboard that also does not seem to work. My thoughts were that it was because it needs to be powered via usb and maybe the mod duo can’t do that? I’m talking about the Duo not the Duo X though, sorry.
I investigated a bit, but it is a lot more tricky than I was expecting.
It is an incompatibility with some devices when “downgraded” from usb3 to usb2 (at least that is my theory).
The m-audio keyboard I have here which does not work on the Duo X right now, also does not work on the PC USB3 front ports, but it works on the ones in the back… (it works on any usb2 port too)
The Duo X usb host is internally a usb3-capable driver, but since we only need usb2 we do not enable usb3 related stuff.
The curious thing is that the error message printed by the Linux kernel on both my main PC and the Duo X is very similar, leading me to think the issue might be the same
Anyway, this is all too technical probably.
We will keep trying. Sadly some USB MIDI devices do not work just yet, sorry about that.
Testing Mod Duo X with midi controllers. So far tried Sonicwave ELZ_1, Teenage engineering OPZ and OP1. Managed to make software synth work only with OP1 so far and not always. Needs a lot of plug-out-in to make it work. using Separated mode on Mod duo X and checking OP 1. Would love to make it work on other controllers/sequences.
Has anyone able to figure out what’s the problem?
I got the same issue with my M-Audio keyboard with my own desktop PC on certain USB ports.
There was a combination of USB-2 port and cable that finally made it work, but very very odd.
M-Audio devices do not seem to like to be connected to USB-3 ports.
From my investigation, it seems an hardware issue on their side. Lots of other people seem to have other very similar issues, usually involving USB-3 ports.
The Duo X (first model) uses a USB-3 port that has its USB-2 pins exposed, thus working in USB-2 compatibility mode. This seems to cause the issue for M-Audio stuff. I was not able to find any workaround so far. There might be a kernel-side “quirk” possible for them, but the ones I have tried did not resolve the situation, sadly.
Not saying it is the case for other devices, but could be related.
It is worth trying a usb2-hub and different cables.
Nice, thanks for the tip. USB2 hub did the trick. OPZ and OP1 work like a charm now upon every try.
Sonicware ELZ1 does not but I tried and it seems it’s the problem with the device itself, as it doesn’t work with computer DAW either.
). Since its working on the MOD Duo it should be able to get working with the MOD DuoX as well, again its most likely a driver issue (luckily there is 
we will be addressing this soon! ).