WARNING: somewhat pedestrian newbie stuff ahead. Coding anything is quite new to me. Other relative beginners may find this example interesting.
This will work essentially the same using scales.
Having just read the FLOSS manual section on tables, and based on an earlier example from Iain McCurdy using a function table to randomize notes, I decided to further explore using tables for scales and arpeggios etc.
My previous experiments with arpeggios often used score loops which have certain drawbacks, for example the inability to transpose as easily and especially not being able to alter the colour (major, minor, dominant, adding 7ths, 9ths etc.) without creating specific loops.
This example reads the Note tables incrementally. Instr 1 feeds either instr 2 or 3 depending on the value of p6. I found that, as the tables are read in order by instr 1, that when a new instance is called in the score it starts one increment from the index where the previous one ended, thereby creating a smoother transition between patterns as opposed to always starting on the first note (Root) of the arp.
To better hear the transitions, line 26:
kTrig metro 8/kDur
can be altered from 8 to 6 or 4 to slow it down.
Possibly not the most efficient method or coding but hey, that’s why I’m a newbie. Instr are full stereo,although it wasn’t really necessary, for further experimenting with adding panning etc.
TableArps.csd (2.4 KB)