[Golist] Flashbelt

[Martin Wood-Mitrovski]

Moses Gunesch wrote:
> ah, sounds like a bust then since the talk is on Monday and I would  
> really need the files this week. Sorry to hear that!

ok, i've got something together :)

http://relivethefuture.com/code/flash/mdk-flashbelt-demo.zip

Its built on PPC but I hope it'll work on Intel.

I also built a windows version if anyone wants it :

http://relivethefuture.com/code/flash/mdk-flashbelt-demo-win.zip

In the zip is a standalone application built from Max/MSP 5 and the flash stuff 
(swf, html file, swfobject)

Some instructions for the swf :

At the top left is the 'toolbar' for creating new box types (only 3 at the
moment,but more to come soon).

At the right is the box inspector for altering parameters and configuring the
nodes in a box.

When you create a box you'll see it has its own set of controls, from left to
right :

Inspect : Show box params / nodes in inspector.
Close   : remove the box
Zoom    : zoom a single box to the whole work area

Then the last 2 function as a mini-transport for IPlayable's

Play / Pause and a Stop button (although just play / pause would probably be
sufficient in this case)

----

Max Application

The Max application responds to a set of OSC messages :

/trigger1 : restart sample 1
/g1	  : sample 1 grain time
/ps1	  : sample 1 pitch and speed

then the same for sample 2, /trigger2, /g2, /ps2

/vol	: sample volumes
/reverb : reverb amount
/delay  : delay amount
/filter : filter cutoff (only affects sample 2)

So, how do you make it do stuff?

1. run the Max app, that will start the OSC server on port 4444. If you click 
the speaker button at the bottom you should hear a couple of samples playing.

2. open the app.html (or just the swf)

3. connect some nodes to messages :)

As an example, try this

1. create a new path box
2. click in the grey box for the path to create some nodes
3. in the inspector select the 'nodes' panel

For a path the first node sends messages from the animated node which follows 
the path, the second node is for sending triggers when it cycles,

4. In the first node message box (it says /box/pos) change that to /ps2 and 
click the checkbox next to it to activate it.
You should immediately start to hear some changes.
5. Create a new path, doing the same as before except change the /box/pos 
message to /ps1 (and activate the message)

Now both samples are having the pitch and speed modulated by the animated node.

6. Create an orbit box and make some nodes.

Now the trick with this is to pause it while you configure the nodes you want, i 
normally make 3 connected nodes and use the last one as a modulator. Also its 
easier if you zoom in to select the node you want (the + button beneath the box)

Try setting one of those (moving) nodes to /reverb

and there you go, some kind of unholy electronic noise controlled by flash :)

Then you can just add boxes, create nodes and set them to send the various 
messages, /delay, /filter, /vol, /g1 & /g2 etc..

what can be interesting is once you have a load of stuff running is to pause all 
the boxes so you get an idea of what happens when flash isnt sending any data.

thats about it.

I realise its pretty complicated, especially because i havent got any way of 
saving / loading setups in the flash app yet. So if you dont want to stand there 
fiddling around while doing the presentation I totally understand.

Of course all the stuff is free for anyone to download and all the source code 
is available so what i'll do later tonight is to write a wiki page with 
instructions and post the link here when im done.

A lot of the code also lives here (as3 OSC library, java HTTP OSC server, 
Max/MSP java objects etc)

http://www.assembla.com/wiki/show/osclib

this is because i've tried to keep just the core 'go related' code in the 
playground, but i'll write all this up later :)

anyway, good luck, hope it goes well for all of you who are involved.

and anyone who tries it out let me know if you have any problems and i'll see 
what i can do, i've not built standalone Max/MSP apps before so I wouldnt be 
suprised if something goes wrong.

thanks,

Martin.