#15

afraid MIDI is a no go. i’m not able to make it work reliably with the teletype USB port, and i’m not able to troubleshoot / fix without doing a deep dive into USB/MIDI (if anybody has any ideas this thread has some details).

so the only feasible option at this point is sending MIDI via I2C and some I2C to MIDI converter.

9 Likes
#16

it seems like crow may be able to fill this position?

#17

possibly - but this depends on crow/tt integration.

#18

Is there a list of controllers that work?

#19

Teletype MIDI + I2C busboard v2 is almost done. Ive added the intellijel header for communication with the MIDI ports on their cases. They were helpful on that part. Last thing I will include on the board is connectors for the teensy USB data pins. The intellijel case USB port sends its data over the same ribbon cable. May as well include the option to connect that to the Teensy 3.2 data pins.

That seems simplest for getting USB Midi outside the case

6 Likes
#20

great news, and super useful additions!

not sure what you’re asking? i haven’t tried bidirectional MIDI via TT USB port with any MIDI controllers, just the USB-MIDI m-audio adapter. i did try sending MIDI from MIDI twister controller to TT and that worked, but there is no sense in implementing something that will only work on some but not all devices.

#21

Hope to be not much of a bother, but I’m curious how this busboard project is coming along? Excited for the possibilities!

1 Like
#22

First batch of pcbs arriving tomorrow for testing :slight_smile:

6 Likes
#23

Just a quick question, how does USB MIDI and Ansible work?

#24

It can function in a number of different ways. Check out the Ansible docs, the Midi section starts about 3/4ths of the way down after the Earthsea section :+1:

https://monome.org/docs/modular/ansible/

2 Likes
#25

Id like to sequence external midi (Digitone, Digitakt) with Kria using 16n to convert cv to midi.
Is it possible to get kria cv values to a range that will work with the fader ops? I can get everyone talking, but the tracking is wild.
Have tried both-
Kria directly
FB.ON 1 KR.CV A 100

Pached Ansible > Txi
FB.ON 1 TI.IN.N A 100

Telexi with an offset
FB.ON 1 + N 24 TI.IN A 100

I can accurately send midi notes to the elektron boxes if i manually put the notes in like
FB.ON 1 24 100

Is there a way to get midi friendly kria values?

#26

Given the introduction of a tuning mode in the next version to correct for voltage differences between CV outputs, I realized that getting one’s CV outputs all tuned the same would actually knock the values read by KR.CV out of tune with each other, since KR.CV just grabs the DAC value directly. So I’ve been considering a KR.N x op which would give you the calculated note value that track x is playing, and then if you wanted to scale that back to the range of KR.CV you should be able to use N KR.N x to get exact pitch tracking on e.g. a TXo. Given the conventions already in place I think it would make sense for this to use the midi note numbering scheme. Does this sound like it would work? KR.CV does have the advantage of being able to capture intermediate values while a note is slewing, which such an op could not easily do.

2 Likes
#27

KR.N would be great. Im adding a +24 offset to the kria values when using txo just to get the notes to audible values. It would be nice to not have to use the Telexi and be able to send KR.N to both TXO and out of my case via the fader bank to my external devices.

If trying to sequence in the other direction, It would also be convienient to just be able to get the note values of the ansible cv ports without being program specific. Like ANS.N 1 So you could sequence JustFriends or TXO from external midi.

Thanks for all the work youve been putting into ansible, the beta firmware is great.

2 Likes
#28

FB.ON uses semitones since it sends MIDI, so you just need to scale values you get from KR.CV to that. V 1 value covers an octave, so to scale to MIDI notes you just need to divide KR.CV by V 1 and multiply by 12 - but best to use SCALE for this as this way you won’t lose precision. something like this: SCL 0 V 10 0 120 KR.CV

with this approach you could also use teletype as a quantizer and control scales in teletype instead of kria, if you prefer. still, KR.N or app agnostic ANS.N would be useful!

1 Like
#29

Awesome. Sincere thanks @scanner_darkly, SCALE works perfectly. I didn’t really understand what that op did but totally grasp it now, and it does exactly what i was hoping. I am now simultaneously sequencing both digitone and digitakt via kria using the 16n as the middle man and its tracking perfectly so far. Its blowing my mind.

1 Like
#30

you could also simply divide by 1365 but that might give you slightly innacurate results (V 10 is 16384, 16384 / 12 = 1365.33…)

the cool thing about having teletype in between (in addition to being able to use it as a quantizer) is the ability to additionally transform notes - transpose (it’s fun to use the knob to control transposition), skip random notes, transpose random notes, turn each note into an arpeggio etc etc

2 Likes
#31

Teletype is the heart of my system and I have barely scratched the surface. Im loving the development of the whole ecosystem and feel fortunate to be able to explore it. If I can eventually plug my op-z directly in as a meta controller instead of a keyboard I will have more power than one man should possess.

2 Likes
#32

@scanner_darkly could you point me to the most up-to-date firmwares for 16n & teletype that include the midi ops? i’m having a bit of trouble finding them myself

#33
1 Like
#34

After reading through this, I understand why we don’t have midi ops for the teletype, but damn if I wouldn’t love having ops just for the twister fighter alone.