#17

Busy times! Got a few projects on the go at the moment.

I have moved the breadboard onto a bit of stripboard hanging off the back of teletype, and it didnt work at first. I shelved it because we’ve had far too hot weather for solder in australia. But today I fixed it up!

So now its no longer in a test case with breadboard hanging off, but in my main case, controlling a malekko quad LFO+ENV, and 2 Disting Mk4s. Im planning on testing it in a musical setting for a while and working out what other ops might be useful. I started laying out a PCB as well, Ill try and finish that off mid-Jan

EDIT: Also I have the expert sleepers select bus MIDI breakout, so ill be able to test sequencing of external gear. i probably wont use it all that much, except for sending tempo info and control changes to external FX pedals

6 Likes
#18

This is hugely exciting to me. Great work and keep us posted.

#19

Been thinking further about this. My interest stems from the fact that i have a whole host of mungo modules that use the select bus protocol to save states, the thought of being able to switch through states using Teletype, while simultaneously switching patterns etc on my monome (earthsea/whitewhale/ansible) and mannequins (w/ just friends) modules is just amazing.

So to my question… i have more modules (that would benefit from being on the same bus) than i do skiff space. I’ve thought about using the TELEXb (Powered i2c Bus), to enable Teletype to communicate with just friends in another case - assuming i also had a i2c select bus bridge, do you know if the TELEXb would also pass along the select bus state?

So the net result i’m after is 2x (or even 3) skiffs each with i2c modules & mungo modules all recallable by TT. Man, that would be a powerful thing.

Thanks for your help so far.
Warmth,

#20

I’m doubtful that the TXb would pass the Select Bus state information, simply because it doesn’t travel over I2C. Nevertheless, all hope is not lost because I believe that Doepfer make/made several “bus access” modules that do the same thing for the Select and/or CV Buses that a TXB would for I2C. And you don’t even have to worry about cable length with them :wink:

#21

So the Teletype outputs regular I2C messages still, which would be transmitted over the TxB module. However the bit of hardware that changes that to a MIDI message onto the CV bus would need to be in each case. Unless you did as @alanza said and somehow linked the CV buses from each case.

Ive been trying with my Malekko modules to get them to clock via MIDI messages on the CV bus, but it hasnt been fruitful. This week im going to add a trigger out to the gate bus on the breadboard behind teletype, and get those clocking.

If anyone wants to give this a go, im happy to share the hardware and code ive used! Its a teensy with $2-3 more of components on a breadboard. The pcb is basically done, i just need to wait until a few other projects are also ready so i can put in an order

4 Likes
#22

If this means I can bridge my TT/ansible ecosystem with Rene and Tempi I’m super interested!

#23

Finally climbing out from under my build and catching up. Have to say that this is damn cool. Congrats!!!

2 Likes
#24

Hello I’ve read this thread a few times over the past few months and am very interested.
I am wondering Is this something that may become a reality for an end user like my self with no soldering skills?
Thanks for your time

1 Like
#25

Did this ever see the light of day? I worked with SDS_Digital on the Melisma and Sandrine implemented Select Bus options (the Melisma acts as both Master and Slave or automatically detects another master if set to Auto). I also have a WMD SSM (Slave) and an Omnimod (Slave) on the same case as the Teletype. I’d be more than eager to learn what happened with this project and whether one can set the Teletype to send messages to the Melisma over the bus.

I’ve been considering suggesting i2c implementation in the Melisma (there are other modules out there than can also accept/send i2c) but maybe it would make things easier to just keep things separate.

1 Like
#26

So interested in this too.

1 Like
#27

I’m still hot-under-the-collar imagining the fun coinciding i2c and select bus module save states (inc makenoise/distings/mungo/wmd/malekko/omnimods etc) into teletype op’s @jimi23. I hope this project isn’t dead in the water.

Side point, likely clutching at straws here but I wonder if MIDI program change messages into the CV/Gate bus is possible with crow ?? I know its outside of crows lane, but as i understand it the module has midi and i2c possibilities.

1 Like
#28

So Melisma acting as i2c > MIDI translator is unfortunately out of the question due to hardware. There are other options I’m currently looking into which already have i2c connectivity; we’re just missing the software.

I’ll check Crow and see if there is a way this could work. I’m not familiar with what it’s supposed to do.

Here’s hoping the i2c > MIDI translator that @jimi23 worked on will see the light of day. We’ll need ops for this, but I’m sure that can be arranged after the fact.

EDIT

@Ravel it seems that it’s really about hardware and whether Crow was designed in a way that it can send messages to the pin in its power connector that goes to the Gave/CV bus. If it does, then it could possibly be re-programmed to talk to the Select Bus, otherwise I don’t see a way. A dedicated translator that plugs behind TT, grabs the i2c data and translates them to MIDI with pins available to connect it anywhere (including the Select Bus) sounds like a more feasible way to go.

1 Like
#29

Hi sorry this didn’t get much further, I downsized my eurorack setup some months ago and sold my Teletype.
I’ve found the project files, I will sort through and upload to Github on the weekend for anyone interested to look at. There wasn’t much complexity to the code, there was more work in adding new ops to the teletype firmware (that wasn’t done by me). The PCB was designed to be a Teletype backpack

A faderbank can also run the i2c -> midi conversion as a test environment for Crow. I do have a crow, and am planning on building a FB soon, so I might be able to look at it more then.

The crux of select bus control is a control change message followed by the Program change as below (code was adapted from the Txo)

image
image580×558 4.66 KB

2 Likes
#30

And in terms of hardware? Thank you so much for sharing information on this project. Too bad you’re not currently invested in this, I wish I heard about it sooner!

#31

Agreed, appreciative of you getting the ball rolling with this and please do share what you have. Wish i had much to offer by way of taking this further (beyond enthusiasm for the project)… hopefully there is someone within the community with the requisite skill and willingness to finish what you started - seemed like you were most of the way there.

#32

New disting can receive I2C and send Select Bus messages! I think we’re about to get that bridge we were after.

3 Likes
#33

Just watching the new Disting EX, and Os is controlling the algorithm from an 8m via i2c. Wold be really nice to have this added into the ops for Teletype if that’s possible.

#34

I’m guessing (edit: confirmed) os is currently using the F8R (new name, 8m was prototype) in leader mode to send SC.CV messages. The new disting ex will need to have a space carved out for it in the ecosystem, both address and OPs.

EDIT: os is using behind-the-panel MIDI in the demo, actually. But I confirmed he is using the SC.CV messages right now.

2 Likes
#35

Beginning to think that the i2c framework needs some better way of switching/routing in the case to be able to modify the connections without having to unscrew everything from the case.

#36

There’s been some discussion about I2C routing over here: I2c multiplex chip?