#41

Yep, totally see that now… and so I’m really considering it… too bad I didn’t fall in love with the mangrove… I think I would have to use dixies instead :wink:

#42

Personally I wouldn’t use note letters (G# etc). I much prefer voltage. Part of what I love about modulars is the interface that departs from the piano keyboard and therefore does not need to be tied to traditional scales and intonation.

#43

I can imagine how this would be ESPECIALLY useful in a small setup, as it potentially can do a job of multiple modules.

Also: a comment that I think then made earlier, that the module does not need to be used with keyboard during performance is something to take note of. As in something that you program in the studio with your specific/unique functionality set, and THEN control this with other modules etc. (Not to take away from live coding idea which also sounds like fun!)

2 Likes
#44

The best part is the ribbon cables :heart_eyes: the possibilities are endless!

1 Like
#45

cool

looking fwd to seeing more of these
the more i think about walk the more i might snap it up

hands free control of certain parame is always fun

#46

will there be commands to modify scripts themselves?

here is what i mean:
trigger 1 is set to output 1V on output 1
trigger 2 is set to output 2V on output 2
trigger 3 is set to output 3V on output 3
trigger 4 is set to output 4V on output 4

now we set trigger 8 to add random to outputs 1-4, so essentially it’s modifying scripts 1-4 to add random.
or it could be used to transpose outputs 1-4 by a certain amount.

i guess it could be done two ways, actually programming outputs 1-4 to do that when trigger 8 is on but if the actual scripts were modified that would be absolutely rad. self modifying programs. oh but then editing would be difficult, so probably not possible… unless changes are only made to Live scripts?

#47

also, would be great to have commands to assign LFOs that could be reset or synced to trigger inputs.

sidenote: noticed the naming is different from white whale - trigger outs are A-D and CV outs are 1-4 but on white whale it’s the opposite…

#48

i considered script self-modification but you get into messy territory, and you can do almost everything you’re probably thinking of with variables and presets.

CV.OFF is cv offset per output.

CV.OFF 1 V 1

cv.offset and cv values get added together. for easy transposition. cv.offset can be negative, but the outputs are 0-10v clamped.

in your example, if you wanted random offset per cv, you have many ways of doing this… the easiest would be:

trig 8: X RAND 2
trig 1: CV 1 V ADD 1 X
trig 2: CV 1 V ADD 2 X

etc… X is a temp var.

or, there are tons of ways to do this, really.

#49

I was just wondering if/how variable values were implemented :wink:

so cool!

can the incoming voltage be set as a variable? so that a single incoming CV affects all lines where the variable is invoked?

#50

preliminary documentation is up (along with the completely new website):

http://monome.org/docs/modular/teletype

this is pretty much an outline at this point. we’ll be adding explanations and examples promptly.

#51

yep, was wondering about variables too. makes total sense.
so cross influencing with variables should be possible too?

trig 1: 
X RAND 2
CV 1 V ADD 1 Y

trig 2: 
Y RAND 1
CV 1 V ADD 1 X

heading over to the doc…

#52

This “cross-pollination” facilitated by variables is what makes this the “ecosystem”… :smile:

very exciting!

#53

note that updating a variable doesn’t change a CV. a CV command needs to be executed to update the cv. or CV.OFF

you can “refresh” the CV’s all at once if needed, with a L(oop) PRE:

L 1 4 : CV I X

pulling this apart-- the command is executed four times-- each time I is substituted with the loop value-- 1,2,3,4. so this is the same as:

CV 1 X
CV 2 X
CV 3 X
CV 4 X

so… if you wanted to put random trigger values out on all four:

L A D : TR I TOSS

A - D are simply mapped to 1-4, so you can use them interchangeably.

#54

Just looking at the variables section of the documentation:

Love the idea of a variable that has a predefined behavior: the O auto-incrementing on each read. Makes me think that there could be more of those in a way similar to the Rules in Meadowphysics. Like for example:
O = auto increase
Q = auto decrease
D = drunk variable
etc.

Also: are X,Y,Z, the only three general purpose variable names? or are the XYZ only used as examples here?

#55

T also. ABCD can be used also for general purpose if you’d rather index TR and CV with numbers 1-4.

i’m considering implementing a runtime variable system, where you can use named variables. but in my use of the tele so far, i haven’t needed this.

you can use one of the four patterns for a scratch “array” which gives you 64 variables also. there is a lot of data storage here.

1 Like
#56

but don’t you like the idea of a drunk variable? :slight_smile:

#57

i do, but it’s a little specific for native functionality. you can make a drunk var thusly:

X ADD X RRAND -1 1

drunk! you can further use WRAP to have it wrap within a range, etc…

2 Likes
#58

I can’t say it enough, teletype looks amazing. Having stacks, patterns and loops really opens up an insane amount of possibilities, not to mention the remote commands. It’ll be like having 8 pairs of hands to perform with.

@tehn, am I correct in thinking that we could set the value of PARAM to one of the variables? Effectively making the param knob a way of performing live CV changes?

1 Like
#59

certainly looks this way!

IN                  get value of IN jack
PARAM               get value of PARAM knob
#60

updated the docs with the current remote commands.

ie.

II WW.PATTERN 5

to recall ww pattern 5