MOD Duo X - Last mile countdown

To keep up the progress report…
Final steps are happening right now.

I am (literally right now :stuck_out_tongue:) preparing the “factory image” we use when shipping new devices, as a semi-automated process that anyone in our team can easily follow.
For the Duo, things were easier using the Allwinner “FEL” mode, it allowed us to write directly to the internal storage.
On the Duo X it is not so simple, it is now a procedure of 2-steps. First we flash the bootloader, and only then we can write the entire OS image.
Nothing we cannot handle, of course :slight_smile:

Something that happens after the initial OS deploy is a hardware test.
We start the unit in a special test mode, which then we use to ensure the hardware is working fully (control chain, usb, midi din, knobs, buttons, leds, etc)
We are finishing the last details to make sure we can test the units before they are shipped. (and ensure it all works)

Our current goal is to finish all remaining “initial release tasks” this week, so we can begin shipping next week.
We invited a musician to our offices next Monday, so he will be doing a final stress-test of the unit.
So yeah, our goal is to ship middle to late next week. :sunglasses:

9 Likes

beauty… thanks for the update, @falkTX!

curious: does the shipping image include the ability to sync to incoming MIDI clock, or is that for a later update?

3 Likes

that is present in the initial release.

the things that we are skipping in this initial shipping are:

  1. spdif output
  2. cv in/out (plus expression pedal mode)
  3. midi clock output position (it will send start, stop, continue but not current position)
2 Likes

Are these things you can promise to be fixed soon? (=this year)

we will surely try.
spdif should not be hard, the important parts are already in place, it is more of enabling the right things in the system.
CV is being worked on.
for midi clock output position I am not fully aware of what the issues are, likely just needs better jitter correction.

3 Likes

Great news! I can almost hear the thud of my shiny new X on the doormat :slight_smile:

Having worked in embedded product dev I know the issues and feel you are approaching it right!

@eggsperde @unbracketed @plutek

I believe this post answer your question about licensing that we were discussing earlier in this thread:

2 Likes

a sneak peek… since this is an internal thing, you don’t see it often… (or at all!)

11 Likes

oh… hello, dear! :heart_eyes:

1 Like

Woo!

1 Like

So exciting!!

2 Likes

This looks very good. I hope the delivery will happen quickly. I already have sweaty fingers;-)

4 Likes

Good to see you in the group!

2 Likes

For the nerdy ones, here’s something else you also don’t see everyday (or ever…).
This is a graphical representation of what is really happening inside the Duo X with a somewhat simple pedalboard loaded:

Each one of those boxes is an (internal) jack client, the “effect_*” ones being the plugins.
Blue is for audio connections, red for MIDI.
So yeah, there are a few things happening behind the scenes that you just do not usually see :slight_smile:

PS: for the even nerdier ones, those that might recognize that canvas - yes, that is carla running in the Duo X, controlled remotely over OSC. More on that sometime later. :wink:

10 Likes

Getting so excited for this!

1 Like

I’d like to learn more about OSC :slight_smile:

EDIT : a bit of search got me to your lovely KXStudio page

https://kx.studio/Applications:Carla

Yeahh ! I never arrived to work with carla-control, but I think I will have to if it also works in Mod Duo (without X)!

@falkTX thanks for the inside tech infos…

so as an example mod-peakmeter basically just drives the output leds via gpio pwm?

correct. you can even get the source for it here https://github.com/moddevices/mod-peakmeter :slight_smile:

2 Likes

ahh nice and logical, so the board uses an i2c pwm expander for peripherials (PCA9685)

sweet