Could be the “aggregated midi mode” not catching your device somehow…
Connect the MIDI device after the duox boots up, run jack_lsp -c inside the unit and post here the output.
Thanks!
[root@modduox ~]# jack_lsp -c
system:capture_1
mod-peakmeter:in_1
effect_0:In1
system:capture_2
mod-peakmeter:in_2
effect_0:In2
system:playback_1
mod-monitor:out_1
system:playback_2
mod-monitor:out_2
mod-monitor:in_1
effect_0:Out1
mod-monitor:in_2
effect_0:Out2
mod-monitor:out_1
system:playback_1
mod-peakmeter:in_3
mod-monitor:out_2
system:playback_2
mod-peakmeter:in_4
mod-midi-merger:in
ttymidi:MIDI_in
mod-midi-merger:out
mod-host:midi_in
mod-peakmeter:in_1
system:capture_1
mod-peakmeter:in_2
system:capture_2
mod-peakmeter:in_3
mod-monitor:out_1
mod-peakmeter:in_4
mod-monitor:out_2
mod-midi-broadcaster:in
mod-midi-broadcaster:out
ttymidi:MIDI_out
ttymidi:MIDI_in
mod-midi-merger:in
ttymidi:MIDI_out
mod-midi-broadcaster:out
mod-host:midi_in
mod-midi-merger:out
effect_0:In1
system:capture_1
effect_0:In2
system:capture_2
effect_0:Out1
mod-monitor:in_1
effect_0:Out2
mod-monitor:in_2
note: output is the same before/after connect
also red lines a problem?
[ 1.411373] g_ether gadget: DuoX Ethernet, version: DuoX
[ 1.411376] g_ether gadget: g_ether ready
[ 3.058274] g_ether gadget: high-speed config #1: CDC Ethernet (ECM)
[ 4.003808] NOHZ: local_softirq_pending 08
[ 4.003939] NOHZ: local_softirq_pending 08
[ 4.004080] NOHZ: local_softirq_pending 08
[ 4.538580] NOHZ: local_softirq_pending 08
[ 4.788557] NOHZ: local_softirq_pending 08
[ 5.004009] NOHZ: local_softirq_pending 08
[ 5.038687] NOHZ: local_softirq_pending 08
[ 5.205566] NOHZ: local_softirq_pending 08
[ 5.207806] NOHZ: local_softirq_pending 08
[ 5.207854] NOHZ: local_softirq_pending 08
[ 10.898386] random: crng init done
[ 10.898405] random: 7 urandom warning(s) missed due to ratelimiting
no problem there (one warning is regarding the unit having low RNG, but fixable in software, coming later with a kernel update; the other is just a little debug thing)
from the previous output, it seems your midi device is just not recognized at all 
please try out other usb devices and see if something shows up in dmesg, a usb storage drive likely to result in something.
usb in general works so no direct hardware issue:
[ 351.573034] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 351.715129] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 351.715659] scsi host0: usb-storage 1-1:1.0
[ 352.733645] scsi 0:0:0:0: Direct-Access SCSI DISK 1.00 PQ: 0 ANSI: 4
[ 352.734635] sd 0:0:0:0: [sda] 15761504 512-byte logical blocks: (8.07 GB/7.52 GiB)
[ 352.734827] sd 0:0:0:0: [sda] Write Protect is off
[ 352.734832] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[ 352.735022] sd 0:0:0:0: [sda] No Caching mode page found
[ 352.735026] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 352.736916] sda: sda1
[ 352.738407] sd 0:0:0:0: [sda] Attached SCSI removable disk
do you have a linux or osx machine you can connect it to?
if you can provide its usb id (something like 046d:c31c) it would be very useful.
perhaps something needs to be enabled in the kernel… maybe that device is not class-compliant?
Definitely not a beta plugin.
Only what was stored in the device at the time of delivery.
both… trying out some stuff.
whats the max current we can take from that usb host port?
okay found the issue: bad usb (power-only) cable… used a different one and it all works 
2 Likes
good to hear, was already making random ideas of what could be going wrong… 
I see, hopefully with the update next week things will be more stable.
If not, we will figure out something together. I will push the update as soon as possible.
2 Likes
Any news about SPDIF use for the next update?
Can you see a date for enabling the CV in- and output?
1 Like
…i suppose, in theory, that would mean tomorrow…
Yes, we have everything ready, but experienced some bad weather in the cloud… 
Only meta-data missing, but it is quite important as otherwise it is going to get tricky to find the plugins.
Very likely still happens today, depending on which timezone you are on 
1 Like
Current plan is to release software update to handle SPDIF together with CV, so that would be version 1.8.
We started some tests regarding CV, more information about it coming soon, but we need to investigate more so we can have a proper guess at when the 1.8 update is coming out.
3 Likes
Hello, so I’m finally desperate now and have no idea what it could be that my Duo X freezes after a certain, but indefinable, time!
I have installed the last update and now everything excluded, whether cables, sources, midi, etc. It can now really only on the device itself.
Does anyone else have such problems or am I the only one?
Greetings from Düsenton Studio Berlin
are you able to ping or ssh into the device when it hangs?
If someone tells me that this is possible.
However, I’m not sure if I have the right equipment for it.
sorry to hear that, hopefully we can fix this quickly.
I have no clue what is wrong, as this is unusual. I will write a bunch of questions in a PM, but on Monday if that is okay.
That’s alright, I’m not in Berlin for a few days, but I’m trying to answer your questions in between.
Best regards Doc Slyder.
I think I have something similar to your problem, but mine Mod Duo X is rebooting user interface constantly. And the strange thing is that sound isn’t freezing while controls are unresponsive and screen is showing the logo.
1 Like