With all due apologies to Bill Bruford (and the rest of Yes)

Yes, Fragile, 1971Endure it if you dare.

Things were just different back in 1971. And if you don’t believe me, consider this: a very successful rock album from that year was Fragile by Yes.

This album contained not only three tracks near or longer than eight minutes each, but five brief tracks that were the individual creations of each member of the band. Some members were not so enthusiastic about this approach, most notably drummer Bill Bruford, whose contribution was an awkward, 37-second noodlefest for drums, guitar, bass, and organ entitled “Five Per Cent for Nothing” [sic, although apparently that’s how they spell it in Britain].

Only 37 seconds, you say? Or more to the point, only five percent, you say? I have now attempted to rectify that shortcoming.

The piece as it originally appears consists of a complex rhythmic pattern, played through twice by the band. Well, if twice through constitutes five percent, simple arithmetic tells us that 40 times through will yield the full 100%. (It also clocks in at a pleasing 11:11.)

So here you go…

[audio:http://blog.room34.com/wp-content/uploads/underdog/100pct.mp3]

If you like/can tolerate this, I encourage you to consider purchasing the full album. (For what it’s worth, I myself have purchased it in one form or another no less than seven times.) It features some outstanding playing and great songs, including my favorite piece of music in the history of human civilization, “Heart of the Sunrise.”

But if you’re in the market for something a little more current… a little more seasonally-appropriate… a little more ridiculously titled, then I would steer you no further than to Chris Squire’s Swiss Choir, a drunken joke new Christmas album featuring Yes bassist Chris Squire, drummer Jeremy Stacey (formerly of Sheryl Crow’s touring band and more recently of the briefly-reformed-and-now-once-again-defunct lineup of Squire’s pre-Yes band, The Syn), and ’70s-era Genesis guitarist Steve Hackett.

Normally I would look at something like this and think, “Mannheim Steamroller, but somehow, incomprehensibly worse.” And yet, from the samples I checked out online, it’s surprisingly not complete shit! “Complete” being the operative word. When I emailed a friend about this album, with the subject line “Holy crap,” he replied “I think you have just come up with the perfect two word review for this album.”

If by any chance you do choose to purchase it, I would implore you to consider doing so via this link to the iTunes store, so they’ll know who recommended it! (OK, they won’t. But at least I’ll get a tiny piece of the action.)

’70s flashback (literally)

Even though I’ve never dropped acid, looking back on the children’s television I absorbed like a sponge in the late ’70s, I think I got enough of the experience. Case in point:

I’m lazily linking over to this on YouTube, but I actually watched it again for the first time in 30 years earlier today on the Sesame Street Old School 1974-1979 DVD set I just bought at Target. Which is not — at all — to say that I hadn’t thought of it countless times in those intervening 30 years. The “plastic house” and the freaky yo-yo dude in particular are burned eternally into my memory.

Now, I know a lot of people my age are going to have a nostalgic recollection of clips like this, but I wonder how many are as deeply imprinted with these iconic images as myself. Back in 1978, when this clip actually aired, I was at my absolute peak of Sesame Street viewing and on most days I spent at least 3 1/2 hours watching the show. (We got two PBS stations; one aired it at 8:00, 11:30 and 4:30, and the other at noon and 3:00.) I saw many of these segments more times than I can count. And speaking of counting, fortunately, I didn’t need, at that age, to learn to do so in Russian:

The first time I watched this I was so in awe of the ambitious yet failed effort to squeeze the copious syllables of the Russian numbers into the fast rhythm of the song, I didn’t even pay attention to the fact that the entire “12” segment consists of U.S. landmarks (Statue of Liberty, Washington Monument, Mount Rushmore, etc.). I wonder when exactly this clip aired on Russian television, and whether anyone involved in putting it on the air realized what it was depicting wasn’t just drugged out hallucinations. (Well, it was, but not just.)

Site girth expansion

I’ve just finished a modification to the site design. I was starting to feel a bit too confined by the narrowness of the old layout, so I’ve basically kept things intact design-wise, but I’ve expanded the layout to be more suitable to today’s 1024×768-or-greater standard screen resolution. I’ve also bumped up the size of the type slightly.

The only design element that’s noticeably different is the little greenish weirdness at the right end of the photos in the header bar. This was something I spent a great deal of time developing for an old, shortlived design that was part of my quickly-abandoned experiment with running the site on Drupal. I may end up getting rid of it again; I just thought it deserved a second chance.

Now then, if you’ve actually visited this site sometime before, you may find the pages are looking somewhat garbled; sadly that’s the side effect of keeping a lot of the filenames the same; your browser likely has old versions of these files cached. Hit the Refresh button a few times or perhaps clear your cache. I did the Refresh thing, but I had to hit it about 4 times before all of the files actually updated. Sheesh, you’d think I was using a Microsoft product or something, not Firefox!

The Case of the Missing Nav Bar

I will admit, sometimes the problems I encounter in Internet Explorer are simply due to slight differences in browsers’ implementation of HTML or CSS or whatever, and I’m just not properly accounting for the way IE does certain things. Other times, it’s true, they’re due to a flat-out bug in my code that Safari and/or Firefox (usually “and”) will just graciously accept, whereas IE will not. (The cases where IE catches errors that Safari and Firefox permit, however, are rare compared to the vast, cluttered landscape of bad code that IE welcomes with open arms but that Safari and Firefox rightly reject.)

And then there are the cases such as the one I encountered today. There’s no way around it. I can’t find a nicer way to put it, IE is just plain fucked up.

Yesterday I was going along innocently enough, demonstrating to a coworker the site I had been working on for him. As usual I had worked with Safari and Firefox as my test browsers, firing up IE through a remote connection to my PC as needed to make sure things weren’t completely off track. (In a perfect world, I would never have to do this, of course. But, well…) And then, wham! Of course this kind of problem only rears its head when you’re showing your work to someone who has the authority to reject it. I was convinced it was a fluke on his computer, but sure enough when I went back to my desk, I observed the same thing happening in IE on my own PC. Time to hit the brakes once again and go into IE debugging mode.

I tested all of the obvious things. No luck. So I dug a little deeper and started testing the more obscure, but at least logical things. Still nothing. And like so many times before, I was reduced to just randomly trying anything to see if I could get a different result, no matter how seemingly absurd.

Fortunately it only took about an hour to track down the problem this time. But as usual there was no satisfying resolution, no “Aha!” moment as I suddenly recognized a stupid mistake I had made. Oh no. The problem was that the CSS definition for the <div> tag containing the entire body of the page specified a background color. Of course! (No, not of course, as this should not have any impact whatsoever!)

*SIGH* Seeing as how that background color specification wasn’t technically necessary, I removed it. Problem solved. Frustration with Microsoft, higher than ever.