Expert Sleepers Disting EX

try using SC.CV.SET instead (it doesn’t use slew unlike SC.CV, my guess is that’s what faderbank sends)


Ah! That’s the ticket. You also have to add 1 to the ID number.

E.g. if ID #8 is mapped to Mix_1->1, you have to SC.CV.SET 9 x

1 Like

yep, the ops are 1-based, so they subtract 1

1 Like

Good to get it working. :slight_smile:

As far as value scale goes: the default matrix mixer range is -200% to +200%.

0 = -200%
4096 = -100%
8192 = 0%
12288 = 100%
16384 = 200%

1 Like

envious! still waiting for the 2 i’ve ordered, can’t wait to try them with teletype.

I did wind up buying a desk-mounted magnifying glass on eBay.

Mappings only apply to the single-mode algorithms. But since the dual-mode algorithms have much more limited parameters, that seems like an OK limitation.


Working on a basic TouchOSC iPad control surface for Distings via midi. Works ok with Mk 4. Needs my EX to arrive before I can finalise everything


Found this rather impressive.


And the mention in the comments that he has 6 channel wav recording working too… What a fantastic module!

1 Like

My EX finally came in yesterday, loaded up a stack of Mellotron samples into the multisample player… using two cv/gate pairs sequenced by crow into a rossum evolution ladder filter… pretty hard to imagine this getting old. Quite excited about i2c integration. Choosing the sample folder with the encoders is super touchy, but if I could shoot it a teletype command to switch folders that would be nice.


Here’s a little marbles sequencing the Disting EX piano and later Pluck:


Hey there – trying to get a newly arrived faderbank working with the disting ex via I2C. I set up the 16n as leader. Connected a trs midi cable to the disting and the faderbank. Disting doesn’t seem to be getting any messages though. The I2C history on the disting is just pairs of zeros. Am I missing something obvious here? How else can I test? Non-I2C function via CV worked great.

Thanks in advance.

check if you have i2c pullups enabled either on faderbank or the disting (should only be enabled on either one, not both), and check which i2c address the disting is using.

I am also having trouble with this if anyone could help?

Connected Disting to TXb like this:

I left Disting EX with default settings (i2c address - 49 0x31) and Pull ups off.

With 16n - Pull ups set on and set to leader in config tool.

I don’t see anything in the i2c history on Disting.

I tried both a standard audio TRS cable and a TRS AxB cable I assume it is wrong cable but have no idea - not played with i2c before.

The trs midi and i2c ports are different ports!

The CV functionality just sort of works as long as there is power coming in to the 16n and there are no problems with the physical build. The i2c and midi rely on the teensy being flashed with the firmware correctly. Good news is there is a web midi test and configuration device. 16n Firmware 2.0.1: release and official thread Being able to verify that the midi over usb is working means that there is functional firmware on the teensy.

You will need something like a txb or a simpler i2c trs cable will have to be broken out to a 3 pin jumper. The orientation of the wires is also important (though if it’s wrong it just won’t work, it’s not a red stripe in the wrong place let the magic smoke out kind of problem).

The trs to 3 pin jumper is something that can be soldered together fairly easily if you have the parts sitting around the house and should look a bit like this:

1 Like

I have that exact cable put together by Michigan Synth Works.

Maybe I missed this elsewhere, but I found that the I2C address for the 16n is 0x34 (per the firmware repo) so made that change in the disting MIDI/I2C set settings (I2C Address 52 0x34). (EDIT: This is bad info per desolationjones instruction)

I thought this discovery combined with the right combination of pull up switches would get me there. Not quite. Still zeros in history.

I did connect to the editor and confirmed midi works as well. So, the unit is A-OK, just something not connecting yet on I2C.

@lisles You’ll want to change the disting address back to 0x31. That’s the target follower address for a 16n. Make sure you are using the i2c Jack on your 16n and not the midi Jack.

@dangriffiths the TXb has pull ups if you connect it to power, so you should disable pullups on both other devices. Doubling up on pull ups shouldn’t cause no i2c signal though…


hm., ok, I switched back to 0X31. The trs is jacked into the one nearest USB/Teensy. Pretty sure this is right. I think I’ll go mow the lawn or something and come back to this later.


Thanks so much. It was actually stopping the signal - turned pull ups off on the 16n and messages are coming through to Disting now. Now the work out the rest of it haha


Mowed the lawn and took a fresh look at this. During a round of unplugs and plug back ins, I mixed up the GND, SCA, SCL orientation on the back of the Disting.

I’m in business now after a rebooting both the disting and the 16n.

Combination working for me now:

  • Disting I2C Address: 0X31 (defaults on both side)
  • Pull Up on Disting
  • Pull Up off on 16n
  • and of course the correct pins plugged in.

Thanks @desolationjones and @scanner_darkly.

Now should I go back to working in the yard on beautiful day or fall into a lovely hole of sound? Hard decision!