#8

That was my idea also.

There are triplets and duplets in the Barton pattern. Hard to get to where needed with integer-based math?

#9

@tambouri I spent some time TT’s eclidian rhythm operator last evening. Really fantastic for generating all sorts contrasting patterns. I will definitely continue to explore, but I was not able to generate triplet patterns.

If I understand correctly, triplets may not be a part of this system.

#10

It depends.
If your smallest triplet value is 10ms, the smallest duplet value can be 15ms and there is no prob. Depends on the tempo you want to use, though.

#11

I broke down the Barton pattern into ms values for each note length, with a base tempo of 60 BPM.

So a quarter note would be 1000ms. Triplet eighth note = 333 and triplet sixteenth = 166. For both triplet types, a bit of math fudging would be necessary to get on solid tempo. For the triplet eighths, we would need to add 1ms to 1 of the triplet parts. For triplet sixteenths, add 1 to 2 parts.

The pattern looks like:

1000
1000
500
500
333
334
333
250
250
167
166
167
250
250
250
250
167
166
167
250
250
333
334
333
500
500
1000
1000

Now, how to actually get TT code designed to make this work… that’s the challenge.

3 Likes
#12

Ok. I believe I’ve come up with Euclidean Rhythm operator (ER) statements that could work for all but the sixteenth notes in the Barton Palindrome pattern.

The smallest value is a sixteenth triplet, so I came up with ER patterns of 24 steps.

triplet sixteenth - 1, 24, 0
sixteenth - ?
triplet eighth - 2, 24, 0
eighth - 3, 24, 0
quarter - 6, 24, 0

Still left with the sixteenth note being able to fit into the length of a bar comprised of 24 steps.

Edit: hmm… If I double the number of steps to 48, this may solve the problem. I’m not at TT, but will give this a thorough test later.

2 Likes
#13

I didn’t have time to play with this last night, and now I’m back at my desk at work, but this is how I was thinking you could use the euclidean rhythm generator. Per my reading of the ER writeup and no actual testing on the teletype, so not unlikely that I’m missing something, but … hear me out :wink:

Using a clock 1/12 the length of the desired 1/4 note in your pattern the following could create triggers when the ER returns a 1. and you could shift through a pattern of fill settings every 1/8th of the piece which would be every 6 beats of the 1/12 clock

i believe ER FILL LENGTH STEP would work as follows

so a script might work something like this.

SCRIPT 1
P.N 0
X MOD ADD X 1 12 x counts 0-11
IF EZ MOD X 6 : P.NEXT move to the next pattern every 1/8note = 1/6 of the 12 count
IF ER P.HERE 12 X : TR.PULSE 1 execute a trigger if ER returns 1

So you would now choose a fill amt for every 1/8 of the piece. (1/8 as this seems to be the smallest scale that the division shifts). so you could put the following into Pattern 0 (split up into bars only to make it easier to see my thought process)

bar 1 - 1 1 0 0 0 0 1 1 1/4 note, 1/4 rest, 1/4 rest, 1/4 note
bar 2 - 1 1 2 2 3 3 4 6 1/4 note, 1/8 notes, 1/8t notes, 1/16 notes, 16t notes…
bar 3 - 4 4 6 4 3 3 2 2
bar 4 - 1 1 1 1 0 …

Repeat disclaimer, this is off the top of my head and likely has some issues. 1 thing I’m definitely unsure of is if ER 0 12 STEP would work to fill a pattern w/ no active steps to take into account the rests. And this doesn’t solve for duration yet

3 Likes
#14

Very nice, @tambouri. You came directly to the 1 beat version of what it took me multiplepasses to get to.

Still required is some fancy pattern resetting to get the correct number of note values per full pattern, but that seems doable.

I fear for the squirrel running the clocking wheel, tho. :smile:

2 Likes
#15

Im pretty certain that ER 0 12 works exactly as expected

1 Like
#16

seeing a problem where the order of the commands I used are likely causing it to skip step 0 and advance before the first beat, maybe that’s cause this?

so maybe have a reset script and change up the order of the commands a little

SCRIPT 1 :
P.N 0
IF ER P.HERE 12 X : TR.PULSE 1
X MOD ADD X 1 12
IF EZ MOD X 6 : P.NEXT

SCRIPT 2 :
X 0
P.N 0
P.I 0

