> teletype: grid # code exchange

teletype

#41

Im new to programing the teletype… what is #P and #G? Thanks everyone! Love seeing the teletype grids here! Truly Inspiring Work Indeed!


#42

#P is for Parameters [edit: this is in fact wrong - the correct answer is #P = Pattern]

#G is for Grid


#43

It was really sketchy. But i promise i’ll do a decent version when i have time and i will share it here of course.


#44

Awesome thank you! I appreciate the simpleness… lol


#45

:slight_smile: if you were looking for a more in-depth answer I’m certainly not the person as I’m probably 10 minutes newer to this than you. As Grid operators are new they’ve not yet shown up in the Teletype cheatsheet. Looking at it again to verify that I see a “Patterns” section and now wonder if I gave you false information? #P might be for Patterns. Now we’ll both have to be set straight - oops.


#46

Ok, I have a question. Last night I uploaded the new 2.2 firmware for teletype… however, after I entered program mode, I tried one of scanner darkly’s basic tutorial… I tried the G.REC command with the appropriate follow up data… on the Metro whenever I tapped the teletype looked befuzzled and game me a unrecognized command return (not
Those words precisely)… I double checked the firmware… and it all looked ok? Trying to figure out what I’m doing wrong…


#47

Hahaha! I have been working through some of the beginner material on the monome site … teletype is awesome so far … lots to learn and it seems the curve is kinda steep but definitely learnable! It’s a nice challenge and a unique way to stretch the brain!


#48

The 2.2 firmware and the Grid firmware are two separate firmwares for now. You can find the Grid firmware here.

It should be noted that the Grid firmware is currently based on the 2.1 release, and will lack any of the 2.2 features.


#49

@unity2k

#P is indeed Pattern - as in, the numbers stored from the 4 patterns, as seen in the pattern tracker screen
#G is presumably for Grid but I’m not actually sure what is being stored here. There appears to be 2 sets of data. Button/fader state maybe? I’m curious too


#50

Are you powering the Grid externally ?


#51

With a monome switch in my eurorack


#52

yep, #P is for pattern data, and #G is for grid to save all button and fader states.

@markthepoet as @Justmat mentioned v2.2 and grid version are 2 different firmwares right now. they’ll be combined at some point but not until one of them is officially released. the grid version does include everything from the latest official teletype firmware v2.1. if you would like to try grid ops you will have to install the grid version.


#53

@Justmat @scanner_darkly
Hey! I figured out what I did wrong! Reflashed the teletype and works perfectly…Worked on a bit of the grid studies and wow…This is cool as F&%k! Thanks for the guidance!


#55

im working on a scene that displays a keyboard (organized in fourths) and records incoming notes in live.
What i don’t get is why do i have the note recorded in the pattern on button down and also on button up ?
Help would be nice if you have 2 minutes to check ! (Clock is script 2)

MARSMOUNTAIN



#1
IF NZ G.BTNV:
P.HERE - G.BTNI * 11 G.GRPI
IF NZ G.BTNV: TR.P 1
IF NZ G.BTNV:
CV 1 N P.HERE

#2
P.N 0; P.L A; P.NEXT
CV 1 N P.HERE; TR.P 1

#3

#4

#5

#6

#7

#8
G.GRP Y
Z * Y 16
X - 7 Y
G.BTX Z 0 X 1 1 0 10 1 16 1

#M

#I
L 2 7: Y - I 2; SCRIPT 8
CV.OFF 1 N 24
P.N 0; A 8; P.L A; TR.TIME 1 5

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

23	0	0	0
24	0	0	0
23	0	0	0
27	0	0	0
23	0	0	0
23	0	0	0
27	0	0	0
27	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	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

#56

is this meant to be IF NZ G.BTNV: P.HERE - G.BTNI * 11 G.GRPI?
placing them on separate lines will not achieve this, so P.HERE will be executed regardless of G.BTNV state. a simpler way might be doing IF EZ G.BTNV: BREAK instead.

btw, IF treats any non zero results as true, so instead of IF NZ G.BTNV you can simply do IF G.BTNV.


#57

Thanks !
So, IF needs to have the statement on the same line.
Is it the same for L x y ?
(edit, yes it is)


#58

correct, this is the case for all PRE ops.


#59

I’ve added a in scale transpose editor to the Fugetta sequencer so that you can transpose individual playheads.

I won’t post the code yet as I want to play with the UI a bit and probably add some more features. Thanks to @scanner_darkly 's latest update with the G.GBX & G.GFX etc. ops, I’ve managed to free up quite a few lines of code.


#60

love seeing more complex examples emerge! glad the new ops can help facilitate that.
are there any other group ops that you think would be helpful in addition to G.GBTN.L, G.GBTN.V and such?


#61

I need to find more time to play with them, but if I think of anything I’ll let you know