this is new territory. i take it that you are triggering many inputs with the same trigger using a mult?

i’ll need to do some testing to confirm, but i’d expect the scripts to be executed in order-- ie, 1,2,3,4… if they all get the same trigger. if this is in fact not the case, it may be very difficult to hack the code to ensure execution order-- this is a bit of an electrical race condition.

I posted the scene in the code sharing thread. I made the first calculation with script 1 and it seems to work… you may or may not like this use of the PARAM to set two variables in a manner more useful (methinks) that just if X goes up, Y goes down, although that is part of it. Found an excellent use for MOD, also… and use for METRO as an aux script…

If we could have multiple PREs per row, then a simple DEL applied would ensure correct order. Even better, I think would be to have a “DEL everything below” command

with v2 when i add SCRIPT (calling one script from a command) being able to DEL SCRIPT x will be great.

1 Like

Hi, here is a little patch build around a " complex evolving sequencer " script on the Teletype. :kissing_smiling_eyes:

9 Likes

Is there a way to read values from the trilogy units? For example, the current pattern playing on white whale or the total number of patterns. WW.PATTERN returns 23 for some reason.

not at the moment, but @tehn said it might be supported in the future. would be a great feature to have!

23 is the “machine code” of the WW.PATTERN command itself.

1 Like

Right on. Good to hear it’s on the roadmap!

@tehn one for the v.2 list?

when feeding the DEL pre a value of 0 the result is no action. not sure if this is intentional. my solve is to make sure i feed it a value no less than 1ms, but being able to say 0 DEL would be nice.

Teletype!

Top 5 of 2015!

https://www.muffwiggler.com/forum/viewtopic.php?p=2097761#2097761

3 Likes

I was a bit surprised, not because it doesn’t deserve to be in the top 5 best eurorack modules of 2015, but because I didn’t think that many people would vote for it. But if I had voted, I would have definitely included it.

It surprises me as well. It’s just that i have the feeling that TT doesn’t really encounter the success it should. There are not so many vids or pictures or songs out there mentioning TT. According to me, TT is the most innovative and powerful module since i got into eurorack.

Hi

i am struggling with a little problem. Can someone be so gentle and tell we why this doesn’t work

1:
CV 1 IN
TR.PULSE A

With every Pulse, TT should read the Voltage on the IN-Jack and set CV 1 to it.
my problem is that the voltage on CV1 will updated on Pulse after.

Let me explain:

current behavior:
Step 1 : In=2092 CV 1 = 0
Step 2 : In=8640 CV 1 = 2092
Step 3 : In=1316 CV 1 = 8640
Step 4 : In=3540 CV 1 = 1316

expected behaviour:
Step 1 : In=2092 CV 1 = 2092
Step 2 : In=8640 CV 1 = 8640
Step 3 : In=1316 CV 1 = 1316
Step 4 : In=3540 CV 1 = 3540

cv input is polled on a timer, so CV 1 IN will output the value of in anywhere between 0-40ms late.

add a delay to the second line:

DEL 40 : TR.PULSE A

you may need to fiddle with the delay time.

it works, thank you.

Marcus

Is the polling timer that long ?
It means that keeping timing between a part of the patch using sampling values in TT and a ‘rest of the modular’ part of the patch would not be tight ?
That would explain a lot.

i’ll check the exact timing. i may be able to change firmware to do on-demand sampling of the ADC, but that seems like a less-good idea for maintaining quick execution of scripts. ie, sampling the ADC at super-super high rates would eat most of the CPU. polled ADC sampling keeps the system smooth.

Alright.
I love using TT to process cv from a sequencer, trigged with the same clock as the sequencer. So timing is critical in these situations.

Blast from the past…
but i was just re-reading this thread, and think this ECHO idea is cool.
Could be very useful and quite musically exciting.
so simple too!
one short line, that could pack a lot of rhythmical interest…

ECHO )) echo )) echo ))