Sunday, January 14, 2007

Mallards

For the last couple weeks, I've been working on artwork for Tale, the MUD, you know. That is, two weekends ago, I got back from visiting the family down south and had an itch to make something, so I've spent all of my off-time since scratching my brain and mouse-pad with fervor. The first thing I drew was a multi-layer sea and sky vessel graphic, the Mallard. The Mallard is one of the seminal concepts for Tale, a Norse style galley with steam and blimp upgrades. It's the focal point for blending a mediaeval theme with a fantasy theme with a Victorian sci-fi (steam-punk) theme. I finished it, cranked out some permutations, called it amazing, and moved on. Since then, I've populated a wiki with bunches of monsters, items, and game design memes.

Today's project was to finish writing the automation for generating permuations (sail plans) of the Mallard. To that end I did a bunch of technial stuff. Skip to the next paragraph if you don't care about technical stuff. The mallard graphic proper is a single SVG file with something like 120 layers. These layers include such wonders as "mizzen-top-gallant-yard", "bow-jib-outer-sail", and "sweeps". Constructing a mallard graphic is a two step process replete with danger. The first step is to filter the graphic for the desired layers. I've constructed several layers files which include all of the necessary layers for a particular sail plan. The second process is sorting those layers to preserve the three dimensional illusion. To this end, I have several sets of "rules" for sorting the layers, rules like "the yard arm is behind the mast", employed exhaustively and brutally. There's one set of common rules, one set of rules for ships that appear to be sailing away from the observer, and one for vessels that appear to be sailing toward the observer. Using these rules, I construct a "digraph", merely a set of layer names associated with layers that are known to be behind them, and then perform a "topological sort" on those layers. I do this all with the command line, so constructing boat-100.png looks like: cat mallard.svg | svg-filter boat.layers | svg-sort rules boat.rules | rsvg -w 100 - boat-100.png. That process applied iteratively renders our 29 (so far) selected sail plans. I can't wait to play a game where these vessels are set in bitter competition and players scramble to arrange their sails to catch the wind and their prey or their daring escape.

So, here, in all their glory, selected permutations of a mallard.

Mallard Ship

Sunday, October 22, 2006

Euphonium

I bought a new euphonium, a Willson 2900 S. It's a four key, compensating, upright, silver (shiny) instrument, with some amazing craftsmanship. I got it on ebay from Mathews Music in Holland for 5k$ including shipping. I've doubled my roommates' ration of obnoxious tuba music.

I took the new euphonium to Ohlohne Tuba Ensemble rehearsal yesterday. The horn was a treat to play. Everybody there has really nice horns, but the Willson is among the best of the best. One fellow who I believe plays a Besson said that the Willson is the Swiss watch of euphoniums. Looking and feeling the craftsmanship and feeling the tolerances, I would have to agree. It's an amazing machine.

I finally grok what "compensating" in "compensating euphonium" means: I no longer have to "compensate" for the sharpness of every note between E flat 2 and pedal B flat by fingering them one half step lower, and I don't have to bend down to the B natural from C. The horn just has a continuum of chromatic pitches all the way down with orthogonal fingerings with those an octave higher on a three key horn.

Kris and his Euphonium

Sunday, October 1, 2006

Cix Rant 23

Let's be clear about at least one thing. Right is affirmative. Left is negative. This means the "enter" key is on the right; the "escape" key is on the left (the exact opposite left, horizontally orthogonal to the enter key, where the caps lock isn't). The "Ok" button is on the right; the "Cancel" button is on the left. Sidescroller games go from left to right. Forms do the same. New panels appear on the right; old panels disappear to the left. Right is deeper in the file system; left is higher.

Commands are on the bottom. Status is on top. This means command lines are on the bottom. Command buttons are on the bottom. Toolbars are on the bottom. Menus are on the bottom. Location bars are on the bottom. Titles are on top. Status bars are on top. The date and time are on top. Progress notifications are on top. Cursor location information is on top. If it's imperative, it goes on the bottom. If it's functional, stateless, or informational, it goes on the top.

The newest stuff is on the bottom. Moving up, stuff gets older. This means that what your buddy said last is at the bottom of the message buffer. This means recent command output is on the bottom of a message buffer. This means modal notifications are on the bottom (like security warnings, notification bubbles). This means the most recently received email is on the bottom.

Let's get serious about consistent, easy, simple and learnable human user interfaces people.

Monday, September 11, 2006

