#276

glad you like the script :slight_smile:

i think it should be possible to move a few lines around so that you can run everything off of an external trigger source by triggering script 1 instead of using the metro script, but unfortunately i’m unable to test out any changes to the script on my own system for a few weeks.

i suspect that it might be an easier fix to clock your main system from one of teletype’s trigger outs by adding a line to one of the scripts.

if you can’t find a solution that works for you in a couple weeks send me a PM and i’ll try to take a closer look.

2 Likes
#277

thanks so much for the explanation, i’ll try to understand the workflow of the script first, and then will try to apply your suggestions, this is a good opportunity for me to learn more about the teletype language.
will let u know if i get stuck :sweat_smile::pray:t4:

thank you!

#278

just want to clarify, am i right thinking, if i want to use external clock as master clock, use it to trigger script 1, so i have to move all the information from Metro script to script 1, and then fits the information from the original script 1 into another script, and then calling that other script from script 1? and i won’t use the Metro script at all?
since i don’t have TELEX, i’m thinking i can erase those lines that use TELEX for offset, so i can free up some script…

for the alternate, teletype as master clock, sending clock from one of the trigger out, right now on the script, TR and CV out sending exact copy of notes from the Pattern (4 melodies).
since i’m using Just Type, i could just erase one line from script #4: IF G.BTN.V: TR.P X; CV X N I. (i’m guessing variable X assign to the notes pattern)
and then let say maybe assign TR.P 4 to Metro script?
but, what if i still want to have the exact copy of notes/gates on TR and CV out 1-3, but only use TR 4 as a clock out, is it possible?

#279

there are a few ways to approach this, but moving relevant lines out of the M script to script 1 and then editing things around is the first thing i’d try. you don’t need to take everything out of the M script—most likely you only need to take the first two lines (with a few edits) to get basic functionality, or lines 1-3, 5 to try and recreate the reset functionality (might be a bit strange with an external clock). so yes, in this case you wouldn’t use the M script because it would not be in sync with your external clock. depending on what you want to do it might not be possible to fit everything.

sending a clock from teletype could be as simple as adding a TR.P 4 to the M script, but then you would have to alter script 4 to remove the TR.P, which is tied to the X variable. without a more careful look i don’t know if there is an easy way to get TR and CV outs 1-3 working the way you describe with a clock on TR 4.

it might be helpful to look at the comments on the original script as a reference if you haven’t already:

2 Likes
#280

thank you so much Jhonathan, that certainly helps a lot! i’m gonna try to work on that now.
and yes, i was also referencing the comments from the original script, been studying it for few hours now, trying to understand how everything works. its really is a complex and clever programming, learn a lot from it. thank you @jflee and @ghost for the great script!

2 Likes
#281

Another approach may be to flash the latest beta firmware here:

This firmware adds the ability to trigger the Metronome script with $9, which may help!

2 Likes
#282

oh wow, i didn’t know that. thank you for the info!

#283

