Preparing my thoughts for crit tomorrow:
- The project is interactive (dynamic)
- Audience will interact with it over time
- Preferred audience is a crowd because it will enhance movement
- Audience should understand they are effecting the system indirectly, but it should not be able to understand the underlying process directly (to keep things feeling random. They should feel like more of a trigger than an influence (even though they actually are)
- Final images should be projected (and printed if static images are interesting, we'll see...)
idea
Using an implementation of blob detection, randomly select some blobs with movement above a threshold (crowd or individual movement, not noise). Draw selected blobs to screen with varying color based on any data available from blobs library (depends on blob implementation). Auxiliary shapes can be generated as necessary, will test.
edit
The flob package was on of the ones Thomas mentioned awhile back. It has trackable blobs that give both lifetime and velocity of a blob, which were two important variables I was hoping for to map to size/color/opacity of my blocks. It also works in both oF and processing2+Thomas also had a single image of the reference art from our trip to the post tower
Fortunately, that's one of the more representative images, and I can just make out the letters "ARITHM" which of course (as Laura was trying to remind me) means these images are from an exhibition in the Bonn Arithmeum. Searching there site was almost futile, but I found a few helpful things:
http://en.wikipedia.org/wiki/Very-large-scale_integration
Hopefully that will give a bit more direct insight into how to draw these objects effectively.
Also, flickr is helpful
http://www.flickr.com/photos/bibi/5939565186/sizes/z/in/photostream/
http://www.flickr.com/photos/bibi/5939007795/sizes/z/in/photostream/
http://www.flickr.com/photos/mitko/2210284854/sizes/z/in/photostream/
No comments:
Post a Comment