I'm Fine

Ah, anger, such sweetness coursing through the veins. No better a time to write down your thoughts than in the unforgiving, irrational haze of rage.

So, I made my first call to 911 today. It was by no means all that important, but I'm given to the impression that it's a good way to get in touch with police dispatch. I felt that the police should know that the traffic lights at De Anza and Highway 280 were out of order, flashing red, at possibly the worst time possible: rush hour. To avoid trouble, it would be prudent to dispatch officers to direct traffic until the problem was solved.

I did not call lightly. After I had driven through the mess and it showed no sign of abating, I thought for a few moments about whether it would be worth tying up the emergency response line for something like this. I figured that almost nobody else was going to; I learned that one in my psychology class: dissolution of social responsibility. Given the circumstances, I figured that an accident was probable. I've never called 911 before, so I also figured that I should overcome my fear of the whole process. What probably tipped the scales though is that today is September Eleventh, and I'm a sucker for irony, particularly when numbers are involved. Here follows (annotated) my conversation.

    Dispatch: S*** *lara ***Emergency*** ********. (cell phone issues)

    Kris: I'm sorry?

    Dispatch: You called 911 emergency. Do you have an emergency?

    Sarcastic Kris: No, I'm just lonely and nobody else answers my calls.

    Real Kris: Ah, yes. The lights at De Anza and 280 are flashing red and traffic's highly backed up. We need officers directing traffic.

    Dispatch: That's the Sheriff's Department.

    Angry Kris: You are a police dispatcher, right?

    Dispatch: It's rush hour.

    Angry Kris: This I can see.

    Dispatch: You treat a flashing red like a stop-sign.

    Angry Kris: Yes, yes. I'm not a pedestrian. I earned the right to pilot this explosives-propelled-two-ton-brick-of-death by passing the twenty question multiple choice test just like everyone else out here. The problem isn't a matter of understanding what I need to do. I got through the intersection some time ago. Don't assume that I'm a whiny punk stuck in traffic crying for help. I'm trying to help here. The problem is throughput. There are stop-lights here because stop-signs don't have enough throughput to support this kind of traffic. The stop-lights are broken. We need uniformed officers to direct traffic because they can emulate the throughput of a stop-light until they're fixed.

    Dispatch: As long as everyone obeys the law, there will be no problems.

    Angry Kris: One would think that you, more than any person in the world, would appreciate how dreadfully naive that statement is.

    Real Kris: Alright, thank you very much.

    Angry Kris: I'm going to hang up now because giving you a piece of my mind is not what this phone line is for and I don't want to keep you from your fiddle practice.

    Dispatch (suddenly cheerful): You're welcome.

Monday, August 7, 2006

Garage Band Foray

So, I've made some preliminary stabs and authoring music in GarageBand.

"Dramatic Overture" was my first attempt. I experimented with dynamics and how well some of the synthesizer inputs behaved in extremely low octaves. Horns were interesting.

"Theme", for lack of a better word, was my attempt to produce a Theme with GarageBand's keyboard keyboard and some editing. The form for the theme is vaguely ABAB', and the form of the piece is vaguely ABA'. It gets messy toward the end. I'm pretty sure that this is a bad thing, but I think I'll leave it as is and call it "high art". Or--honesty hurts, so be nice--the counter melody is improvised; that's why it's crappy.

This was an attempt to get some more meat out of a piece. So far most of my work has been a blind stab into the solution space that GarageBand provides, so there's very little chord progression or polyphony. Oh well, this one continues in that vein. Let's call it "modal" and pretend it was on purpose. I think I succeeded to produce an interesting mood with this piece, with a sort of schizophrenic fight between major and minor hemispheres with no definitive winner.

Wednesday, June 21, 2006

Net Neutrality

Tim Berners Lee developed the technology that lets us view each other's web pages. The web grew exponentially from that humble foundation because of a simple premise that, until now, did not have a name. Now it has a name, "Net Neutrality", because myopic capitalists, specifically telecommunication companies, have realized that they're sitting on a gold mine built entirely of our purses. Yes, that means your purse. They want to hold communication for ransom using their government protected monopoly. Tim Berners Lee has a blog entry that you should read.

Friday, June 9, 2006

Re: Prophecy 2

It was, after all, just a matter of time: Prophecy 2 fulfilled, except that they made the RSS feeds unnecessary for day to day use. Maybe add publication features later; let's call that Prophecy 2.1.