#252

teletype numbers are signed 16 bit integers, so the possible range of values is -32768 to 32767. negative numbers are represented using two’s complement - that’s what pretty much every computing system uses, and this is why you get negative numbers if you set the most significant bit: for instance, doing this: BSET 0 15 results in -32768.

when using binary ops (BGET / BSET etc) you don’t have to worry about remembering how two’s complement works, unless you need to convert a binary value (like a drum pattern in your case) to a signed decimal value teletype uses, say if you need to initialize a variable. in this case yeah you can just use an online converter tool, or if you’re on windows you can use the calculator app switched to programmer’s mode. or just use the live screen and manually set the bits with BSET.

#253

axe thing one

For the guitarist in you. Hopefully the video will serve as a quick manual.

requirements

download
axe thing one.zip (3.2 MB)

installation

  • axe thing one.txt is the teletype file. rename it to ttXX.txt where XX is the scene number you want to load it into. copy to your USB drive root, and load on teletype
  • slot1 is an ER-301 quicksave. copy the files in the folder to one of the quick save folders on your ER-301 SD card. then load that quicksave
    /ER-301/v0.4/quicksaves/slotX

other notes

  • the ER-301 quicksave comes with 6 acoustic guitar samples inside the quick save folder, so it should load ready to play
  • the first 6 or so default chord presets are in the key of G major. you might have to select a preset button other than #1 to get things started the first time
  • some fun stuff to try would be using something other than acoustic guitar samples, trying some different tunings (e.g. bottom two strings doing bass)
12 Likes
Crow & end-user documentation
#254

this is amazing!! thank you for the detailed video walkthrough. added to the grid codex!

1 Like
#255

For some reason when using teletype 3.0 ( I havent tried previous firmware), TR1 aka clock output doesnt follow the clock that I send to input 1. Any idea why that could be happening? It sort of skips certain clock pulses, but stays in sync. Maybe the issue is with the clock pulse width?

#256

it sounds to me like TR.TIME 1 might be set longer than the time between clock pulses coming in?

1 Like
#257

are you seeing something similar to this? Teletype dropping TR.P -- with video :-)
i’m planning to look into it when i get a chance.

edit: actually not sure that’s related. could you describe what happens exactly and post your script?

#258

Teletype / Grid Ops Rene / Rungler… getting there.

I’m working on a scene to make a Make Noise MATHS, plus an STO (or whatever), and a QPAS (or whatever). Into a sort of melodic Benjolin. Using shift register methodology to create patterns and fluid variable, based upon just 2 gate/trigger ins, from the two MATHS function generators.

It’s not a deep as a Benjolin or a Rene. But it seems like a playable ‘instrument’.

Overview -

Script 8.
CV input of notes to the melodic sequence pattern. Shift register style. Once there are 16 values, any new first value is added and the 16th (now pushed to 17th) is deleted. Keeping the pattern 16 steps long. These values can be entered at any time.

Scripts 1,2,3
Triggers/Gates 1 and 2 generate the Rungler values. Trigger 1 is the ‘oscillator’, Trigger 2 is the clock. A 4 step sequence/shift register is created and a 4 bit value is generated.

The second row of the grid displays the current (Z) rungler value 0-15.

The 7th row of the grid displays the current (Y) intermediate variable value 0, 4, 8, 12…

These two trigger/gates also clock the melodic pattern.

Trigger 1 advances the melodic seq by 1 step, Trigger 2, by 4.

Script 4 plays the basic melody. Taking the data generated by scripts 1-3 and the grid.
The 16 steps are represented by a 4 by 4 square of buttons at the centre of the grid. Any of the stages can be muted. The default - unlit button setting - is unmuted.

Script 5 randomises the melody using the Rungler value and the buttons to the left of the square. More buttons pressed, more random.

Script 6 sporadically transposes the melody using the Rungler, the fader at the bottom of the grid (semitones), and the buttons to the right of the square.

Script 7 generates stepped and smooth CVs from the Rungler.

