#264

Oo that’s a fun idea as well! This would make it easier to have small bursts of rhythm, which I think would be pretty fun. I definitely don’t make use of the stack often enough.

Can’t wait to try out some of these ideas tonight and report back :slight_smile:

2 Likes
#265

i like to add delayed secondary hits with a very low probability. so you get a lil extra something every now and then.

6 Likes
#266

Let thing be pretty loose on a per-trigger time basis. Using a variable to accumulate error, you can occasionally use a beat to “pay off” part of the accumulated error. To avoid paying it all back on beat 128, you could pay it off (part or all) whenever error exceeds a particular threshold.

EDIT: Alternatively, work “one tick behind schedule” with a steady METRO script setting up the next tick on random delay. Instead of accumulating error, now you’ll just constrain how far off each beat is allowed to be.

2 Likes
#267

Is P.RM one-based? I’m going through the Teletype studies 5 and after doing P.INS 0 5 and P.INS 0 6, the tracker page is showing 6 at the row 0 and 5 at row 1. If I do P.RM 0 though it first removes 5 and then 6. With PN.RM 0 0 it returns the correct order though.

Edit: Actually it’s not even that, if I do P.PUSH 5 and P.PUSH 6 and P.RM 0 twice it returns 6 first and then 5 so it seems like P.RM is actually working backwards?

#268

I believe P.RM has been fixed in the new firmware which has just been released today.

Relevant bugfix:

https://github.com/monome/teletype/issues/149

Also:

https://github.com/monome/teletype/issues/150

1 Like
#269

Ha I was almost certain it was user error, I’ll install the RC. Thanks!

#270

Just had some time to test this out further. I’m trying to determine via IN which script I’m going to run, using my keyboard as a selector.

A GTE IN 1000 // just a random cutoff point, 1000 seemed like it’d work
DEL 100: SCRIPT ADD A 5

^This doesn’t work. I have to go up to DEL 400 for the scene switch to trigger reliably. Still Cirklon as CV source… Any ideas? I can’t believe my Cirklon slews CV by 400 ms. (Slew is off for that CV output)

#271

Followup on fluctuating tempos:
I went with a simple delayed trigger approach, and although it didn’t sound all that interesting with the Volca Beats, I had a lot of fun with it triggering AD envelopes controlling some sounds out of 3 Sisters and modulated by Just Friends.

I ended up just using 2 scripts:

1
X AVG T TIME
T TIME; TIME 0
SKIP 16: SCRIPT 8
OTHER: TR.PULSE 1

8
A B; B C; C D;
D MUL RAND 32 DIV X 32
DEL D: TR.PULSE 1
DEL C: TR.PULSE 2
DEL B: TR.PULSE 3
DEL A: TR.PULSE 4

Basically I created kind of a shift register, so the there’s 4 different but related randomized rhythms getting created. Also, every 16th beat fires normally, to stay somewhat grounded on the beat.

I had a lot of fun with this, but I have 4 CV outs and a lot more scripts to make use of, so I want to expand this further. Maybe I should use the PARAM knob to control what divisions of the beat are possible? Any other fun ideas?

EDIT: Just realized I never revisited Script 1 after adding the other 3 rhythms, so I’m skipping every 16th beat for 2-4 entirely. It didn’t sound bad, but I’ll probably change that later :smile:

4 Likes
#272

Does anyone use any microtonal scales with Teletype? Would love to know how you’re using them. One thing I would like to do is create a simple quantizer with say a just intonation scale- what is the easiest way to do this?

2 Likes
#273

i don’t use microtonal scales - but i have made a quantizer. i can’t write the script out now, but the gist is:

  • write your scale in one pattern
  • scale whatever you’re reading (param, or in) to a range equal to total number of notes in your scale
  • on trigger read the current scaled value as the index of the pattern with your scale in it

as for writing out a microtonal scale - i dunno -but i’m sure soemone here does :slight_smile:

3 Likes
#274

Thanks a lot for spelling this out @shellfritsch! I will try experimenting with millivolts in relation to cents and see what I can come up with.

#275

One of the Teletype studies does just that (i.e. explains how to use patterns to define scales).

#276

Ok awesome! I’ve only gone through the first three, so I will scan/ try to finish them up.

#277

It’s in the 7th one :
https://monome.org/docs/modular/teletype/studies-7/

1 Like
#278

Hmm, is a quantiser a tool that provides a note value/voltage based on an index, or a tool that rounds an incoming voltage to the nearest note in a scale? The solutions above solve for the former definition, I think that it would be easy enough to solve for the other sense by using two columns of the patterns as a lookup table, and spin through the first column based on an input voltage, and use the second column as the lookup.

1 Like
#279

Quick example quantiser. Pentatonic minor.

4 Likes
#280

Thank you @GoneCaving!!!

#281

Hi, is it possible to program the frequency intervals in a sequence?
let’s say I have a cv sequence of 5 notes and I want to
play the 1st then then the 2nd after 20 sec the 3d after 1 min etc…
Thanks

#282

Two ways i would think about doing that. Either way, store the note values and intervals in a pattern. Then either have a script play the note, advance the pattern, and call itself with the interval using DEL. Or, have the script called from the metronome, and have the script change the metronome interval.

2 Likes
#283

I just performed a show where I controlled three voices from the modular and played guitar. Thought this would be a good place to share how I used teletype to make that happen.

First, I tuned each of the voices to a pitch and kept that the same throughout the performance. I then took every song and found (up to) 4 notes that would randomly cycle (using the N operator) based off the root note of the voice that would be in key for each song. So the patterns look something like

// for song 1
0 2 3
2 5 3
6 8 3
7 2 0
// for song 2
1 4 5
4 7 6
3 2 0
8 2 0
// etc....

I then had a param knob that I scaled down to correspond to each of the 8 songs that were part of the set. I made use of RRAND to choose notes (1 + n) - (4 + n) of the pattern, where n was the knobs position multiplied by 4. In other words, for song 1, it would pick from notes 1-4, 2 from notes 5-8, etc.

I also used the position of the knob to pulse the trigger outputs (and thus flash the led) so that I could tell which position the knob was at rather than just guess. Trigger out 1 would flash for songs 1 and 5, 2 for songs 2 and 6, etc. I did this by using the modulo operator to “wrap” the sequence to the 4 leds I had access to. My param knob was 0-7, so ADD MOD PARAM 3 1 will convert that to 1-4 wrapping.

This LED flashing ended up being a really smart idea, because the knob I used was on the TXi, and had some i2c feeze-up a couple times. I knew if I didn’t see an led, I needed to power cycle! :slight_smile:

I’m glad I took the time to do this rather than try to manually tune the oscillators between songs (which would have been a lot more stressful). Before the next show I want to add some sort of calibration position to the param knob so that I can tune the oscillators and not be paranoid when transporting the system that a knob is going to get moved and mess things up!

15 Likes