Teletype MIDI IN ops [experimental]

[scanner_darkly]

@EqualTemperament

MI.$ 0 x : My thinking was that script x would fire on any event - note, controller, etc. But it only seemed to trigger on note on events

this is fixed, new firmware in the OP!

@EqualTemperament

Start/stop controls of the Kronos sequencer do send events 6 and 7 (was expecting 5 and 6 but not sure?)

i think this might actually work as intended - i vaguely recall seeing some device sending “continue” instead of “start”. do you get event type 6 for “stop”?

@EqualTemperament

For the ones I listed as don’t work, they also didn’t work with Per|former. Except the Novation Impulse which seemed to work fine with Per|former but not teletype. Oppositely, Akai Advance mostly worked with teletype but didn’t even register on Per|former

this does make me feel better about things not working with teletype! and since teletype uses the same MIDI implementation as ansible i would expect same result with ansible.

@EqualTemperament

CCs behave erratically. I am updating T with MI.LC and whenever I move a CC control it alternates between about 3 different numbers. One of them appears to be the correct CC number

i wonder if it actually sends multiple CCs from one knob - like high resolution mode or something like that. can you try this script:

#I
MI.$ 3 1

#1
PN 0 0 MI.CL
L 1 MI.CL: PN 0 I MI.C
L 1 MI.CL: PN 1 I MI.CC

since MIDI events are processed based on a timer, it’s possible that several events can happen before the next check, these op variations allow you to process all events that happened, not just the latest one. this script should process all CC events and place them in pattern banks 0 (controller number) and 1 (CC value) starting with index 1. value in pattern bank 0 at index 0 will contain the total count of events since the last time the script was executed.

this is important if you want to get reliable output from multiple knobs or chords.

@EqualTemperament

Question: can scripts be overloaded with events? E.g.

MI.$ 1 1
MI.$ 2 1

to fire script 1 for both note on and off?

yep, you can totally assign same event types to the same script (say, to save space), and then use MI.LE to determine which event triggered the script.

@EqualTemperament

confessions of a MIDI device hoarder

that would make a good name for an album (or a memoir)
thanks again for your help - if you ever visit vancouver i owe you a beer!

[EqualTemperament]

@scanner_darkly

if you ever visit vancouver i owe you a beer!

Negative - should we ever meet in person, drinks are on me.

@scanner_darkly

you can totally assign same event types to the same script (say, to save space), and then use MI.LE to determine which event triggered the script

This was not working in the 2nd build but seems to be fixed in the 3rd build that fixed the MI.$ 0.

Akai Pro Advance 49

@scanner_darkly

i wonder if it actually sends multiple CCs from one knob - like high resolution mode or something like that. can you try this script

So your ‘process events in window script’ helped me figure it out, though it was not actually sending multiple CCs when adjusting a single. What was oddly happening is that I was connecting to teletype via the 2>1. When connected to the 2>1, there is some sort of weird bi-directional jitter going on with MIDI CCs. No clue what’s happening here, as nothing weird happens with the 2>1 with other devices. I think we can confirm Akai Advance 49 works now, when I connect directly to teletype (surprised my old rev teleype powers this thing with its color TFT and huge multi-color LED drum pads). See video for what happens when connected via 2>1.

July 31, 2020

More Confessions/Device testing

• Roland Juno-G does not seem to work (with teletype or per|former)
• MAudio Venom does not seem to work with teletype but does work with per|former

And Then…

I thought I’d actually try to do something a little more advanced and maybe useful. This is an ER-301 chain preset and teletype scene for an 8 voice polyphonic piano with velocity sensitivity that you can play with attached midi controller. It is set up to be last note priority but I have not actually implemented the voice stealing yet - works fine if you don’t exceed 8 notes.

It’s actually working quite well! This is something I haven’t been able to do with modular yet. I could do 8 voice poly, but not with velocity per voice too - that would require a MIDI–>CV converter with 24 CV outs which I don’t have. Until now (kind of) with i2c.

