RedMst, RedTrk, RedTrk2 and RedSeq are a set of SuperCollider classes that I now finally cleaned up and released. I wrote them about a year ago and have been using them for live performances since then. They function as sort of a timeline and the basic idea is to sequence code in a very simple way.
The master keeps track of when some tracks should play and then switches them on/off with .play and .stop at the right time (next quant beat, default= 4). A track can be any code that responds to these two messages (Pbind, BBCut2, Pdef, Routine, etc).
redMst is distributed as a quark. See Quarks help file for more info on how to install.
Quarks.install("redMst");
and then recompile SuperCollider and open the RedMst help file.
Screenshot of the RedMstGUI3 example...
But RedMst can of course also be used totally without any GUI.
I have constructed a wireless sensor system for my performance costume. It has 2 accelerometers (3-axis ADXL330, SparkFun - same as in the Wii remote I believe) and 4 switches (digital). Both receiver and transmitter use a microcontroller (ATmega8, Atmel) and a transceiver (Mirf v2, SparkFun).
Below is a short video, some pictures, SuperCollider classes and also the schematics and the complete firmware if you want to build the thing yourself.
tn8 and I started weekly meetings for people interested in interactive sound programming using SuperCollider. Here is our wiki with example code and discussion forum. Much of it is in Japanese but the example files should have comments in English.
We meet every Friday at 17.00 for a ~2h session. 2nd floor, new building, IAMAS, Ogaki. Open for everyone.
I wrote a Max5 to Max4 patch converter in SuperCollider. The reason was to get more people to install SuperCollider. So this is software with a hidden agenda.
Download it from the page: /code/sc/#classes. See the readme for installation instructions and info on how the conversion works.
It can also be used to generate, examine, manipulate and process Max5 patches in different ways. Below are some screenshots of patches from the max-examples folder that I manipulated using this class. They might look strange but are fully functional. I just did things like add curly segments to all the patchcords.
In June I cleaned up and released my red-framework for managing MaxMSPJitter patches. It is hosted at code.google.com/p/red-framework/ and you can get it via anonymous SVN checkout.
The framework is for stacking, chaining and mixing MaxMSPJitter patches and shows my way of organising patches. I've been working on/with it since 2006 and it now contains >100 modules. It can handle Jitter, control data, MIDI and also SoftVNS video under Max4.5.
Welcome to join the project if you are interested. It is easy to write your own modules.
Installation...
(for OSX 10.4 and earlier you'll first need to install SVN separately)
In June I compiled my tiny collection of plugins for Psycollider. (RedPhasor, RedNoise, Bit, Slub, Atari2600, Pokey etc.) They are available as separate downloads on this page: /code/sc/#plugins.
Extract and put in your userExtensionDir, recompile. Now the RedXM and RedMOD classes also work as they depend on RedPhasor.
And for reference here's my way of compiling UGens under Windows XP...
About letting the computer generate SuperCollider code automatically... Stefan Kersten made a very nice plugin for SuperCollider. It's called FM7 and implements a 6x6 phase modulation oscillator matrix. While trying it out, I wrote some code (pasted in below) that automatically generates parameters for it. So every 8th bar it'll construct a new patch around the FM7. In these patches, the FM7 parameters are UGens with random frequency, phase, range and offset.
At times, I start the generator, lean back and listen. When something good catches my ears, I copy the generated code from the post window. Here are some ok ones I've collected... n_fm7patches and below are MP3 excerpts of the same. But the best ones I, of course, keep to myself.
By randomly generating patches and synths like this I lose a lot of control and time listening to all the generated patches. Most are crap sounding. But on the other hand, the blind randomness sometimes comes up with so strange rhythms and sounds that I never would've been able to think of myself. And the time lost could be minimised using, for instance, genetic algorithms or other types of searches in this huge parameter space.
s.boot
//--more repetitive 2ch instant clicks 'n cuts with code generation /f0
//when you hear something you like, you can save it by copy&paste from the post window
(
Routine.run{
var syn, time= 16; //allow each patch to run for 16sec / 8bars
inf.do{|i|
("\n//fm7 patch"+i+"generated on"+Date.localtime).post;
syn= ("
(
var x= #"++({{{1.5.linrand.round(0.5)}!4}!3}!6).asCompileString++";
var y= #"++({{{1.5.linrand.round(0.5)}!4}!6}!6).asCompileString++";
{
var ctls= x.collect{|a| a.collect{|b| LFSaw.kr(*b)}};
var mods= y.collect{|a| a.collect{|b| LFSaw.kr(*b)}};
var chans= #[0, 1];
FM7.ar(ctls, mods).slice(chans)*0.5;
}.play)").postln.interpret;
time.wait;
syn.free;
};
};
)
A fire patrol rehearsal (i think). I enjoyed watching it more like a modern dance piece. It went on for a full hour and looked very strange. It seemed more important how you moved than what you did. as you can see in the video clips below, when they finally roll out the hoses it's very quick and efficient. But then they spend a lot of time rehearsing this odd positioning. nice choreography in any case. I really wonder how it works out in a real-life fire/chaos/danger situation.
