As we discussed tody in lecture, the OSC protocol allows for complex communication to and from any device on the network and, by it address (/1-a/3, etc) and to any object within the device or application receiving it. The complete specification can be found here:

OpenSoundControl Spec 1.0

The most important section on the page tells us about address wild cards and groupings. Today we did things like:

/*/3 55

...which would send the message "55" to every "3" within every object. I mentioned that I was unclear about other methods of specifying the address so here are the answers.

* means all members

[1234] or [abc], "brackets" mean a match on each character

{23,45,56,456,1,2} comma separated groups are in curly brackets

Other methods are listed on the above-linked Spec page.

Also, I wanted to link you to some potential uses, others who are already using OSC to organize themselves and their material plus several technologies that have sprung up around it.

Some areas of use: http://opensoundcontrol.org/osc-application-areas

Hard/Soft implementations: http://opensoundcontrol.org/implementations

FLOSC: http://www.benchun.net/flosc (Flash to OSC for web interactive pieces)

Occam: http://www.mat.ucsb.edu/%7Ec.ramakr/illposed/occam.html (OSC to MIDI app)

There are hundreds of other tools floating around on the web and many implementations for commercial applications such as Live!, Max/MSP, Reaktor, and others.

Of course don't miss the monome.

See the attachment. This is stage1 of a larger project to build a Pd-extended master patch. I'm hoping to just build a script that would automatically generate a master patch from libraries loaded at start up...that's the end goal, anyway.

Following up on the "expr" expression object, you can find documentation here.

General docs for PD are here and there are several other resources here.

I am sorry to say that my friend who is lending me his drum set does not feel comfortable with everyone using his set for the show.

-Avi

Hey everyone,

I found these video tutorials for the subtractor and thought it may be useful to some.

The first three links are the tutorial series on the subtractor.

http://www.mutantaudio.net/forum/ezlinks.php

-Avi

Hey there,

I was just wondering if there was any further information about the video that was taken for Music220's final performance.  I'm sure I'm not the only one that would like to see it.

Thanks,
John

To follow up on a non answer from lecture, here is a straight-forward introduction to TCP and UDP.

http://www.devmaster.net/wiki/UDP_vs_TCP

One of you recently pointed out that arrays have a size limitation (necessary for memory saving), so for large soundfiles, it is recommended that you read them directly from disk.  The object we looked at for this is [readsf~].  Note that you must specify the number of channels within the object, such as [readsf~ 2] for a stereo file.  Also, unlike [tabplay~] or other array/table readers, the filename must be reset before each play.  In the attached patch I am playing 2 soundfiles simultaneously, also reloading the same file automatically once it is done playing. 

Enjoy!

Following up on this afternoon, I ended up creating two patches to help Matt Rung with his loop idea.  I thought they might be useful generally, so they are attached here.  This is still using the "openpanel" method of loading opening for convenience, but there are many other ways.  I have the gamelan sample patch I mentioned today around here somewhere (my home machine).  If I can find it, I'll post it for your perusal.

UPDATE: You will find the gamelan patch attached below as well (it is a zip archive since I included the soundfiles, all from sflib).  Unpack the folder, and open "auto_trigger.pd".  Hit GO and listen to my pattern!  I think this turned out pretty well given how trivial is it.  The coolest part happens right when you open the patch, auto-loading all of the files into the arrays with a line (could also have been a counter)!!

BONUS: I included a second subfolder of samples within the gamelan folder, african percussion samples to try in place of the gamelan sounds.  Just place them in the main directory (overwriting the gamelan samples) and listen again, whah-la, new samples, new riff.