#919

as @synthetivv said it’s expected - variables I, J and K are local to each script. this is on purpose - this way you can store up to 3 values in each script without tying global variables or worrying about accidentally overwriting them in a different script.

1 Like
#920

Thank you! Yes must be this „local“ behaviour. Didn’t know that also K and J are local. But even in live mode it seems that they can’t be changed… which lead me completely to this trap :slight_smile:

#921

that’s because live mode has its own execution context, so they would be local to it too (not sure if you set J in live mode if it retains it though - it’s possible live mode gets a new execution context each time you execute something).

1 Like
#922

image
image4032×3024 2.25 MB

This just happened, it’s gone now but was wondering if anyone experienced this also?

#923

I’ve caught on to the idea of Teletype as a meta-sequencer as well as it’s capacity to work with Crow(s), ER 301, and 16n over i2c.

I’ve been doing the research and I can see: “If your Teletype has a green circuit board, it can support 2 direct ii/i2c connections. If it has a black circuit board (Dec 2018 revision), it can support 4 direct ii/i2c connections.”

I’m looking at a buying a green PCB version but what I don’t understand is: if you have a green psb with the backpack with the 12 male 6-pin, are you still limited to two devices besides TT (as above)? Or maybe there is a direct/indirect (or daisy chained?) relationship going on that I’m not tracking… Right now I’m just using 16n as master with ER 301.

It’s all a little head spinning and hard to choose whether to take on this avenue of learning along side the others I’m currently working through. Thanks in advance.

New to monome, and monome + modular: ask questions here
#924

with the backpack you can have more than 2 devices connected. there is no definite limit but you might get less reliable connection with too many devices, but it should be fine with even 8-10 devices.

it is recommended to only have one leader device on the same i2c bus, otherwise you might run into issues with teletype freezing or i2c commands getting dropped. if you want to use teletype with faderbank, you should switch 16n to follower mode and use teletype to poll for values and send them to er-301.

detailed info on i2c here: A user's guide to i2c

1 Like
#925

thanks for clarifying! I’d seen your posts about your i2c setup so I knew I was missing something.

1 Like
#926

I have another simple teletype question for the crew here!

I am trying to better get a hold of the patterns section as methods of storing things. So, I wanted to make a couple of different note phrases in to 1 pattern in different indexes in the hopes of basically creating scenes that I can move between.

So, say I wanted to have 3 phrases of note values in pattern 0. They would be 8 steps long, thus, the first pattern would be 0-7, the next would be 8-15 and finally 16-23.

Now, I want to just send a clock to scene input 1 to keep things simple and have a random swap between these different sections of pattern. My simple idea was to have K be my pattern identifier (either 1, 2 or 3) and be able to semi-randomly swap between these patters.

Is there a good way to exchange loop areas? How would I go about this? I’ve tried altering the loop and I’ve tried having k define what the next phrase would be, but then I goof something up and the pattern gets locked at the beginning index instead of moving on to the next number.

I could put together how my failing example looked if that would help.

#927 
I

P.L 8

1

K RND 1 3
IF == K 1: P.START 0
ELIF == K 2: P.START 8
ELSE: P.START 16

I think it would be okay, but I have to verify tonight to ensure it works.

3 Likes
#928 
1 

P.START * 8 RND 2

20 chars of fillers

2 Likes
#929

With this, I could add a line of probability for different patterns using a local variable too. Thanks once again!!!

1 Like
#930

Did you already see this: Teletype workflow, basics, and questions
I also had this problem and just replaced the screen. @tehn may help you!

1 Like
#931

Does anyone have any suggestions on how to approximate the Marbles jitter knob on TT? I did come across this post but wasn’t able to successfully single out the jitter function.

#932

thanks for this, it has only happened once and it’s gone now. The screen doesn’t appear to be detached in any way, but I’ll keep an eye on it :grimacing:

1 Like
#946

Since it is now buried in the “New to Monome” thread by a modprune, here is my simple CV recorder, which is forming the basis of a very fun joystick-driven patch today:

Script 1 (arm record while high, disarm and reset sequence on falling edge):

IF ! STATE 1: X 0; P.I P.L
IF ! STATE 1: BREAK
IF X: BREAK
P.I 0; P.L 0; X 1
P.MAP: 0

Script 2 (trigger advances clock):

IF && X STATE 1: $ 4
IF ! OR X STATE 1: $ 3

Script 3 (playback function):

CV 1 P.NEXT

Script 4 (record function):

J IN; P.PUSH J; CV 1 J

Init script:

$.POL 1 3; X 0
6 Likes
#947

Hi Everyone ! I would like to know if there is a script for copy the « sending » TR 1-4 and CV 1-4 teletype outs to the ER-301 by i2c ?
That’s for not changing line by line the outs of the original scene

> teletype : code exchange
#948

Hi @Mad86,
I don´t think there is a general solution to copy all TT´s outs to redirect to ER-301 as this is not the way how TT is programmed. In such cases I change or add the SC-commands to the code line by line. As the scripts are by its nature not such big, it takes usually not very long to change a script.

#949

Hi @KitKatAndy !

Thanks for your reply. So, ok it’s the only way I was thinking about.
Maybe it will improve…
It can to be cool to have the possibility of setting it in a init scene…

#950

that was the main idea behind this proposal: NOTE teletype op

1 Like
#951

Have you looked into Ansible’s i2c leader mode (new in v3.0.0)?

1 Like
(Teletype) CV from Ansible while running Kria on TT