More hackery

Trying a lower bpm than normal. Also I’m starting to add more higher order rhythm functions to increase live coding potential… “(~> n)” shifts the pattern one beat to the right, (last one was faked, I’ll take that as a compliment! As Kassen pointed out, that one was mainly just a sequencer. A polyrhythmic sequencer, with sequences for parameter values as well as samples but a sequencer nonetheless. My aim is to try to stay as simple as possible but I’m currently looking for ways of transforming sequences through live coding. This is a step towards that.

Thanks for all the source code requests, I will release the code eventually and announce it here, but might take a while… Sorry.

I might do an opendork showing this stuff at dorkbotlondon tonight. Might not be time though as we’ve got a lot of classy presentations to get though.

I should say I’m not at all opposed to text as a interface to sequencing; I feel sequencers could do with some fresh blood, interface-wise ,now that the demands on them on the interface level are going up with the sequencer often being the main instrument in modern music with live improvisation implied or assumed. One project in the ChucK scene took inspiration from Emacs-style commands to enter data into a sequencer.

The X0X series, after all was meant for practising guitar with and despite some virtuoso performers I do feel that that shows a bit.

Hi Alex, Bob here. Some guys at a Perl(+PHP+…) meeting pointed me in your direction. So glad they did!

To me this is screaming out for an evolutionary algorithm to take care of the pesky typing & learning the syntax issues!

I’ve been generating audio with Perl/PDL and optimising it with genetic programming (also live on web, see the link). I was thinking about a rewrite in csound or chuck but would probably never find the time.

Will definitely check out dorkbotlondon too. I’m gearing up for live performance.