#rpm12 Reflections, part one: Wherefore the challenge?

Now that I’m “done” (probably) making music for the 2012 RPM Challenge, it’s time for a few posts reflecting on the experience. First up, the prime question: why do I do this? Or, in a more Shakespearean tone, wherefore the challenge?

Last night on Tumblr, my Internet friend and a musician I greatly admire (and whom I met through my first RPM in 2008), Joshua Wentz, posted:

In Februarys past I took part in the RPM Challenge, but it isn’t for me any longer. I outgrew it, which is a shame, because there was a tipping point for that project where it could easily have become the biggest thing in music. Alas, it is not to be.

The idea that he had “outgrown” RPM stuck with me after reading that. On one hand, it stung just a bit, because here I am participating in RPM while he and several other musicians I met through RPM that year have all seemingly moved on. But on the other hand, it was a sentiment I completely understood, and have felt myself since 2010, the first time I (effectively) skipped RPM. I was so inspired and motivated by my intended album concept that year that I went ahead and recorded it in January (in two weeks), thus disqualifying it for RPM. (Then I did end up submitting an album for RPM, but it was entirely improvised and recorded in one afternoon, on February 22.)

The RPM Challenge has never really been a challenge for me; I typically complete my album in two weeks or less. Finishing in a week this year is exceptional even by my standards, but I never come down to the wire. It’s just not how I operate.

Granted, a big factor in how quickly I produce music is my style, and my approach. My music is almost entirely instrumental and fairly improvisatory, and I use MIDI a lot. I think a huge time-suck for most musicians is lyric writing and carefully crafting a perfect song structure, as well as tweaking mic setups. I have none of that in my process. Plus, it’s just me. If there were more people involved, we’d also have to negotiate schedules and the inevitable conflicts. (I am not without internal conflict, of course.)

Let’s refine the question: Why do I still participate in RPM? I don’t need the external pressure of the challenge to get an album done; I am, if anything, excessively motivated when I start making music. And each year I am less and less involved in the “community” surrounding the challenge, so the timing becomes almost irrelevant.

I guess you could say I’ve outgrown RPM too, but that’s not quite an accurate, or at least complete, description of the situation. It’s also that RPM has failed to grow with me. The challenge got a lot of publicity in late 2007, which is when I learned about it. It was featured on several prominent websites and even on NPR. But its organizers haven’t done anything with it. I guess they’re satisfied to keep it where it is. Unfortunately, “where it is” is a horribly designed Joomla! (yes there’s an exclamation point in the name *shudder*) website with a terrible interface, one that has only had minor surface updates in the 5 years I’ve been looking at it.

But an ugly, unusable website only scratches the surface of what’s disheartening to a serial RPM participant like myself. It’s that apparent lack of desire by its founders to let RPM itself grow that makes it feel so easily outgrown, which is ironic since the entire purpose of the challenge is to spur its participants into growth as musicians by successfully completing an album project.

So, if it’s not the community and the collective experience that compels me, why do I do it? Looking back on my past few RPM albums, I’ve started to notice a pattern: RPM becomes the catalyst to get me to try something new and crank out a bunch of music, which then ends up informing the musical work I do for the rest of the year. I can already feel that coming with this particular challenge.

Pocket Symphonies, built around the idea of using an iPhone as the sole instrument, has been a success, but it’s been an experiment. The music that resulted is like something out of an R&D lab. It’s a prototype. I’ve learned a lot about what does and doesn’t work when trying to make music on an iPhone (which will be the topic of a follow-up post in a few days), and I probably only would have done that with these arbitrary parameters, partly set up by the RPM Challenge and partly by my own vision for what I wanted to do.

I’ve been playing around with iPhone music apps for years, but it was only when I committed to recording an entire album using them that I forced myself to really see what they could do, and even now I feel like I’ve merely scratched the surface. But now I feel like I know how I can integrate the iPhone (and iPad) into my “regular” music-making activities in creative ways.

Beyond production techniques, this album was a chance for me to explore some musical styles I’ve been interested in working with. In particular, I’ve become increasingly interested in the chillwave style of electronic music, especially since falling in love with the theme music from Portlandia, which I have since leared is a song called “Feel It All Around” by Washed Out. I recorded a couple of tracks that I think put my own typically idiosyncratic spin on this style, and I am looking forward to pursuing more of that in the coming year.

Reflecting on all of this, I guess the RPM Challenge is, like life, what you make of it. It’s looking increasingly unlikely that the organization behind the “official” challenge is ever going to develop it into the kind of thing I once wanted it to become, but that doesn’t really matter. And whether or not I only record during the month of February, whether or not I even bother to submit the CD to RPM HQ on March 1, also doesn’t really matter. What matters is finding that source of inspiration that allows a person to channel their creative energies into something tangible. And RPM, whatever it is, still does that for me.

