#162

45 minutes into my new teletype and am having a blast. Currently working on my dream ASR (which will have a bunch of trigger-based variations): a total personal-joy project. But just working with it for a bit makes me want to beg for an operator addition: something that is could be something like T.FIRE 1-8, and would be used to simulate the firing of an incoming trigger.

This would allow me to have four triggers each do a thing with a set of TR/CV output, but also have the metro fire any or all of them without duplicating the logic (which might be tough to fit on 6 lines of code). I’m assuming I didn’t miss anything that would allow this, right?

But dammit, I’m having fun!

[ddg]

2 Likes
#163

Hi all i was hoping you guys can help me out with this script. Basically its a simple knob recorder for pattern data, turn the parameter knob to generate numbers for a pattern. My problem is i cant figure out how to lock the values until the next time i want to generate some new pattern data. here is my code;

M:
TR.PULSE A
P.N 0
P.L 6
P.INS RAND 6 RSH PARAM 10
CV 1 N P.NEXT

I would like for the values to remain until the next time i twist the param knob… I realize i could do this with a manual gate or something like that but i was wondering if there is a more elegant command to achieve this functionality. :anguished:

#164

This would works i think:

I:
P.0
P.L 6

M:
X RSH PARAM 10
P.N 0
P.NEXT
IF GT X 8 : P.HERE TOSS
IF EQ P.HERE 1 : TR.PULSE A

So if you turn PARAM past 12’ the pattern will constantly change. Below (?) 12’ the pattern will loop. ( i think )

2 Likes
#165

Thanks a lot for this! I’m going to try it now :smile:

#166

No problem, let me know if it works as expected :blush:

#167

Superb! it works really well thanks M4R71N… I had to tweak it a bit as toss was just giving the pattern 1’s and 0’s and for some reason the bottom IF command seemed to be slowing M down. This code has the desired effect(although not getting the values from the param knob as i originally intended, PARAM after P.HERE goes crazy and does not limit the range);

I:
P.N 0
P.L 6
M 80
M.ACT 1

M:
X RSH PARAM 10
P.N 0
CV 1 N P.NEXT
IF GT X 8 : P.HERE RAND 12
TR.PULSE A

Would you mind helping me understand what is happening with the IF X greater than command here?

1 Like
#168

Oh ok I thought that you were only interested in rhythmic patterns. The IF lines set that turning PARAM past 12 o clock will activate the “random note mode”. Where you expecting something else for the PARAM knob?

#169

looking for some help!
using the drunk pattern code to move through a scale:

P.I ADD P.I RRAND -2 1

question: how i can prevent this from wrapping, so when it gets to one end of the pattern it starts to work it’s way back down/up? i have P.WRAP 0 enabled, but sometimes the playhead escapes…

#170

agreed and this has been discussed before. it’s on the git wishlist:

1 Like
#171

P.WRAP only applies to P.NEXT and P.PREV

try:

P.I WRAP 0 32 ADD P.I RRAND -2 1

so you’re wrapping before assigning.

#172

This works exactly as I wanted now. I just thought initially I would get the note values fro the PARAM knob. Ahh right so the first code you gave me generated rthymic patterns with TOSS. So in this example would the 1’s and 0’s be the gates of the pattern?

#173

Yes exactly, 1 = trig and 0 = mute step

#174

This is great fun! Just using that code to generate rhythmic parts, excellent for self patching… Thanks again for the help, The IF GT and EQ commands here have finally sunk in too! Much appreciated M4R71N!

#175

ah makes that makes sense. i had to split that line in two (it froze TT), but otherwise it worked great. thank you!

#176

Awesome - shoulda looked there. Great work, dudes!

[ddg]

#177

Hi,
Just wanted to see if any decision has been made on implementing more scripts or longer scripts? The more I use TT and the more I learn about its potential the more I wish I could squash more lines in! With 2.0 coming I thought I’d check if this is on the cards (I checked github but couldn’t see anything there).

Cheers,
Alex

#178

longer scripts, i don’t think so. adding scrolling would make the UI unpleasant in my opinion.

but more scripts, this is a possibility. they wouldn’t be linked to hardware, but they could be “auxiliary” scripts, given i’ll be adding a soft SCRIPT command to trigger another script. what’s slightly frustrating, though, is that scrolling (brackets) through the script list will get longer. so i may need to implement some hotkey to jump directly to a script? also, when the scene size grows, we may push up against the flash limit of scene storage-- so i may need to reduce the total scenes from 32 down to 24 or something.

1 Like
#179

This sounds fantastic!

#181

Is there a way to reset a pattern (remove all values)? I tried L 0 P.L : P.RM I but that doesn’t work. It would be nice to have a simple command like P.RESET.

#182

Maybe looping a push of value zero 64 times ?