#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.

#35

not to say midi ops are completely impossible - but i don’t have enough knowledge of the USB protocol needed to investigate the issue properly.

#36

Totally understand. Was just thinking about ways to allow for more playable methods with the teletype besides just the grid and such. Have been looking at some of the Mutable Marbles emulations and was thinking of ways to get around my lack of a TXi. But! Again, we’re just talking about a niche experience that I sorta want because I don’t currently have it. Call it functionality GAS. Ha

1 Like
#37

Do you know if it would it be possible (theoretically) for someone (:raised_hand: maybe…) to look into the USB midi protocol and edit the firmware to include a MIDI op, which might be able to read notes as CV values, and (maybe) have notes on a given channel trigger a script with that channel id?

#38

i think i should maybe revisit it - receiving MIDI events worked fine, it was sending that was the issue. if you want to take a look at debugging the latter check out this thread.

here is my old midi branch: https://github.com/scanner-darkly/teletype/commits/midi

it’s hard coded for testing (it stores MIDI values into variables and triggers scripts 6/7) but should be a good starting point.

4 Likes
#39

That’s amazing!! I’d be very happy even if it were only able to receive MIDI to be honest, just as a first release perhaps?

I think it’s worth having some discussion on how different scripts are triggered though - be it corresponding to MIDI channels as I suggested, or incrementally from whatever MIDI channel is selected (with each note on), ignore MIDI channels altogether and only ever trigger scripts 1-4…?

This might be very exciting to use something like the OP-Z + Teletype to sequence stuff directly ( would also make the teletype a MIDI-to-i2c converter too?), and/or meta sequence Kria :heart_eyes:

Anyway, I’ll take a look into that branch!

5 Likes
#40

i think it should be assignable in order to cover different use cases. something like:

MIDI.S channel event script

event specifies the event type that will trigger a script - notes on/off, CC, start/stop/pause/clock, perhaps using a bit map so you could specify multiple event types.

5 Likes
#41

revisiting MIDI in ops, beta version here: Teletype MIDI IN ops [experimental]

1 Like