The top row or the grid is a fader controlling the gate length of TR.P 1, which plays the melodic part. High values will mute some triggers.

Apologies, again, for video glare making the centre 16 buttons into an indistinct blur…

https://vimeo.com/335634872

RENE RUNGLER

#1
X EZ X
PN.NEXT 1
TR.TIME 1 LSH G.FDR.N 1 6
$ 4

#2
G.REC 0 1 16 1 0 0
PN.L 0 4; PN.INS 0 0 X
PN.L 0 4
Y + * 4 PN 0 2 * 8 PN 0 3
Z + Y + PN 0 0 * 2 PN 0 1
G.LED Z 1 15; $ 3

#3
G.REC 0 6 16 1 0 0
G.LED Y 6 15
L 1 4: PN.NEXT 1
TR.TIME 1 LSH G.FDR.N 1 6
$ 4

#4
G.GBTN.L 0 4 4; A PN.HERE 1
IF EZ G.BTN.V PN.I 1: CV 1 N A
IF EZ G.BTN.V PN.I 1: TR.P 1
G.BTN.L PN.I 1 8; $ 7
IF NZ G.GBTN.C 1: $ 5
IF NZ G.GBTN.C 2: $ 6

#5
B QT DIV Z G.GBTN.C 1 1
EVERY B: PN.INS 1 Z PN 1 15
EVERY B: PN.L 1 16

#6
C QT DIV Y G.GBTN.C 2 1
EVERY C: CV.OFF 1 N G.FDR.N 0
EVERY 2: CV.OFF 1 0

#7
T TIME; TIME 0
CV 2 VV LSH Z 5
TR.TIME 2 15; CV.SLEW 3 / T 2
EVERY Z: TR.P 2
CV 3 VV LSH Y 5
EVERY Y: TR.P 3

#8
DEL 20: D DIV QT IN N 1 N 1
DEL 20: PN.L 1 16
DEL 20: PN.INS 1 0 D
DEL 20: PN.L 1 16
DEL 20: CV 1 N D
DEL 25: TR.P 1

#M
G.GBX 0 0 6 2 1 1 1 6 0 4 4
G.GBTN.L 1 2 4; G.GBTN.L 2 2 4
G.FDR 0 0 7 16 1 0 5 6
G.FDR 1 0 0 16 1 0 5 0
TR.TIME 1 150
M.ACT 0

#I
G.RST; X 0; Y 0; Z 0
L A D: I 0
PN.WRAP 1 1; PN.I 1 0;
G.GBX 1 20 0 3 2 2 1 3 0 3 1
G.GBX 2 23 10 3 2 2 1 3 5 3 1
PN.L 1 16; M.ACT 1

10 Likes
#259

very cool - added it to the code exchange page!

#260

Thanks!
I’m a little confused regarding where things like these should be posted. There’s the original TT code exchange page, here. There’s this page, and there’s your page at GitHub. Sharing here feels right, but don’t want to add redundant posts…

#261

this is the right thread for grid based scenes - this is a sibling thread to the main TT code exchange. the goal is to have a dedicated thread not just for posting grid based scenes but also for any grid ops related discussion / feedback etc.

the github page is simply an index of all the grid scenes posted here, for easy search and to just get an idea of all the things possible with grid ops.

1 Like
#262

Doing some research, thought I’d make a post here to brainstorm a little. I really like the way the Kria sequencer works and was wondering if there are any examples of people writing scripts here with page functions similar to the kind seen in that program? I want to do something similar to Kria but with slightly altered, more MLR-esque functionality to drive the STS. Any input is appreciated and I hope to share any interesting findings along the way. Cheers!

2 Likes
#264

Got my Teletype about ten days ago and I’m already completely in love with the possibilities. I figured I’d share this simple mutating “pseudo-Turing” note Grid sequencer that I made today:

It’s a clocked Kria-style sequencer. Every clock tick, PARAM is read as a percentage probability of mutating the current note using TOSS to add or subtract a fifth. Notes can also be set manually. Notes are translated into a scale using a pattern lookup table (minor in this example) and the bottom row can be used to set a loop range in the usual Kria way.

