I had a milestone in Robotron gameplay last week:

This is the first time I've cleared a million points! Probably the best classic arcade game of them all!

There's been a fair amount of talk on the pd list lately about doing a new batch of shirts and since I've long thought it might be nice to have a pd shirt, I decided to bang out a design:

Now it's up to the community to decide how much they love it!

I recently acquired a certain netbook so that I could be frugal but still have the ability to hack while mobile. Of course, I have to run Debian...it's a curse...but it rules.

Surprisingly, things work altogether very very well. I still don't think I'm that savvy, but I've gotten things to play together quite nicely. I will create a real page and post my results/settings/findings soon....but I made a stupid simple hack tonight that I thought I'd share.

So I'm running Fluxbox again. It's clean, simple, and takes up very little screen real-estate. It's been a few years, but it's as elegant and non-intrusive as I remember it.

The default keys file for fluxbox has commands that grok asla (via alsactl) and are able to nudge the volume up/down based on the magical function modifier keys (like Fn+F7 or Fn+F8 on the Wind). That's all great...but at least with the sound apps I run (including Flash!), the defaults aren't enough because this "Front" control keeps stomping on things (eg. it apparently needs to be massaged after the Master is massaged). I wish this wasn't the case, it's stupid, I should complain...Whatever.

Scripts to the rescue.

For the MSI Wind, I made three scripts, one does muting, the other two do volume up/down. They look something like this:

#!/bin/bash
for control in Master Front ; do
        amixer sset ${control},0 1+
done
aplay ~/media/sounds/volume_change.wav

The 1+ indicates volume up, change to 1- for volume down.

And then in ~/.fluxbox/keys we can map things like:

176 :Exec ~/bin/volume_up
174 :Exec ~/bin/volume_down
160 :Exec ~/bin/volume_mute

What this provides is two things. First, when you press Fn+F7, for example, the Master and Front volume levels will both decrement. The Front is changed last, so that the actual volume output level is applied. Secondly, the 'aplay' line gives a little chime to audibly indicate the volume level...something akin to the sound that those $2000 Macintoshes make.

I found this bink sound on freesound and think it works quite well.

Until I can create a real page for my Wind setup, scream loud and enjoy the hack.

Just a quick peek at the first set of 3 kolpxnty boards that I had fabbed:

They are not without problems and have not yet been instructed to bend the circuit things, but they will soon. The above is being driven from Pd via MIDI by way of Benito.

More to come...

MySpace has always sucked...so fock MySpace. Well fine, it has it's place, so do the other social nets...

Not only is archive.org officially and formally a nonprofit with library status, they are also classified as the bee's knees, the good stuff, what's good, what matters.

Although this is nothing new, I have to keep reminding myself (and you!) just how fundamentally RAD it is that I can listen to an amazing recording of a noise performance in Estonia a mere day after it was made. The future really is now. This is what radio should be, or at least will be...once we all work around the restrictions.

I keep coming back to this idea...about ditching the restrains of monetized networks, for-profit tools, and encouraging people to seek enlightenment. Seek answers through knowing the potential of your tech.....

Learn what's out there, what can be done freely, truly freely, let's build tools to help people get free...

So my pal Mykle has done this EPIC event called LIGHTBAR to cheer people out of their seasonal affective disorder during February in Oregon. If you can't see the victory in building a GIANT and BRIGHT bamboo-event-party-dome, by hand, in the middle of winter, then you need to be poked (with sharp bamboo).

A few of us from dorkbot PDX have been peripherally involved, even contributing some works.

My friend Brian and I collaborated on a light-based project dubbed the RETINAL TATTOO GUN. The concept involved a series of bright flashes intended to [temporarily] imprint iconic imagery directly into the retina with strong after-images (ghosts).

We had a semi-working prototype up at LIGHTBAR last weekend before it collapsed(!!!) this week. This iteration of the retinal tattoo gun was a pretty big technical failure, but it was a fun project and we have a nice foundation going forward.

The circuit I designed/built had a series of issues, the worst of which was some form of ground bounce or inductive jibber jabber that caused all 8 flash channels to fire when any of them fired. Turns out that yeah, it's nontrivial to sequence a bunch of disposable camera flashes.

The day of installation we also found out that the repurposed viewmaster switch was connected in a way that caused the flashes to trigger when the advancer jobby was directly in front of the slide...so most of the light power was dampened. Whoops, doh!

We hope you enjoy the above image, and we hope to have something dangerous, compelling, and electrical to mount to your face in the near future.

Another victory for open source.

I've been trying to stay fairly cutting edge again at home -- with my Debian unstable and pretty up-to-date kernel builds. I'm usually surprised at just how easy things are now...

But my crappy little phone stopped automounting for some reason when I plugged it in. I managed to search and find this bug thread which suggested a similar problem and a patch for Nokia phones. A few minutes later I had downloaded the patch, applied it, and then tweaked it to match the manufacturer/product IDs of my silly phone.

It ended up looking something like this:

UNUSUAL_DEV(  0x0474, 0x0749, 0x0000, 0x0481,
        "Sanyo",
        "Sanyo Mass Storage",
        US_SC_DEVICE, US_PR_DEVICE, NULL,
        US_FL_FIX_CAPACITY),

One kernel compile and reboot later and it worked like a champ.

Of course, all this begs the question "Why did it happen in the first place?"...which is another topic completely. Having the ability to take ownership and fix the problem to get work done (until the upstream [kernel]) is priceless. You'll never get that same experience with your closed source OS.