MaxPat - max patch parser, converter, manipulator, generator

i wrote a max5 to max4 patch converter in supercollider. the reason was to get more people to install sc. so this is software with a hidden agenda.
download it here. 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 patchlines.

red-framework published on googlecode

in june i cleaned up and released my red-framework for managing max/jitter patches. it is hosted here and you can get it via anonymous svn checkout.

the framework is for stacking, chaining and mixing max/jitter 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 the terminal type:

svn checkout http://red-framework.googlecode.com/svn/trunk/ red-framework-read-only

then press (p) to accept permanently.
last add the red-framework folder to max's file preferences.

it is licensed under gnu gpl v2 and requires max5+jitter for osx. it has not been tested on windows xp yet but should run.

concept...

modules: generators, modulators, outputs
faders: cross, gain, etc.
slots = module+fader
chain = slots in series
stack = slots in parallel
mixer = go from parallel to serial

//--module:
a max/jitter patch following a simple standard
it must have 2 inlets: in, ctrl
and 2 outlets: out, info
the module can be generator, modulator or output

//--slot:
a slot is a fader + a module
slots also have 2 inlets: in, ctrl
and 2 outlets: out, info

//--stack:
builds a stack of slots - serial in and parallel out

//--chain:
builds a chain of slots - serial in and serial out

//--mixer:
a mixer of slots - parallel in and serial out

pros and cons...

why use red-framework?
same for jitter, midi, controldata, softvns
reusable patches
generalised and efficient

i have made various bigger performance patches using red-framework
special gui/bpatchers for stacks, chains, mixers

drawbacks?
only discrete events - no msp
no opengl or shaders
too complicated to perform with
went back to my old os9 patch
eg. learning the effect chain - not re-ordering!

my plugins available as windows binaries

in june i compiled my tiny collection of plugins for psycollider. (RedPhasor, RedNoise, Bit, Slub, Atari2600, Pokey etc.) they are available as separate downloads here
extract and put in your userExtensionDir, recompile. now the RedXM and RedMOD classes also works as they depend on RedPhasor.

and for reference here's my way of compiling ugens on xp...

1. install mingw (automated installer 5.1.4). add g++ support.
2. install pthread (2.8.0). put it C:\pthreads-w32 or modify the path below.
3. download sc source and put it C:\SuperCollider-Source or modify the path below.
4. open command promt and cd to your plugin directory.
5. g++ -shared -Wno-deprecated -O3 -Wno-unknown-pragmas -DSC_WIN32 -D__GCC__ -D_REENTRANT -DNDEBUG -DSC_MEMORY_ALIGNMENT=1 -IC: \SuperCollider-Source\Headers\plugin_interface -IC:\SuperCollider-Source\Headers\common -IC:\SuperCollider-Source\Headers\server -IC:
\SuperCollider-Source\libsndfile -IC:\pthreads-w32 C:\SuperCollider-Source\windows\PlugIns\ExportHelper.cpp -o RedPhasor.scx RedPhasor.cpp

n fm7 patches

about letting the computer generate sc 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 loose 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 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;
        };
};
)















































































june practice sessions -again

finally rendered mp3 excerpts of my 31 one hour practice sessions from last year. music quality varies... but the code and history files are still available here.
































Pages

Subscribe to f0blog RSS