The Pace, Phase 2Once I had the prototype working, it was time to get serious. I secured an installation space at Squeaky Wheel (712 Main Street, Buffalo). The room that I would be using measured almost 10' 10.5" x 18' 6", which was fine in terms of width, but perhaps a little long, considering the width of the projections. The door to the room was centered in the wall, so I decided that I would build a temporary wall in the space, placing the entry to the installation to the side. This wall would limit the length of the installation to 12'. The size of the room allowed me to determine the maximum number of buttons in the room, which would have been 120 (based on 1' squares placed side by side). Eventually, this number was reduced to 22 buttons; aside from 120 buttons seeming like overkill in such a small space, I also didn't have easy access to 120 ASCII characters via my hacked keyboard. As I started to construct the floor, another issue arose that also lead to reducing the number of buttons: if the panels were placed side by side, there would be no negative "safe" space in the room where people could stand without interrupting the flow of the video (standing on a panel effectively paused the video, constantly returning the movie clip to the second frame). For aluminum panels, I used recycled plates from a printing press, cutting them into 14" squares to minimize waste. I drilled a small hole in the corner of each square, where I attached the wire that ran to the breadboard. I laid them out in five rows, alternating the number of panels (4,5,4,5,4). This seemed to be the optimum layout, assuring that panels would be pressed as people walked through the room while still allowing for negative/safe space (columns were separated by 12", rows by 9"). After laying out and wiring the bottom matrix, I covered it with carpet padding. I cut a holes in the padding centered over each panel so the the top and bottom pieces would connect when stepped on. Since aluminum is a soft metal and will hold a shape once bent, I also placed a small piece of padding in the center of each hole, aiding the prevention of creating permanent concave bends in the top panel. The photo below is a shot of the padding with five small holes cut for each panel (this didn't work so well). With the padding in place, I laid out the top panel matrix and wired it. Finally, I covered it all with a piece of carpet, creating a smooth walking surface. Considering several restraints (time, projector availability, finances, and Flash movie width), I temporarily discarded the fourth wall (though it will return in the final installation). With the physical interface constructed, it was time to return to the Flash file. I created additional movieclips to total 22 and wrote 18 new lines of poetry that would (hopefully) make sense in any configuration. I increased the stage size, mentally dividing it into thirds: video grid wall, text wall, and fullscreen video wall. I expanded the original video grid to echo the new floor, laid out the new text movieclips (now limited to 10 seconds), and placed full-sized instances of the video clips. In the actionScript, I added lines in the keyListener to include the new symbols available on the floor, modified it to activate both video and text instances, and built an array using the keypresses that activated the video and text on the other two walls.
I added an enterframe function to call instances of the movieclips on the third wall to play, then discard the first member of the array (the clip that was just played). This effectively built an automated editing system in which the user's path through the room created a new movie pieced together from the activated clips. The sound in the space will respond to light levels in the room, from both the video and the shadows that people throw on the wall as they interrupt the projections. To measure the light, I used a photocell resistor wired into an Arduino board. I found several helpful resources on the Arduino website, including the following code that will send pin information from the board to Max/MSP:
In order for the above code to work, I had to download the SimpleMessageSystem library and install it. (I just followed the instructions for Arduino to Max communication found in the Arduino Playground.) Also available from Arduino was a nicely constructed Max patch that reads input from the pins. I modified their patch to take pin data, multiply it by a certain amount, then use that result as a frequency output by the DAC in MSP. I also shot some video of my tests of the photocell, which I've posted on my own site here. Finally I had both the physical and virtual built and was time to put them together. I added a second graphics card to my Mac Pro tower, allowing up to four displays. Since I was using the walls of the room as screens, I couldn't use rear projection (as indicated in the original concept sketch). I built shelves on the side walls to hold projectors pointed at the opposite wall, and Squeaky already had a hanging shelf that was suitable for the wall across from the door. I plugged the projectors into my computer and discovered an unexpected problem: when I display the Flash file in full screen mode, it will not expand to cover all three displays; instead it compresses it to be the width of the main display. So, with all projectors set at 1024 x 768 resolution, I centered the swf(limited to 2880 pixels wide) as best as possible, which left some blank space on both side walls as well as the title bar at the top of the window. This is an issue I will need to overcome in the final four-wall installation. In showing people the prototype and the space, a few other interesting topics came up in discussions. I've already mentioned my efforts in creating "negative" space where a person standing still would not interfere in the playing of a video or text movie. After seeing this put into effect with several people in the space, I'm feeling slightly conflicted about this decision. On the one hand, the original concept of the piece was to create a space "that resists rest," one in which the user/viewer must be moving in order to keep the walls playing. I really enjoy that idea and it's hard for me to give it up, though I think, in this space especially, this may not be the right piece in which to force motion. If the space had entries/exits on opposing walls, or if it were installed in a hallway, walking through the piece would be more natural. It seems like the confined space at Squeaky invites people to stand and watch, or at best mill around with your eyes trained on the walls. I've noticed that when several people are in the room, individuals are more likely to stop and chat, paying no attention to whether they have paused a video. In fact, I'm not even sure that it is obvious to the uninformed user that it is a lack of motion that has paused a video. Something many people did notice, however, was when another's body interrupted the text wall and the lines of poetry were projected onto a body instead of a flat inanimate surface. Of course, this also occured with the video walls, but seeing video on the body is apparently less exciting. In any case, what I like most about this development is that it causes people to become more aware of their body in the space, moving intentionally to either escape or interrupt the projections. I also noticed this behavior as people encounterd the photocell and realized that if their shadow fell over the sensor, the music tones got lower while bright light made the tone get higher. I see anything that gets the user moving through the space as a positive aspect. Seeing the installation up and working, with people in the space was very exciting, as well as useful. Even though I have plans to expand from where I'm at right now (building the fourth wall, adding more photocells and different types of sounds), I feel that the project is fairly complete and the experience of the users was a very close approximation of what it will be with the fourth wall up. Mostly I'm glad I had the chance to do a preview and get some feedback before the opening. |