Guinea Pigs
Posted: October 14, 2015 Filed under: Anna Brown Massey, Pressure Project 2 Leave a comment »Building an Isadora patch for this past project expanded my understanding of methods of enlisting CV (computer vision) to sense a light source (object) and create a projection responsive to the coordinates of that light source.
We (our sextet) selected the top down camera in the Motion Lab as the visual data our “Video In Watcher” would accept. As I considered the our light source, a robotic ball called the Sphero, manipulateable in movement via a phone application, I was struck by our shift from enlisting a dancer to move through our designed grid to employing an object. This illuminated white ball was served us not only because we were no longer dependent on a colleague to be present just to walk around for us, but also because its projected light and discreet size rendered our intake of data an easier project. We enlisted the “Difference” actor as a method of discerning light differences in space, which is a nifty way of distinguishing between “blobs.” Through this means, we could tell Isadora to recognize changes in light aka changes in the location of the Sphero, which gave us data about where the Sphero was so that our patches could respond to it.
My colleague Alexandra Stillianos wrote a succinct explanation for this method, explaining “Only when both the X and Y positions of the Sphero light source were toggled (switched) on, would the scene trigger, and my video would play. In other words, if you were in my row OR column, my video would NOT play. Only in my box (both row AND column) would the camera sense the light source and turn on, and when leaving the box and abandoning that criteria it would turn off. Each person in the class was responsible for a design/scene to activate in their respective space.”
The goal was to use CV (computer vision) to sense a light source (used by identifying the Sphero’s X/Y position in the space) to trigger different interactive scenes in the performance space.
Considering this newly inanimate object as a source, I discovered the “Text Draw” actor, and chose “You are alive” as the text to appear projected when the object moved into the x-y grid space indicated through our initial measurements. (Yes, I found this funny.) My “Listener” actor intercepted the channels “1” and “2” which we had our set-up in our CV frame to “Broadcast” the incoming light data, to which I applied the “Inside range” actor as a way of beginning to inform Isadora which data would trigger my words to appear. I did a quick youtube search of “slow motion,” and found a creepy guinea pig video that because of its single shot and stationary subjects, appeared to be possibly smooth fodder for looping. I layered two of these videos on a slight delay to give them a ghostly appearance, then added an overlay of red via the shapes actor.
As we imported our video/sound/image files to accompany our Isadora patches into the main frame, we discovered that our patches were being triggered, but were failing to end once the object had departed our specific x-y coordinates as demarcated for ourselves on the floor, but more importantly as indicated by our “Inside Range” actors. We realized that our initial measurements needed to be refined more precisely, and with that shift, my own actor was working successfully, but we were still faced with difficulty in changing the coordinates on my colleague’s actor as he had multiple user actors embedded in user actors that continued to run parts of his patch independently. The possibility of enlisting a “Shapes” actor measured to create a projection of all black was considered, but the all-consuming limitation on time kept us from proceeding further. My own patch was limited by the absence of a “Comparator” as a means of refining the coordinates so that they might toggle on and off.
Lexi PP3 Summary/reflection
Posted: October 12, 2015 Filed under: Alexandra Stilianos, Pressure Project 3 Leave a comment »I chose to write a blog post on this project for my main wordpress page for another dance related class –> https://astilianos.wordpress.com/2015/10/13/isadora-patches-computer-vision-oh-my/
Follow the link in wordpress to a different wordpress post for WP inception.
Myo to OSC
Posted: October 12, 2015 Filed under: Uncategorized Leave a comment »Hey there everyone.
Here is a video those missing steps of getting the Myo up and working:
And here are the links that you would need:
https://github.com/samyk/myo-osc for the Xcode project
https://www.myo.com/start/ for the Myo software
Remember, that this is a very similar process to getting the Kinect, or any number of other devices connected to your computer and Isadora.
Please let me know if you have any questions, or if you would like to borrow the Myo and try to do this yourself.
Best!
-Alex
Jonathan PP3 Patch and Video
Posted: October 12, 2015 Filed under: Pressure Project 3, Uncategorized | Tags: j, Jonathan Welch Leave a comment »
https://youtu.be/HjSSyEbz68Y
CLASS_PP3 CV Patch_151007_1.izz
PP3 Isadora Patch
Posted: October 7, 2015 Filed under: Isadora, Pressure Project 3, Sarah Lawler 1 Comment »Hi Guys!
Here’s our class patch so far for PP3!
CLASS_PP3 CV Patch_151007_1.izz
-Sarah
Coherence???
Posted: October 6, 2015 Filed under: Uncategorized Leave a comment »I was thinking we might want our scenes to be connected… I have a patch that turns on an outside night scene with crickets chirping and animal moving around in the woods… There is also a little parallax as the “performer” moves around in the space (the 33% X 50% piece of the stage before the performer triggers another patch/scene/whatever), but I could adapt it if we have a common vision…
The performer’s position is represented by the moving H (Vorizontal) and V (Vertical) readout. The numbers would not be visible in the projection.
The trigger position is in the lower left corner.
The “Sextant” and a patch that I was using to activate my Scene/Actor when the performer was in area 1
Posted: October 6, 2015 Filed under: Uncategorized 4 Comments »I am guessing the area’s range is 100 X 100 in both directions, so I divided it into 33/33/34 W and 50/50 H, and wrote a user actor to define area 1. This could be used to activate a scene or turn on/off projectors.
The red quantifies the H axis, blue the V, purple is the combined, and green is the output with a value.
Computer Vision Patch Post
Posted: October 5, 2015 Filed under: Alex Oliszewski, Connor Wescoat, Isadora, Josh Poston, Sarah Lawler 2 Comments »
Screen Shots included within zip!!!!
Selecting Scenes
Posted: October 4, 2015 Filed under: Jonathan Welch Leave a comment »https://vimeo.com/141210159
I put together an animatic for my first idea for the scene selection.
The icons are purely arbitrary; we would probably want something more representational of the concept behind the individual scenes.
I am totally flexible on the idea, and it is dependent on being able to get reliable X Y positional data on the performer from the overhead camera…
Class notes on 9/30 regarding PP3
Posted: September 30, 2015 Filed under: Alexandra Stilianos, Uncategorized Leave a comment »PP3 GOAL: Create an interactive ‘dance’ piece (as a group), each should create a moment of reaction from the ‘dancer’
Group goals/questions:
- Focus on art!
- What will we do?
- How will we do it?
- What is my job?
- Establish perimeters and workflow?
- Understand the big picture?
- How is the sensing being done?
- What is the system design?
Resources:
- 4 projectors
- 3 projectors on floor
- 2 HDMI Cameras
- Top down camera with infra red
- Kinect
- Light/sound system
- Isadora
- Max/MSP
- Myo (bracelets)
- MoLa
- Various sensors (?)
Group 1: Sarah, Josh, Connor, “Computer Vision Patch”
- Turn on MoLa, video input, write simple computer vision (CV) patch that gives XY coordinates
- Program lighting system, provide outputs and know what channels they’re on
Channels (1- 10)
- x
- y
- Velocity
- Height
- Width
All x2 for the 2 cameras (top down and front), 2nd camera would be same identifiers but on channels 6-10.
Group 2: John, Lexi, Anna, “Projector System”
- Listen to channels 1-10 of 2 cameras, take data, create patch and a place for them (6 quadrants were discussed, each in charge of one)
Options:
- Create scenes and implement triggers
- Each create our own user actor in the same scene
(This is by no means an exhaustive or exclusive list, just my general notes from today!)


