Andrew's ITP blog

For my Nature of Code Final, I continued some of the elements for my thesis.

1.   Mapping the major factors of Craig Reynold’s steering behaviors to theater terminology, using the 8 Laban efforts (LabanEfforts)

This was done by using Dan Shiffman’s flowfield and flocking examples as a reference tool.  And then building controls into ControlP5.

In the code attached here, it draws the results directly into the sketch. In the version for my thesis, it sends the drawing through Syphon.  Also included is my openNI tracking code, which you can work with.  It is built to track up to four users at a time, and color code them for recognition.  It is also built to calibrate quickly with any projector.

I should note that the tracking code also sends a calibrated image of any users infront of the Kinect over Syphon.  When interfaced with software like Isadora this can be used to provide an alpha mask, and project black over the users’ bodies to avoid spill and protect their eyes.

2. I continued my work with the textured cloth.  I made it so that the images could be changed out while the code is running.  I also made it easier to restart the animation to allow for a more iterative rehearsal process with less setup time.

Again, In the code attached here, it draws the results directly into the sketch. In the version for my thesis, it sends the drawing through Syphon.  This code is greatly indepbted to the toxiclibs library for Processing, and the 3d cloth example.

Most of my work is in the area of live performance.  So I wanted to play with how feedback could be used simply but effectively to enhance the performance, rather than distract.

These two screenshots are from  a patch I worked on, using video from an excerpt of a piece with an aerialist I am working with.  This would actually be used with a live input, but for classroom reasons I went with a recording.

The primary goal of my final is to explore two main questions:

1. How do qualities of movement help define characters’ personalities, and internal states in a given moment?
2. What are the benefits (for live performance) of exploring movement through code rather than rendered assets?

Drawing from the world of performance theory/training, I want to explore Rudolf Laban’s “8 efforts” of movement through code.  You can find my breakdown of Laban’s efforts in the attached PDF here:  Laban Movement Notes

The simple version of my final would be to:

• Create a class of moving objects
• Have system of the class relate to a specific person/character on stage
• Be able to change the Laban Effort of each system while the program is running.

The more complex version is to build it into different methods of interacting with the characters onstage.  These include:

• Having the objects respond to multiple performers’ bodies as attractors.
• Placing moving elements onto the bodies of the performer
• Having the physics of the external world respond to a given characters internal state.

I would also like to build in ways of changing the images of these objects via key commands, or gui buttons.  Lastly I would like to explore using Syphon to “export” tge visuals from my Processing code into Isadora to allow for scalability/combining sketches.

You can view a video of my initial experiments here:

Below you’ll be able to see my first Jitter Patch.  My goal this week was to familiarize myself with some of the basics, as I’ve never used this method of programming before.

Mainly I explored variations in speed and volume.  I also wanted to play around with using the spectrum to change the RGB valuse via the char map.  And maybe it’s just my affinity for object oriented programming – but I wanted to  explore the “cordless” method of sending and receiving signals.

Click here to download my patch

 Week1Pt2.maxpat

Jitter Patch Week One