If anyone wants to try it, I think the most fun screens to watch and understand what’s going on are the pattern view on teletype, and the hold mode view on ER-301. Note that if you need to implement an octave transpose to put middle C where you want it, that’s in script 3. Just add or subtract some volts (V). I subtracted 2.

SC.CV + J 1 - MI.NV V 2

I recommend to put the .wav and .slc in /ER-301/samples unless you want to go re-attach the wave file across 8 sample players. I have only tested this on ER-301 v 0.5.03 48kHz version.

Poly 8 Piano ER-301.zip

[scanner_darkly]

@EqualTemperament

there is some sort of weird bi-directional jitter going on with MIDI CCs. No clue what’s happening here, as nothing weird happens with the 2>1 with other devices

that is weird since 2>1 is just a mechanical switch. i did notice some weirdness with novation launchcontrol when connected via 2>1 vs direct, but not with any other MIDI controllers i tried. can’t tell from the video - does it give you the correct CC value for the proper controller number? would filtering on that in the script provide a usable workaround?

@EqualTemperament

an 8 voice polyphonic piano with velocity sensitivity

this is great! and the nice thing is you can do additional processing on teletype, use param knob to transpose, control velocity range, create your own arpeggiator etc.

[EqualTemperament]

That would likely work as a workaround, though I don’t really need for this device to work with teletype. I’m just basically trying to help establish a baseline of what works with it. Seems like some things don’t, but plenty do. Some of the things I’ve tried, I can’t even remember if they claimed to be class compliant, so I wouldn’t worry about some of them not working. The things I was really hoping would work did.

Yeah, I think that’s the beauty of these MIDI ops. Much like everything else in the monome ecosystem they allow you to roll your own custom solution for whatever you’re dreaming up today. You can do some things you just can’t do with anything else!

[scanner_darkly]

exactly! i think teletype as a MIDI processor provides a really good combination of flexibility and ease of use. you can create sequencers out of simple controllers, remap CCs (useful for older controllers where you can’t change controller numbers, or for creating synth specific mappings), controlling multiple parameters with one knob, creating complex actions etc etc. i’ll try to post some examples this weekend.

[meri]

Arturia Keystep works this is with your piano @EqualTemperament

@meri.leeworthy

[thopa]

Just found this post…oh dear!
So i know i have to digest and test all the above info, but you are saying i could use the pots on a midi twister to enter cv n note values on the tracker, and use the knob switch for some kind of note on /note off action? So i can dream of making a teletype sequencer, where the patterns could be controlled by the midi twister?
Thanks!

[scanner_darkly]

yeah, that’s definitely doable, and i can confirm midi twister works with teletype.

i’m in the process of adding documentation for midi ops so that they can be merged into the official beta version.

[thopa]

Thanks for the reply @scanner_darkly that is great news!
Im away from my twister at least for a week, but i just thought i might give it a go with the befaco vcmc since it has buttons and faders that are sent trough usb midi.
Maybe i could use it also ala txi and convert voltages to midi messages that can go into teletype, though that doesnt make too much sense to be honest.
Will give it a go!
Muchas gracias!
Ps: and i just thought that the twister has 4 banks just like the teletype has 4 trackers…

[ParanormalPatroler]

@thopa

Im away from my twister at least for a week, but i just thought i might give it a go with the befaco vcmc since it has buttons and faders that are sent trough usb midi

What a great idea x2! I have the twister and never thought it could be a Grid replacement. And it never crossed my mind to use the VCMCs usb output as a direct control for the TT! Need to update my TT and try this.

[scanner_darkly]

MIDI in ops have been merged to the latest beta posted here: Teletype 3.2+ feature requests and discussions

i’ve also enabled the midi clock event but don’t seem to be able to test it successfully (either my devices aren’t sending midi clock or i’m doing something wrong…) if somebody could give it a try it would be great!

since midi clock runs on 24ppqn, it’s divided. by default the divider is set to 24, you can set it to any value between 1 and 24 with the MI.CLKD op (run it without a parameter to get the current value). you can reset the clock division counter with MI.CLKR.

