Archive
jason

so this week I mocked up a working prototype of my final and put it up for the class to try during class time.

the concept gets a little lost in the game-like interactivity of the project so maybe for the final i will just go all out and make it a game…..but then again i dont want to lose the concept too much….anyway, we’ll see what lauren, alex and the class have to say about it…

here is my project diagram:

Read More

So thinking more about my project….i’m not sure I know how to measure an amount of movement using kinect and use it to soften or amplify sound so I have changed the interaction a little…

 

– the user still begins the experience by calibrating (assuming the submissive pose).

– a loud, high-pitched noise is played.

– two random points are picked on the screen and the user has to find them with his hands.

– as the user gets close to the points the sounds volume and pitch decrease

– when the user gets close enough to the random points the loud, pitched sound plays again and new random points are picked.

 

For next week:

– have a working prototype of this project for review.

Read More

So here is some more clarification on the actual physical form that the piece will take:

It’s going to be kind of a game but infact the software will be playing the user as opposed to the other way round.

 

– The user will begin his experience by assuming the submissive pose.

– Their will then be a loud, high pitched sound created by the program and the user will need to move rapidly to keep it under control.

– Once the user has figured out that his movement is controlling the sound (and the sound reaches a reasonable volume and pitch) then the program will switch and his movement will make the sound louder.

– The program will switch between randomly between these two modes without prompting the user.

– If the user moves away from the scene the high pitched sound will continue.

Read More

Project Proposal

NEW and IMPROVED!!

 

So, conceptually, the most interesting thing that came out of my midterm (I think) was not actually the sound that my users created but the lengths people will go to in order to interact with the piece. What I found really interesting was the pose that the user has to adopt in order to get recognized by the software is called the “submissive” pose. This got me thinking about the processes we go through as users in order to allow software to essentially “take our skeletons” (I’m thinking this will be the name of the piece) and use them for their own ends.

 

The idea is that my project will highlight and amplify that exchange of ownership of our own essential parts (in this case our skeleton). In some way the user will be asked to act submissively toward the software and the software will abuse this exchange and use it’s ownership of the users skeleton to manipulate the user into acting under the software’s demands.

 

 

 

TimeLine

 

 

Nov 12th

 

– Consider the actual physical form that this piece will take. Do experiments with motors tugging on the body against natural movement, on text-based scenario’s where the software will tell you to take submissive poses in order to get to the next stage of the project and then scold you for being so submissive.

– Have a working (un-interactive) form of the project which documents how a user travels through the project. (a system/project diagram).

 

Nov 19th

 

– First Prototype

– Even if the two do not interact have both the skeletal recognition software working (basically almost done) and a sketch which takes the user through the narrative of the project asking for keystrokes or mouse movement instead of  submissive poses.

– Consider where the project is going to be presented. Are there any specific spatial requirements?

 

Nov 26th

 

– Technical development of the two sketches (hopefully not much is needed at this point).

– Connect the two sketches (probably using OSC which I have already used before) and allow time for minor tweaks to the code for an optimal interactive environment.

– Allow time for small design and aesthetic changes.

 

 

Dec 3rd

 

– Final Presentation

– Allow for setup and documentation time.

 

Jason Rabie

 

Read More