Taking a break writing here in favor of a short adventure in apartment hunting.
In an homage to the Television Apocalypse, Youtube is showing classic television shows like The Outer Limits. It's excellent psychodrama. Here's a transcript from episode 1008 titled The Human Factor.
Man: if this machine works it will be possible for two minds to communicate directly. To share the same thoughts and emotions simultaneously. Woman: emotions? Man: psychiatrists think the intellect is a useful but devious trait. this machine will let me know what the subject is really feeling, way down underneath the intellect. Woman: I'm not sure I want to go through with it. Man: be a good girl. (pats her on the shoulder patronizingly) Man: take a look at the oscilliscope. Woman: Huh. Well you can't tell too much from that, can you? Man: Not too much. But in a moment I may know what you really think. because I intend to amplify those waves and feed them back to a machine into a terminal instrument which is capable of translating them back into the thoughts and emotions that produced them. and that terminal instrument is my own brain. Now relax, I'm bringing up the power.
It's 2009. The Bandwidth of a consumer Internet connection is going up. Laptop computers are ubiquitous, small storage devices are everywhere and can meet or exceed internal storage, everyone's making movies, sounds, pictures on their computers. I'm doing this. But where the fuck am I going to put this stuff when I don't want it available on the laptop but I don't want to delete it? There are a lot of solutions to this problem. Most notable is Apple's TimeMachine product, which makes the decision for you by dedicating an entire external USB disk to the role of incremental backup. But what if I want to control what gets backed up and what doesn't? Some things should not be backed up. Cache files, auto generated image thumbnails, temporary files, garbage directories generated by OS X, private documents with very particular accounting of where each copy resides. Apple has taken the road of abundance and thrown assumptions of privacy and efficiency out with the bathwater. Fortunately, OS X and GNU/Linux have neato user obsequious tools like rsync and rdiff-backup. For my Mac, I wrote a simple script that backs up my entire home directory in one command with an optional file to exclude directories to backup.
#!/bin/sh
EXCLUDE_FILE="$HOME/bin/full_backup.exclude"
rsync -rv --progress --stats --exclude-from=$EXCLUDE_FILE $HOME/ $1
Search for EXCLUDE PATTERNS in the rsync manpage for the exclude patterns file format. Basically, one on each line with shell wildcards accepted.
This will copy everything in my home directory except for the files (or patterns) in the .exclude file to a directory
passed in as an argument at runtime. It will also give you an realtime progress meter for each file! Neato.
Kevin Farrell and Devin Maxwell are
Four Trio This recording is produced with love by arsenic-free music: "we have arsenic-free music, they don't"Doom Metal. An excellently named genre. I can't stop listening to Nadja's cover of Needle In The Hay, my favorite Elliot Smith song of all time. Oh yeah, and Lala is my new favorite music site.
I learned how to make materials, atmosphere and a sun! Here's my first test render with the finalized model.
I have decided to give the movie a working title of "radio astronomy". Not too catchy but it makes me feel funny when I say it.
Also, the Wacom tablet is not worth it. While the x.org drivers and the kernel drivers in CentOS 5.3 work well, somehow the application specific configuration is different and crashes, making the pressure and tilt useless. Would be nice to debug sometime but right now I'm not doing much painting or drawing.
A picture tells a thousand words. Here's my story from this weekend
On deck: Wacom tablet installation and configuration for the OS, Blender, Gimp and Inkscape. Oh my!
Dove in head on. Here's my list:
The Good:/lib/modules/fglrx/. Also requires crucial settings for 3D
acceleration to perform in a visually acceptable way (read: 3D objects do not
get clipped by a noisy black plane). These settings are also
not documented and probably manifested from my particular hardware
configuration.Got a nice 2 way AMD64 workstation with an ATI R350 video card. Old hardware but better than anything else I have for the previs work. CentOS is...well it's interesting. The video card worked by default for GLX mode and the monitor resolution was auto detected to 1280x1024.
There are a lot of missing pieces, most of which are related to software. CentOS has a much more conservative selection of packages then I'm used to. Notable differences from Debian:About 11 days ago I set out on a journey to create a custom Debian package repository to serve my own custom built packages based on very specific versions of source code. Through the oral history of my predecessors and some experimentation, I have accomplished my goals. It was not easy. I'll outline my process step by step here, so other can continue the tradition. Yea knowledge!
Before you start out with any labor, you must first answer some preliminary questions and sketch out your architecture. The first question you have to answer is "who else will be using these packages". If the answer is "no one" this article is not for you.apt-get install checkinstall for that. If the
answer is "many other servers and workstations controlled by others aside from
myself all running various versions of Debian or Ubuntu", then read on.
My needs
aptitude install pbuilder reprepro nginx dpkg-dev debhelper devscripts fakeroot dh-make autotools-dev cdbs dpatch
Next open the control file. Verify all dependencies for the versions on your
build system. All we need to do here is make sure the package knows about it's
supporting libraries. Adjust the version numbers as needed. Now you have to open
the rules file. If you added any custom
configuration options when you first compiled the code, you need to find the
section that calls ./configure and add those options. You also need to read
through the build target and see if the original author of it is doing some
weird things with the build process. If it matches up pretty well with your own
successful compiliation then you can move on.
In some cases you might need to patch the source code or perhaps the original
author's patches won't apply cleanly to your new source code. This is what
dpatch is for. Compare the old patches with an interactive dpatch shell by
entering dpatch-edit-patch [patchname] where patchname is what you
want to call the patch. Tuxmaniac has a Short
tutorial.
Run a test build/clean directly with fakeroot debian/rules
[build|clean] Where build or clean is the target you wish to test. If the
build process is functional, it's time to build the source and binary packages!
Yea! But not yet...Aw :c
Build dependencies. During your testing you might have noticed that the test
build fails due to missing build deps. You can install these deps by hand each
time but that's a pain. Fortunately pbuilder provides a nice shell script that
will figure these out and install them. Just run this in your debianized source
directory:
/usr/lib/pbuilder/pbuilder-satisfydepends
Magical! You have all build dependencies installed. Now you can try and build
the package. I'm using debuild like so:
debuild -us -uc
If debuild succeeds, you should have a bunch of files one directory up. An
explaination of their roles:
dpkg-source -x
*.dsc
Next up, serving them from a repository!
Found this poster in the hallway of my office this morning. It is advertising the Wall About film festival. Sounds cool: I haven't heard of it, the poster is designed well and it has the word "film" in it. Relevant to my interests. Then I had the misfortune of reading the text on their web page. I'll copy verbatim to save the agony of looking at the whole thing.
Wallabout is: a collaborative project putting cultural assembly into explicit practice; a collective celebrating artists’ efforts and the co-production of art; a festival promoting the continuous flow of creative episteme and the techne. It is a question leading to a question leading to a question. Wallabout is committed to challenging our minds while exulting the works of to-day. Wallabout is about it all.Sad thing is I'm still interested. Can't judge poorly the whole event for one bad writer. Fucking art.
I rented this DVD as a reference for my film not knowing what to expect. Well, here's the 8 minutes of chapter 2, see for yourself:
"Workflow" is a word I hear a lot but no one has a definition for it aside for what "works for them". So perhaps a good workflow is what works for me? Let's see. Since I'm a real software developer and a fake filmmaker, I will take my software workflow, which is quite productive and adapt it to directing/producing a film. Here's my software toolset as it stands:
I'm working on a short film. It is currently untitled. Here are my production notes up until now.
Doing previsualization from nothing to something. Can't get a permit more than once so that rules out coverage on location. Started with a top down photograph of the architectural footprint from Google Earth, used the software measuring tools to determine some rough distances between points. Took the photo and brought it into Inkscape. Began tracing paths and curves around significants parts of the landscape. Got the proportions right. Imported curves into Blender, two week crash course in 3D modeling. Got the right paths converted into polygons and through a lot of guess work, some arithmetic and a lot of measuring defined one unit in a realistic scale. Read online that the building is 6 stories, guessed that one story will equal 10 feet and fudged the height of the building to 60 feet. Couldn't find any specs on the water tower so calculating height is impossible. But lo and behold, there is a treasure trove of photographic coverage on Flickr, and thanks to Flickr's camera metadata reader, I got lucky and found a dude who did helicopter shots with a Nikon D50. Both building and water tower in frame. Got the lens mesaurement and the aspect ratio of the shot. Exported data from Blender to Autodesk FBX format, solicited T for some help with that precious software. Imported FBX and T did her magic by creating the same camera and locking it to the photograph. The original geometry was composited with the photograph and the camera was moved and scaled to make the 3D building fit with the size and angle of the photograph. That gave us the water tower height reference in a perspecitive view. She created a cylinder of the proper height and exported both building and water tower as a Wavefront OBJ format file. I imported that file back into Blender and now I must match it up to the scene I have. This process was facinating. The photographic reference was what I was missing all along. It's amazing that I can use the Internet as a reference for not only visual information but also camera and lens details which can apply to a 3D world. It made me think of my first calculus class, since the number of known values was so little but it wasn't merely a 2D plane so things like angles, tangents and lens curvature influenced the results. We have come so far from those days of proving our physical world on paper to taking what was written on that paper and transforming it into a computer program so we are no longer required to do the math necessary to make the simulation correct.Two small notes about chef conventions (assumptions), after I got my test installation running.
I'm experimenting with Chef after attending Ezra Zygmuntowicz's talk about it at Philly E-Tech conference last week. The back story is that I began writing my own framework in Perl two weeks ago to automate building up EC2 instances. I made some progress but it was far from extensible. So I'm trying chef. If all goes well I'll have a framework in place to create new nodes so I'll never have to log into them, they will "just work". The goal being a base Debian EC2 image creation and a tiny bootstrap script passed as per-instance metadata to get chef installed.
First Impressions? Not too good. Here's my test, ported from a subroutine I wrote in perl with some file I/O and a big ol' system() call.Three days of rest for the vacation and I'm ready to go back. The way back was not as eventful as the way out. I woke up late. Real late. Didn't leave Philly until 1PM and I had to catch the ferry at 7PM. That's 6 hours to cycle 85 miles. And the weather forecast was for rain at 5PM. Sounds AWESOME. I also had a 10 pound load (including laptop computer) and no matter which way I turned there was a headwind from the north.
It was everything I expected. Not since PBP 2007 did I suffer so much on a bike ride. Fuck that. With more time and better weather the route is very pleasant. Few turns, good roads and a nice pace between towns. Here's my map and near finalized cue sheet. WARNING! Page 3 is the route back. Page 1 and 2 is the route out.

