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

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

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

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

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)

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

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

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:

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

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

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

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

2 Likes

same here :frowning: 20 char

thanks for this Is there something similar to this for mac?

there are a lot of ways using builtin shell tools.

here’s one with sed

sed $'s/\x0d//' windows.txt > unix.txt

macOS uses LF (0x0a) just like unix.

in the bad old days, os 9 used CR (0x0d)

windows did, and does, use both (0x0d 0x0a)

so that command just deletes all instances of CR.

2 Likes

forgive my ignorance here but how do i perform this?

Topic: Little Companion

I have coded a scene for wanderers. In attached zip please find a manual, a code explanation and two versions of the scene (one for internal sequencing which is the main and one for external triggering only). Feel free to try it!
Little Companion_1.00.zip (6.0 MB)

Did a short demo video for a fast overview.

Loose ideas to think about to implement:

  1. Currently its a 2D+ X/Y-Sequencer. Would it be possible to increase to 3D+ X/Y/Z-Sequencer with this left empty $5 and some mods?
  2. “spacetime curvature” possible then in a sequencer cube?
7 Likes

great documentation, and looks very interesting! for more context, it’s a “CV Controllable / Feedback Matrix Sequencer” inspired by make noise rene.

added it to the codex page!

1 Like

This looks really fun, and I’ll second the great documentation comment! Looking forward to trying it out.

2 Likes

Thanks Joe for your support!

@scanner_darkly is there an issue with loading pattern numbers? With fugetta_transp.txt every function works as it should but only the amounts for the note scaling are loaded wrong. I never mind. But if this is an general issue it should be investigated. Neg. values were translated from note values to absolute numbers. Running v3.2.

2 Likes