#rpm12 day 2: Does the world really need more music?

One of my tentative song titles for this year’s RPM album poses a question, in humorous song title parenthetical form:

(Does the World Really Need) More Music (?)

I wondered that again as I awoke this morning with Death Cab for Cutie’s “Codes and Keys” in my head. It’s the title track from an album they released last year. It’s a pretty good album. Every time I listen to it I think, “This is pretty good. I should listen to it more often.” But then I rarely do, because there’s just so much really good music being produced these days.

Do I really need to toss my little CD onto the already massive mountain of music (not the most poetic alliteration ever) being produced every year?

Well, that’s not really why we make music, is it?

I want my music to be heard. I want it to be enjoyed by others. But mostly I want it for myself. I have an urge to create that comes from a place I don’t completely understand. But yet I do it. I must do it. Because that’s what I do.

My music isn’t the expression of a troubled soul. I’m not bearing my heart with the music I create. I just have sounds in my head and I need to get them out.

But the creative drive goes deeper. It’s not the most satisfying realization, but I’ve come to learn that on some level, I just need there to be things in the world that I’ve made. In the words of Steve Jobs, I want to make a “dent in the universe.” Existence is so incomprehensibly vast, and we are such an infinitesimal part of it. But, for a few dozen of the Earth’s trips around the sun, we’re a part of it. And, what’s more, we know it.

I guess that drive to simply leave a mark before I’m a pile of dust is the driving force behind a lot of the creative impulse, at least for me.

I used to think that this creative impulse was at least partly tied to an instinct for procreation, that bringing new life into the world was what I really felt compelled to do, for simple biological reasons. But I have kids now, and while they’re great in many ways, it hasn’t lessened that urge to create art.

So, I continue to make music. I explore. I refine. I grow. And I keep trying to get it all out of my head and into the world.

This is not at all where I had intended to go with this post. I was going to just talk about the song I worked on last night, which ended up sounding a little bit like a Trent Reznor/Atticus Ross soundtrack… if all of their soundtrack tunes were 12 minutes long and ended with an extended, unaccompanied theremin solo. But that’s probably not as interesting as probing metaphysical reflection.

The short version of the daily progress report is, last night was another productive session, and I extensively employed two new apps I just discovered last night through the App Store’s often questionable “Genius” tool: Alchemy and SoundPrism. The latter gets an endorsement from Jordan Rudess, which is good enough for me.

The merits of a fresh start

It’s hard to start over. Make a clean break. Go back to the very beginning and build things from the ground up. I experience it all the time in web development. Most of the time, starting over from scratch in this field is seen in a negative light. “Reinventing the wheel” is the standard metaphor. Why do something you’ve (or someone else has) already done all over again? Better to take what you’ve already built once or twice or a hundred times before and just reuse what you can, tweak as needed, give it a fresh coat of paint (so to speak) and call it a day — to keep the clichés coming, fast and furious. Check.

But… on the other hand… did you really do it the best you could on the very first try? Is it another coat of paint on a sturdy, reliable structure that’s stood the test of time, or just another layer of lipstick on the pig? Well, for better or worse that’s what I do, most of the time. It’s what most of us do. Because even if we have the chance, starting over from the beginning means a lot more work, and isn’t what we’ve already got, good enough?

Maybe. But is “good enough” really good enough? Really?

Today my 5-year-old son was bored. BOOOOORED. And he asked me what he could do. I spotted on the shelf above my desk the bulk Legos I had purchased several months ago to keep on my desk at my old job. They’ve pretty much just been sitting in their containers since I’ve been working from home, and I decided it was time to break them out.

So we sat at the table and started building. I had packed them somewhat hastily back when I left that job, and they were still mostly clumped together into the odd, improbable configurations I always liked to build when I was sitting at my desk mulling over a coding problem.

As we began putting the Legos together, I mostly kept these proto-creations and just added on to them or made slight modifications. It seemed too time-consuming and counterproductive to take them all apart and start over again. But then I stepped away for a few minutes, and when I returned, I discovered he had completely disassembled them all. Everything. Nothing but individual pieces, and we had to start over.

I grabbed a few pieces and began to imagine the configuration of whatever it might be that I was about to build. And then the ideas began to flow. I started seeing arrangements I never would have imagined — or, more precisely, bothered to imagine — otherwise. The end result was probably one of the most interesting and (dare I say it) whimsical Lego creations I’ve ever come up with. (And I don’t use the word “whimsical” lightly. Or at all.)

And it never would have happened if I hadn’t gone back to square one and started over.

Thanks, kid. Those of you who are registered users can see more pictures from our Lego project here.