Larkspur Bowl Downhill from Lee Azzarello on Vimeo.
I made a program! It records the radio. It's your last chance to participate in this crucial part of the modern world. Download, install, be confused!
Inspiration. It's like opera.
Three great links to two artists (Aaron Koblin and Daniel Alfonso Massey) and one project of thousands.
I Hardly Know Her (witty!) is a Flickr viewer. It approaches the problem I'm asked about often: How do I make a photography album online if I'm a professional photographer? Well, I got mines, now it's time to make yours. I'm working on the details.
Interesting. Yahoo's page on API clients results in a set of three that are written in the Ruby language. Like most web "API" libraries, I click on all of them and figure out the pieces later.
Sounds and Emotions is a pretty good radio show put on weekly by Nico Bogaerts in Brussels. Their tag line is "Experimental music for experimental people". Unfortunately, their distribution format is 180 degrees from "experimental". It's quite conservative and restrictive, limiting their distribution using format obsfucation. Since I like their show so much, I have composed a script to use mplayer to save a copy of the streaming mp3 to disk. I'll be uploading them weekly to a drop, as I listen to them. The script is also present in the drop, if you are so inclined to rock the steez yourself.

Misspelling Generator is amazing...in concept. In the long line of cool conceptual concepts that have unintended consequences, Erik Borra and Linda Hilflings's Firefox plugin claims to intercept searches to Google and generate a set of misspelled terms based on your proper terms. Cool concept, but a bit of an implementation fail from all ends. In the 10 times I used it, every time I used more than one term it would crash firefox because the script took too long. After these 10 uses, the public wifi network I was on mysteriously began reporting that all my search terms were blocked because it was suspected that I was a robot trying to abuse Google.
In summary, this software is a failure because it literally fails to evaluate (or halt, I'm not sure which), then it submits a false positive to it's far-end. Like ABSML, its a good idea with a bad execution.Miss Heather has been very nice with our little dialog. But wait! There's more shitfones being documented. This one is pretty amazing, though the Queens shitfone wins, literally.
I have an honorary degree in software engineering from the university of the Internet. I propose to a different friend on facebook every monday. I'm single on weekends, which is when I hack on things like web programming, sound synthesis and databases. I hack on drop.io when I'm married.