A couple of times since I put out those Thing a Week CDs I’ve gotten emails from people asking me why Code Monkey is in mono. Usually I was all “Huh?” and then sometime later would kind of forget about it. It’s not in mono, it can’t be in mono, why would it be in mono?
Well guess what? Code Monkey is in mono. I just noticed that the track I delivered to the CD production place way back when is about half as big as it should be BECAUSE IT IS IN MONO.
Nevermind that I didn’t notice at the time, nevermind that I didn’t even bother to check when people told me over these last couple of years. What’s amazing to me is that it hasn’t really mattered in any significant way. I’m sure I sweated like crazy over the stereo placement of this or that element during the mixing process, and then I just plastered over all those details with stucco, and turns out nobody really cares. Not even me, apparently. This is a lesson that I learned (or rather, failed to learn) many times over the course of Thing a Week: that thing you’ve been working on forever, buffing and polishing to get to that last 2% of excellence? It’s done. Finish it and move on. Hey, at least it’s not in mono, right? Because that would be a huge disaster with serious consequences.
And so you know, this error will be corrected in the forthcoming greatest hits CD “JoCo Looks Back” that’s being manufactured even as we speak.