A little experiment over the weekend.
“My screen is a scrapbook: every time my mouse moves, i tear away part of the screen and save it. over time a big bundle like this builds up”
Via: Kyle McDonald
Beautiful glitch when switching Rhino CAD to a new monitor.
Using facial-recognition algorithms (Processing’s OpenCV library) while slowly degrading an image until the algorithm no longer sees a face.
At Steve’s request, a program that will play the word “parklife” from Blur’s song of the same name whenever the return/enter key is hit. Works while running in the background, receiving return/enters from any program. Unnecessarily keeps track of parklife-count.
After an afternoon of working on a Processing project with Alex Myers, I created a Processing sketch that pixelates and posterizes an image. Next step (and definitely the hardest) will be to find the weighted center of the pixel areas (not each pixel block but areas of the same color). The above image is Van Gogh’s “Starry Night”.
Max/MSP users: look familiar?
For the past week I have been wrangling with getting ffmpeg (the open-source, command line video utility) to run in a Processing sketch and preserve the hard edges of graphical and/or intentionally pixelly video. It now works!
Details are listed in the code itself, but it is most important to note that the codec is likely the most important factor in getting good quality. The “png” codec is great, but will create rather large files; mjpeg (MotionJPEG) also works well for graphics and hard edges (pixellated images, etc); H.264 is all-around good for photgraphic images.
The sketch below runs ffmpeg’s commands within Processing (as covered before) and exports a video from a series of still files. Processing’s built-in video library seems ok, but offers little in the way of control as compared to ffmpeg. Questions or suggestions are welcomed – feel free to use but please give credit!
While I really don’t know why, the previous sketch seems to break with a Java IOException error. It appears that ffmpeg can’t be found, but the solution is simple: specify the path to your ffmpeg install. For example:
/usr/local/bin/ffmpeg filename.mov etc...
The “-c:v” option to specify the codec is also updated to “-vcodec” and “-acodec”