PATTERN 0 :
1 1 0 0 0 0 1 1 1 1 2 2 3 3 4 6 4 4 6 4 3 3 2 2 1 1 1 1 0 0 0 0

This way it should trigger the 1st step before moving to X = 1

1 Like
#17

Nope - throws a ‘not enough parameters’ error

#18

This line is a character too long it seems. Drat!

Solved by storing P.HERE in a var Z.

 P.N 0
 Z P.HERE
IF ER Z 12 X : TR.PULSE A
....
#19

I think @GoneCaving is stating that ER 0 12 step should always return a 0. It does. (Or it should, if it doesn’t it’s a bug.)

The C source that underlies the op is here, you can see at the beginning of the euclidean function that it returns a 0 if fill is less than 1.

1 Like
#20

Yep, that’s clearly what I meant. Post was from memory and without checking, but meant that a rest is certainly possible.

1 Like
#21

The scripts @tambouri provided worked fine. I had to make a change for the long line and add an I script to define the pattern length.

Would it be more helpful to edit the top post to include the working code, or just enter it in a post at the bottom?

Thanks to all who helped in this. To me, this opens a lot of possibilities for handling rhythmic structures. Much better than relying on multiple clocking modules to get there. And… only 2 scripts. 6 scripts slots left open to handle the rest of a composition.

Amazing tools…

4 Likes
#22

[quote=“carvingcode, post:21, topic:5188”]
Would it be more helpful to edit the top post to include the working code…?
[/quote]i think so

great topic

2 Likes
#23

And perhaps add a link to this thread to the Teletype code exchange

1 Like
#24

OK, before I transfer the code up top, would you all check this over to make sure it fits into your logic? What I tried to do is modify the scripts so that only one clocking source (jack #1) would be necessary. Do you see any problems?)

SCRIPT I (init):

P.L 32                        // Set pattern length

SCRIPT 1:

Y ADD Y 1
Z P.HERE                      // Get current pattern position
IF ER Z 12 X : TR.PULSE A     // Euclidian Pulse
X MOD ADD X 1 12              // Play out ER
IF EZ MOD X 6 : P.NEXT        // Move to next pattern position
IF EQ Y 24 : SCRIPT 2         // Reached end of pattern

SCRIPT 2:

X 0                           // Init
Y 0
P.N 0                         // Set working pattern
P.I 0                         // Set pattern to 1st position

PATTERN 0 : 
1 1 0 0 0 0 1 1 1 1 2 2 3 3 4 6 4 4 6 4 3 3 2 2 1 1 1 1 0 0 0 0
3 Likes
#25

I’m curious about how you are using the Y value. It seems this might be resetting your pattern earlier than you are intending. As I’m reading it, Script 1 : Line 5 is advancing the pattern every 6 executions of the script, and Script 1 : Line 6 is resetting the pattern every 24 executions, so you would only be getting through the first 4 values in your pattern. You could simplify a bit and just rely on the pattern’s own looping capabilities and eliminate the need to use Y. The scene should work exclusively triggered by Script 1. My thought for Script 2 beyond getting it all in sync was that it seemed a fun addition to reset it at odd times and be helpful in testing, but it shouldn’t be necessary at the end of each loop. I wound up adding it to my init script so that the whole things starts in sync.

I do think script 1 should have a P.N 0 line. If you expanded your scene later and used more scripts and patterns, another script could call a different pattern and you could end up referring to P.HERE and P.NEXT of a different pattern.

I tried the early version out a couple nights back. If it’s any help here’s where I landed:

INIT :
SCRIPT 2                  // sets X and p.n 0 location
TR.TIME A 25              // just a value that worked for me

SCRIPT 1:

P.N 0
Z ER P.HERE 12 X          // this looked a little clearer to me
IF Z : TR.PULSE A
X MOD ADD X 1 12
IF EZ MOD X 6 : P.NEXT

SCRIPT 2:                 // for testing or playful resets

P.N 0
P.I 0
X 0
#26

Thanks, @tambouri. I admit to not testing the Y var usage. The intent was to have the advance and reset be contained in one script.

I’ll take another look when I get back. TT is a great tool that I’m just beginning to learn. My coding experience has all been high level, so still wrapping my head around the single line methodology.

#27

Gotcha, I do believe you should be good to go w/o the Y commands, the way the pattern commands work should make that redundant, but let me know if that doesn’t work for you

1 Like