[Cromatica45]

I’m trying to figure out a way to control different voices of Just Friends and keep them sustained till I release the key instead of cycling with a fixed AD envelope. Is there a way to do this? Let’s say that I want to trigger different notes each one on a different channel. I could solve it by executing different scripts depending on which channel the note comes from, but I’m stuck with it …

[Cromatica45]

Ok. I’ve managed to do this … A simple GATE/CV converter to I2C over MIDI, using the BEFACO VCMC.
Probably there a lot of things to polish …

VCMC 2 JUST FIRENDS I2C

IF VELOCITY NEEDED PER VOICE
CHANGE SCRIPT #1 LINE #4
FROM PN 5 TO PN 2 AND
DELETE LINE #3 



#1
L 1 MI.NL: PN 0 MI.NCH 1
L 1 MI.NL: PN 1 MI.NCH MI.N
L 0 5: PN 2 I 4
L 1 MI.NL: PN 5 MI.NCH MI.LV
$ 3

#2
L 1 MI.OL: PN 0 MI.OCH MI.N
$ 3

#3
L 0 5: PN 3 I * PN 0 I PN 2 I
L 1 6: JF.VOX I N PN 1 - 1 I 4
L 1 6: JF.VTR I V PN 3 - 1 I

#4

#5

#6

#7

#8

#M
TO.TR.M 1 PARAM

#I
JF.MODE 1; JF.SHIFT N -36
MI.$ 1 1; MI.$ 2 2
PARAM.SCALE 10 1000
TO.TR.TIME 1 5
TO.TR.M.ACT 1 1
M.ACT 1; M 50

#P
6	6	6	6
1	1	1	1
0	0	0	0
63	63	63	63

0	50	3	0
0	27	3	0
0	13	3	0
0	13	3	0
0	13	3	0
0	13	3	0

[ParanormalPatroler]

How did you connect TT with VCMC? To the best of my knowledge the VCMC doesn’t (fully?) support i2c yet, so am I right to assume you went via USB from the front, qnd hence used the MIDI ops?

[Cromatica45]

Yes, by using a USB cable from VCMC to TELETYPE. As I have the TWO>ONE module I can still change from the keyboard to the external midi in without unplugging the cables

[EqualTemperament]

@scanner_darkly

i’ve also enabled the midi clock event but don’t seem to be able to test it successfully (either my devices aren’t sending midi clock or i’m doing something wrong…) if somebody could give it a try it would be great!

since midi clock runs on 24ppqn, it’s divided. by default the divider is set to 24, you can set it to any value between 1 and 24 with the M.CLKD op (run it without a parameter to get the current value). you can reset the clock division counter with M.CLKR .

I can confirm the clock event is working. Both my Kronos and Hydrasynth seem to be sending clock just fine. I just tried a very simple experiment to flash the LED.

MI.$ 4 1

1:
TR.P 1

All looks good, it’s flashing on the quarter notes and I can adjust the speed with the tempo controls on the device sending the clock. I don’t think the M.CLKD or M.CLKR ops made it into build CB56E83 though. I am getting unknown word on those ops.

[scanner_darkly]

great, thanks for your help with testing!
and sorry, had a typo there - it should be MI.CLKD and MI.CLKR.

[EqualTemperament]

Ah, of course. Should have caught that myself. I can confirm that MI.CLKD seems to work as expected then. I’m not quite sure how to test MI.CLKR. Happy to try something if you have a suggestion.

[scanner_darkly]

not sure to be honest! i added it more so that there is a way to reset the division counter. i think it would make sense to reset it on a midi start event, or if you have a trigger that signals the start of a bar, you could put it in the corresponding script.

[woofy]

I am having troubles with reading out the toggle messages from my softStep.
I have to press a lot of times until the message gets through.

My script is just like:
I
MI.$ 3 1

1
l 1 MI.CL : A MI.C

So in the variables overview I see A changing after pressing 5-8 times for each toggle.
IF I use the pressure sensor mode on the pads, I instantly get the MI.C.