Guys, I hate to ask, but could I get a basic explanation of how these scripts are notated? We can use something like @MengQiMusic’s wonderful “wanfeng” script. I get the basic parts (scene #1, 2, etc). I also get a general gist of the patterns, but I’m curious, with the section as follows:

Is this refering to the pattern Loops?

And then with the grid layouts bellow. What do those notate? I see there are two of them, but I’m curious how they break down… If someone could break me down a simple “what the heck” I would really appreciate. I’ve looked all over and it seems there isn’t a simple explainer to the notation style we’ve landed on.

#284

It’s the format saved and loaded to USB disk when you perform a scene backup using the procedure described here. So you can grab the scene straight from such a post, put it in a file on a USB drive, and load it into one of your Teletype scene slots, or capture a scene to a file you can share. You are correct that this is pattern data and grid configuration at the end, I don’t know if this format is currently documented anywhere but you can find the code for writing and reading scenes here.

1 Like
#285

Oh wow! Very cool. Okay, thank you very much. This makes for a wonderful tool. Much appreciated!

#286

Did you ever happen to continue work on this? This seems like an amazing tool for the teletype/grid ops.

#287

Finally sharing this! I call it “STTS”
STTS.txt (1.5 KB)

I designed this script for the STS, although it should work with other samplers with little or no modification.

It uses two adjacent Earthsea-style keyboards to trigger the respective left and right channels on the STS. There are two faders to select samples from the currently loaded banks. There’s a momentary reverse button for each side as well which I have found to be great fun to toy with.

The most interesting thing I discovered while working on this became an unintentional feature:
pressing multiple buttons at once on one channel’s keyboard can give more granular control of where the sample playback starts, so while there’s only 48 buttons on each keyboard, you can get way more positions by playing around with different combinations. I want to say it’s because of some slew that is applied on the STS’ start position inputs–so this part may not work on other samplers. Would love to hear from others about it!

Lastly wanted to ask if @scanner_darkly or others ever made any progress on building a pattern recorder into their scripts. I’d love to implement here if anyone could share their insights!

4 Likes
#288

this is great, added it to the code exchange page!

teletype is great for controlling other modules as you can be more precise / create complex gestures etc, but combined with grid especially so.

re: pattern recorder - you mean like mlr style? or something else?

1 Like
#289

Awesome thanks :slight_smile: 4ms modules are super fun to pair up TT with. Earthsea for SWN is a great project to mess around with.
And yep, pattern record just like MLR (and Earthsea as well I believe)

#290

Topic: 32-step sequencing without meta pattern

Hello,
just like to share and get some feedback for optimizing/expanding my first scene created for kira. Im a bloody beginner in teletype programming so Im sure there is plenty of space for improvement :slight_smile:.
First I would like to refer to my feature request in another thread. After all I decided to create a workaround with tt.

The scene can simply chain track 1 and 2 to a “32-step track” and you can manually switch on the grid between track 1 and 2 as usual for editing first 1-16 and second 17-32 steps without automatic switching between patterns, which I often prefer while composing, compared with the workflow with metapatterns - which of course also does a great job in a lot of live usages. CV of all notes will be redirected to tt`s CV1. Beside this you also have the ability to adjust the clock speed (even to zero for stopping) with the param knob. (Triggers from Ansible could be also summarized and outputted from TR 1 of tt in $ 1)

As it`s only a simple workaround with some disadvantages I like to read your ideas:

  1. Longer or continious data (like glide) cant be emitted of tts CV1 as it is only a momentary rec. of ansibles CV1+2. Is there a possibility to continiously forward those data or am I forced to solve this outside the monome ecosystem?
  2. There could be done some other improvements like simple adjusting the complete length of track 1 and 2 via scripts. (Of course you would have to change the lengths manually for kira as well.)
  3. You are welcome for other thoughts.

It`s perhaps not worth at all, but it was fun and interessting to me that I could realize this behavior by myself…

KIRA: START+STOP 32 LENGTH

#1
SC.CV 1 ADD KR.CV 1 KR.CV 2
CV 1 ADD KR.CV 1 KR.CV 2

#2

#3

#4

#5

#6

#7

#8

#M
M SUB 1000 RSH PARAM 4
IF > PRM 50: TR.P D P.NEXT
IF P.HERE: KR.MUTE 2 1; $ 1
ELSE: KR.MUTE 2 0; $ 1
IF P.HERE: KR.MUTE 1 0
ELSE: KR.MUTE 1 1

#I
TR.TIME D 5
KR.POS 0 0 0
P.I 0
P.L 32

#P
32 0 0 0
1 1 1 1
0 0 0 0
63 63 63 63

1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0

#G
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

tt30s.txt (1.2 KB)

2 Likes
#291

Very cool that you were able to script something to get closer to what you wanted, extending or modifying apps’ default behavior with Teletype or crow is a very exciting idea to me.

The way to do this would probably be to have a Teletype op to read the current slew value and adjust Teletype’s CV.SLEW according to that. In the current beta firmwares you can get the duration with KR.DUR but there’s not yet a KR.SLEW. Ansible can’t really stream values to Teletype, Teletype asks for a value and then waits for Ansible to respond, and Teletype can’t really do anything else (run metro scripts, update DACs, execute delayed commands, process keyboard input) while it’s waiting for a response.

I also frequently want to do something like this when using metapattern mode, will have to think some about possible UI and implementation.

2 Likes
#292

Hi scanner_darkly,
I just wanted to try some of the amazing scences which were done by the community over time and you have linked: https://github.com/scanner-darkly/teletype/wiki/CODE-EXCHANGE
Some of those I think are broken (due to firmware update of tt)?
I didn`t tried every scene but those are broken:

rené emulator
16 patterns for er-301
pressin’ pals (pressure points emulation)
fugetta (multihead sequencer)
earthsea style polyphonic control
rhythmicon emulation
st8p
4-track, 16-step trigger/CV sequencer

…and also those 3 from here:

orca
turning machine
txi markov

Here is also an example how the scene name is shown for some of those:

image0
image02016×1512 514 KB

If I`m right and the newer firmware (I run 3.x) is the reason, would it be perhaps simple to fix the older code in those scenes for a newbie like me to give them a try?

Thank you for your support!

1 Like
#293

the issue here is line breaks - teletype does not properly load scenes saved with windows or mac style line endings. if you copying and pasting scene text using a text editor it will use whatever is the standard for your system.

you can use something like notepad++ to fix it - open a scene file, then do Edit -> EOL Conversion -> Unix (LF) and save. it should load with no issues after that.

6 Likes
#294

NR Grid Visualizer

This is a 4 track grid-based implementation of the NR numeric repeater op in teletype firmware 3.2+. It allows for visualization and control of the generated patterns.

The scene outputs four tracks of trigger sequences on TR 1-4, and outputs these same sequences over the ii bus to the ER-301 ports (SC.TR 1-4). The sequences are calculated using the numeric repeater NR op. The scene also gives control of the input params for numeric repeater.

ROWS 1-4: Visualization of the trigger pattern for each track 1-4. (no interaction)
ROW 5: Clock/step indicator (no interaction, timing from metro)
ROW 6: Factor [0-15] (per track)
ROW 7: Mask [0-3] (per track)
ROW 8: Track select [1-4] (controls which track’s Factor and Mask faders are visible in ROW 6 and 7)
PARAM: Prime [0-31] (shared by all tracks)

You can watch a demo/howto of the scene in the first seven or so minutes of Teletype Talk Episode 8.

NR Grid Visualizer.txt (1.6 KB)

12 Likes
#295

this is awesome! a great example of using grid control to make something like NR more immediate/visual.

2 Likes