teletype and walk are available for pre-order at control in brooklyn:

please support these fine folks who believe in forward-thinking design!

1 Like

i know this is will open a can of worms, but i’m still up to implement new ops/etc. things i’m considering:

DRUNK which has a state, each read changes by -1, 0, or 1. settable to a value.
H which outputs the average of the last 8 values assigned to it (“history”)
RSH right shift (div by powers of two)
LSH left shift (mult by powers of two)

all of these things can be done already with existing commands, but my goal is provide a toolset for common uses. if anyone has a super common use case in mind, please let me know and it might make it into v1.0

1 Like

Pre-ordered. Can’t wait. Thanks!

SWAP X Y - swap 2 variables (would save on the need to use a temp var)
X DEC VALUE LIMIT - decrement X by VALUE but don’t let it go lower than LIMIT
X INC VALUE LIMIT - increment X by VALUE but don’t let it go higher than LIMIT

^ LIMIT could be optional (will wrap if goes under/over)

These are good suggestions! @scanner_darkly

I wish there was a way to set those limit values for INC/DEC rules in Meadowhphysics :smile:

Also, re:v1 inclusions: extended ES sync pretty please…

+1 :sunglasses:

Really looking forward to it.

can we get a (pre)release day celebration demo?

Much more video to come! The current demo is just an attempt to introduce some raw capabilities, but there will be more videos in the musical performance context, and perhaps tutorial style ,though these might end up more in the text w/ ‘screenshots’ territory depending on what makes most sense.

There’s a huge amount of depth to teletype on it’s own, as well as in integration with the trilogy & walk - which is to say we haven’t discovered more than a tiny fraction of capabilities so far. I for one am excited to make music with the thing, rather than just think about it conceptually (@tehn has the only prototype rn)!

1 Like

yeah the tutorials could definitely be screenshots or just scripts + explanation

the next video doesnt need to be mindblowing but it’d be nice to just see it as part of a patch…we can disect whats happening or merely observe one potential use case

IDEA:

Does the makey makey could work with teletype ?

because it acts as a keyboard but can works with object like fruits, vegetables etc…

Um… yeah? Vegetables?

Edit: I spoke too soon, without googling. Vegetables!

teletype is not “played” with the keyboard. it’s “programmed” with the keyboard. it’s “played” with the trigger inputs, from other modules.

so the makey likely doesn’t translate. i’m sure you could rig a makey-to-trigger interface, however.

Are the trigger inputs just comparators? Could one trigger them with piezo discs or loud sounds?

they are normal digital inputs. you’ll want to pre-condition messy signals to get predictable results. i can check for exact trigger voltage thresholds.

Cool. No worries. Sounds like what I would expect.

another reason to get this (hinted at above)

it will make a perfect companion for a drummer…
at first I was merely thinking of patch control via pedals but if you have piezos or something like this

it could really open up how you improvise or perform a song

another potentially useful command - FLIP, if a variable is 0 set it to 1 and if it’s anything other than 0 set it to 0.

could be used to make something like this more elegant - a script to add swing/reset WW (trigger 1 is clock in, trigger 2 is reset):

1

IF X II WW_SYNC
ELSE DEL PARAM : II WW_SYNC
FLIP X

2

X 0
II WW_POS 0

this one just sets the absolute value for swing delay based on the param pot (should probably also scale/limit), but should be simple enough to use TIME to adjust swing based on the clock rate and then the param pot could control percentage instead.

1 Like

only one PRE is allowed per line.

ie, you can’t use ELSE and DEL in the same line.

the PRE system (with the : separator) is only real “hack” to what is a very standard prefix notation calculator (which teletype is). http://en.wikipedia.org/wiki/Polish_notation

as it stands, the engine isn’t equipped in its current state to do things like

FLIP X

because X is passed as a value, and FLIP doesn’t have any facility to know the address of the variable. this seems trivial, but it’d be an ugly hack into a currently very elegant and efficient engine. luckily, most things can be done that you’ve suggested, but require more words. FLIP X is:

X EZ X

here values flows right to left. the leftmost is always the setter.

the ELSE DEL can be implemented as a var instead. let’s us T because it’s time based (this is arbitrary)

1
IF X T 0
ELSE T PARAM
DEL T : II WW.SYNC
X EZ X

hope that all makes sense. i’m well into the manual now, should have a mostly-complete version posted by tonight.

3 Likes

thanks @tehn, i thought that might be the case (only one PRE per line) but yeah, still doable with variables.

re: FLIP - thought EZ/NZ could be used but wasn’t sure what they meant exactly (still not but should really wait for the updated manual!)

1 Like

EqualsZero NotZero.

equivalent to == 0 or != 0 so great for state flipping.

1 Like