Grid ops / integration

Quick clarification - Ansible Satellite doesn’t exist today? I can’t find anything on it. Is it an alternate Ansible firmware? I’d love to test the beta, but I don’t have an ext5v [1] or switch. I do have an Ansible and a TT though.

[1] - I bought an ext5v, but it was stolen off the UPS cart. An extended UPS reimbursement effort ended in me getting a trilogy compatible power supply in the meantime. Now i wish I had re-ordered the ext5v. They’re hard to find, I hate that someone took one out of circulation that I’m confident has no idea what they stole. It’s probably at the bottom of Boulder Creek.

1 Like

i’m waiting for parts to arrive (next week) and i’ll have the new all-usb “offworld” power solution ready and for sale on the site…


This sounds pretty great…will pick one up for sure.

My situation worked out fine for me. I ended up with a Row Power 40. No regrets.

ansible satellite doesn’t exist yet, just an idea, but i’m hoping to find the time to work on it at some point. actually surprised there hasn’t been much response to this, i think this could really be great for small set ups, especially if you have something like an ansible satellite / ww combo with ansible running grid scenes. you could edit scenes on a teletype and transfer them via usb stick, or you could just use the scenes posted on the github.


Is the idea to run TT scripts on Ansible? I missed the original discussion. That sounds very cool. Headless TT!

1 Like

yeah, the idea is to run it as headless teletype. the difference in hardware would need to be accounted for - 2 trigger inputs instead of 8, but the 2 buttons could be used as a way to manually trigger 2 more scripts, no input and no knob, but you could use it with a TXi to get 4 knobs and 4 inputs). the mode button could be used to enter the scene selection mode where you would select a scene with the 2 buttons.


new beta posted. changes are:

  • changed button and fader identifiers and coordinates to 0-based instead of 1-based. if you already have scenes saved you’ll need to modify it - simply subtract 1 from the first 3 parameters in button and fader declarations. if you use math to find buttons or do something similar (trigger sequencer study uses this) it’ll need to be modified as well. i’ve already updated the wiki on ops, and will update all the studies later this week.

  • an important feature - button and fader states will now be saved both to flash and usb. this is really useful if you script sequencers - this way your sequences can be saved together with scenes (and it’s useful in general to have your UI be in exact same state when you power it on). one consequence of this is new buttons and faders don’t get their states reset to 0. if you do prefer this you can simply use G.BTN.V 0 or G.GBTN.V 0 in your init script. this is fully compatible with previous versions - you can load grid aware files on non grid firmware and vice versa. [technical details: grid state takes 64 bytes per scene]

  • total number of buttons increased to 256 for better support of grid 256.

here is an example of how it can be used, a trigger/CV sequencer scene:


all grid studies have been updated to account for the change to make coordinates and ids 0-based and to make sure they will be compatible with the upcoming version 2.1. i’ve also finished the groups study.

a brand new starting simple study shows some simple examples and explains the logic behind the op naming which should make it easier to read/memorize them. all the scenes are available for download and linked in their respective studies!

a video demo for “starting simple”: trigger visualizer / simple sequencer / lofi oscilloscope:


so the button state for all 256 buttons is saved with scenes, but we also have patterns. and since you only need 16 pattern values to store all 256 buttons (1 bit per button, each pattern value can hold 16 bits) you can store up to 16 full snapshots.

this idea led to the pattern canvas scene. this scene uses pattern memory to store 15 grid “slides” (not 16, i needed some pattern memory as extra variables), which could be edited with a grid and recalled with a script. instead of using a slide number it actually treats all slides as one continuous 240x16 steps pattern, and you can slide back and forth:

of course instead or in addition to using it as a visualization tool you could treat it as a 240 step 8 track trigger sequencer!

the script (might add it as one of the studies): pattern_canvas.txt (1.6 KB)



Can you tell me, does one need just 2.0 firmware installed on TT for the grid integration scripts?

This is a beta for a future release of the TT firmware. The current TT firmware does not contain the grid features.

1 Like

as @justmat said you will need the beta version posted in the first post of this thread (which is pretty much the official 2.0 with grid integration added). this beta does not include any of the upcoming 2.1 features, but once 2.1 is officially released i will rebase the grid beta on it so it will have all the 2.1 features as well.


so naturally i had to try scrolling canvas with an arc…
16 sounds from 4x TXo modules with decay controlled by one encoder and wave shape controlled by another.


that is very satisfying to watch!

this was one of the very first ideas i had for grid/teletype integration… water circles scene. pressing on grid triggers a note with VCA opened by slewed CV from teletype that gets smaller as the circle grows bigger. position controls pitch and wavetable via a couple of telex TXo modules. ansible levels controls the speed of decay.


Seems that those rare Telex modules are becoming more and more important!

1 Like

definitely, grid / teletype / telex is a very powerful combo! i really need to take more advantage of the many awesome ops @bpcmusic created for telex…


Holy crap, I just got the October Monome letter and realized this existed. I’d completely looked past this thread. Teletype just went from an inessential luxury to a must have for me. Pretty crafty, @tehn!

I’m not sure if this will constitute the most elegant way to get grid control over Reaktor, or the least elegant, bordering on hilarious. But it’s happening either way!


new beta! i did a rebase on the official 2.1.0 firmware so it now includes all the exciting new features @sliderule added. i did a quick test and everything seems fine. it also includes a bugfix for G.REC causing issues with out of bound coordinates (now they can be safely used and it will crop appropriately). code is now here:

the new beta posted in the op or just grab it here: teletype.hex [B0F9779 grid]

and here is the water circles scene if anybody wants to play with it (this includes a new op for x/y pad that is still work in progress). CV voltages will be updated as circles decay, and trigger will be fired whenever you generate a new circle. it uses all 4 pairs of outputs. it will also output a note corresponding to the X coordinate on TXo outputs (if you don’t have one you can repurpose some of the teletype CV outputs - change it in scripts 4 and 8). i’ll post a breakdown of the scene in a future study.

water_circles.txt (1.4 KB)

oh, and i renamed the thread to make it a bit clearer.


Hi there, I just wanted to introduce myself and express my massive appreciation for all the hard work everyone has put into pushing the Teletype forward. I picked one up at the beginning of the year and have been having a blast with it, but seeing how it’s evolved over time really has blown my mind.

Much respect and love to everyone who’s contributed to this amazing ecosystem!