MOD Duo X - Last mile countdown

It just appeared on my desk. I was ready to wait a few weeks more, but here it is - serial number 4, and I am happy as a boy can be.
Let’s see what this beauty can do for me. First impression: this is going to be a lot of fun…

12 Likes

Lookin’ good!!!

1 Like

The Duo X comes with a selection of CV modules to fulfil all of your modular dreams.

is there more info or larger pic?

We will be releasing the CV related plugins in 5 days.

2 Likes

Hallo MOD Jünger,
zunächst einen großen Dank und Respekt für das Zustandekommen des Duo X.
Ich bin neu hier und Besitzer eines MOD Duo X (Seriennummer 006).

Nach Zuhilfenahme des Wiki Troubleshootings bekam ich die Zauberkiste zum laufen, hatte aber leider ständig abstürze in Form von einfrieren und nichts geht mehr, sowohl im Web Bereich, als auch Stand alone. Ich hoffe das sich das mit kommenden Software updates erledigt.

Hat jemand auch bereits ähnliche Erfahrungen?

Viele Grüße aus der Hauptstadt
Doc Slyder

Hello there, welcome to the forum.

Please keep the conversation in English, so everybody can follow along.
(Ich kann ein bisschen Deutsch verstehen, aber nicht anderes leute)

Are you able to describe what is your use of the unit?

We are going to be pushing updates frequently, yes, but I am not confident enough to say they will fix your issues.
Which system/PC do you connect the unit to? (windows, mac, something else?)
The more information we have about the issue, the better chances we have of understanding it and fixing it.

OK, we continue in English and I try to make my problem a bit more concrete.
I have a Windows 10 system and so far I have connected a Döpfer Dark Time / Dark Energy 3 to Input 1 and via Midi In the Duo X gets the desired BPM.
From Output 1 it goes into a Behringer X32 digital mixing console.
The connection works, even the BPM will play correctly and the website I get connection.
But the Duo X freezes regularly and the connection to the website as well.
Even without a connection to the web, the device freezes after a short time.
Only after a restart of the Duo X is it again, but unfortunately not long.
I hope you can do something with it, because I like to help improve the magic box.
Greetings from Doc Slyder

1 Like

Thanks for the feedback. I have some follow up questions.
You are connecting the MIDI from the “Dark Energy 3” into the Duo X, to get MIDI sync going correct?
Are you using the MIDI DIN cable?
Assuming that device can send MIDI over USB, please try that instead of using the MIDI DIN ports.

Also, if you disable sync over MIDI, do things work better in general?

My guess here is that something is going wrong with the MIDI sync mode inside the Duo X.

Hello and thanks for the quick reply.
All my devices (Behringer Model D and Neutron, Arturia Drum Brute, Novation Peak and Bass Station 2, Döpfer Dark Time and Dark Energy 3 and Akai Advace 49 and MPX16) are connected via Midi DIN cable and I would like to keep that.
I will try if the Duo X works better without a DIN cable and will report you.
But I can report back at the weekend at the earliest.
Greetings from Doc Slyder

1 Like

…watching this closely… i don’t yet have my Duo X, but sync via MIDI DIN is important for me as well, for some of the gear i’ll be working with.

1 Like

It is a tricky situation. MIDI sync fluctuates a lot, due to the low resolution of MIDI messages and their timing. Most plugins do not handle well the (tiny) change of BPM every cycle.
But we will do our best to find a working solution.

2 Likes

I am glad to hear that you are looking for a solution and hopefully will find it.
But I’m confident because others have already done so. :wink:

1 Like

MIDI Sync is also important to my planned setup. I currently only use MIDI in using the DIN cable with no problems at all. I had some crashes of the Duo X when I started it, but after changing the pedalboard loaded and playing around with the device for maybe 30 minutes, no cashing anymore. I dod not report it because it never happened again and I do not know how to reproduce or force a crash. I’m keeping my eye on this and will report as soon as I have more info…

3 Likes

So, it looks like the freezing of my Duo X is not due to the synchronization with Midi DIN or Midi USB!
I set the clock source to Internal in the settings and removed all midi cables from the device.
Only input 1 and output 1 are occupied and nevertheless the device freezes after a short time!
It does not matter which bank and which board I call.
Does anyone else have an idea?
Greetings from Doc Slyder

Just got my duo x. Oh Man what a lovely and great engineered device:) thanks for all your hard work!

7 Likes

Might be a specific plugin causing this, did you enable the beta plugins?

In any case, we will be releasing v1.7.1 update early next week, as we already have a few bugfixes.

Almost everything works fine now for about an hour.
Just couldn’t get USB Host Midi to work. Using an Arturia Keystep. Using normal Midi-DIN Cable works perfectly. Looking and dmesg and lsusb nothing seems to be there or mentioned regarding USB -Midi/HID devices. any hints?

cheers max

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