"TURING MACHINE" GRID
TR1: CLOCK TR3: RESET
PARAM: PROB OF CHANGE/STEP
     BY A FIFTH UP OR DOWN
CV1 OUT: NOTE
PN0: SCALE LOOKUP TABLE
SET LOOP USING BOTTOM ROW

#1
T WRAP + T 1 C D
SCRIPT 2
L 0 15: G.FDR.L I 2
G.FDR.L T 4
A SCALE 0 16383 0 6 G.FDR.V T
CV 1 N PN 0 A

#2
Y LT RAND 16382 PARAM
B + G.FDR.N T ? TOSS 4 -4
IF Y: G.FDR.N T WRAP B 0 6
IF Y: G.LED 15 0 15
ELSE: G.LED 15 0 0

#3
T D

#4

#5

#6

#7
IF EQ G.GBTN.X2 1 -1: BREAK
IF EZ G.BTNV: BREAK
C G.GBTN.X1 1
D G.GBTN.X2 1
G.GBTN.L 1 5 5
L C D: G.BTN.L + I 100 12

#8

#M

#I
G.RST
G.GFX 0 0 0 0 1 7 1 2 8 16 1
G.GBX 1 100 0 7 1 1 0 4 7 16 1
C 0; D 15

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

0	0	0	0
2	0	0	0
3	0	0	0
5	0	0	0
7	0	0	0
8	0	0	0
10	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0
0	0	0	0

#G
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000

0	1	4	4	2	0	4	0	0	0	0	0	0	0	0	0
0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0
0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0
0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0
8 Likes
> teletype : code exchange
#265

I had some fun today porting the drum maps from Mutable Instruments Grids to a Teletype/Grid version.

The original code uses a 5x5 grid of drum patterns. Each pattern is 32 beats long and has a track for kick, drum and hat. Each drum-beat contains a value up to 255 that is the probability of that drum firing on that beat based on the level of the kick/snare/hat inputs.

To make the maps fit in Teletype’s pattern memory, I reduced each 8-bit probability value to 5 bits, and stripped the patterns down to 16 beats (most of the patterns don’t use the offbeat at all). I also reduced the 5x5 map to 4x4. I also haven’t yet implemented the crossfading between maps in the grid, the code just snaps to the nearest map. There’s a Ruby script that performs the embedding, and the Teletype code pulls the bits out again with bit-shifting operations.

I used Grids integration with a grid and faders to compensate for the lack of CV inputs, but it’d be much nicer with TXi or 16n inputs if I had one of those available.

13 Likes
#266

So Trigger 1 is clock and 3 is reset?

#267

Yes, forgot to mention that.

#268

Did anyone ever get around to trying this out? I’m going to give it a shot myself when I get the chance. I am trying to set up pages so that I can switch between a main trigger sequencer page and additional CV fader sequencers (working off of @mattbiddulph 's turing sequencer for this bit! good timing). Perhaps there is a tricky way to condense multiple “pages” of buttons into one init script, but I am not a programmer by trade so anything hacky that gives me a few more lines is really helpful for learning how to solve these problems.

1 Like
#269

The SCENE.G op was added in the 3.1.0 release, which lets you change scenes without resetting grid controls, the intention being to let you use an entire scene (or more?) for initializing complex Grid apps.

3 Likes
#270

this is absolutely awesome. I can’t wait to use it. Thank you :slight_smile:

#271

A quick hack to give my Grid the basics of an Ableton Push isomorphic scale keyboard:

the code:

Works in a pretty brute-force way, just using pre-generated pattern lookup tables to derive the note numbers of each point on the grid. Patterns 1, 2 and 3 map note numbers to major, minor and dorian scales. Change the scale in use by changing the “2” in line 22.

3 Likes
#272

Hi! Did you managed to create the Earthsea style polyphony scene for the TT to be used without the JF? I’m enjoying this a lot, but I would also like to control other VCO’s with the grid controller.
Thanks a lot for your work!