#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
#952

Ok I need to try it. That sound exactly what I mean. Thank you :pray:t2:

#953

Ok I must to upgrade… thank you :blush:

#954

I would probably recommend updating directly to the latest beta, posted here.

1 Like
#955

sorry - i should’ve been more clear - it’s just a proposal, not currently implemented.

1 Like
#956

Great :+1:t3: cool I will made from here. Thanks again.

#957

Ah ok I was believe it’s rule.
Yes it’s a good idea that you have, I hope it will developed, it can simplify things.

1 Like
#958

I’m trying to add probability to a trigger pattern but my skills are still poor.
Having a simple pattern:
1 0 0 1 0 1 1 0

and script 1 with:
X PN.NEXT 0
IF NZ X: TR.P 1

Script 1 is triggered by metro with $1

How can I add a PROB op to decide to read or not the 1 values in the pattern?

#959

My favored method of adding probability is to generate a random number in a fixed range and move a threshold around within that range. Then random numbers which fall above the threshold can be your triggers. I also shy away from conditional PREs and use the ternary IF operator ? instead, where possible.

But in your case, I’d use PROB Y: TR.P ? X 1 5. There is no trigger 5 to ping, so that gets ignored.

1 Like
#960

First lets do some spring-cleaning, shall we?

J PN.NEXT 0
IF J: TR.P 1

Or in one line:

IF PN.NEXT 0: TR.P 1

You go back to the two line version like this:

J PN.NEXT 0
PROB 90: BRK
IF J: TR.P 1

Or with RND

J PN.NEXT 0
IF && J ! RND 9: TR.P 1

Not sure this one-liner will fit (away from my teletype):

IF && PN.NEXT 0 ! RND 9: TR.P 1

If you set the pattern somewhere else (or don’t change it somewhere else), you can loose the “0”:

 IF && P.NEXT ! RND 9: TR.P 1
6 Likes