Floyd Collins or: How I Learned to Stop Worrying and Love Dynamic Range

April 8th, 2012

If you’re reading this, you’re probably involved in the audio industry to some degree and are aware of such issues as the “loudness wars” and the lack of aural dynamic range in popular media. If you’re reading this and not in the audio industry, then you’re probably an overly-polite friend of mine, in which case – thank you, I appreciate the effort, but really – it’s not necessary. You can go do something else; I won’t be offended. The appropriate brownie points have been credited to your account.

While I’ve understood these concerns over dynamic range, I haven’t necessarily been a huge advocate of them. I like things loud and I think a lot of modern music actually works well being heavily limited (the exception being that Adele album that’s getting way too much airplay right now). Partly because of my own personal tastes and partly because of the general lack of silence around me, I haven’t truly appreciated the impact of quiet.

Until now.

As I mentioned earlier, I’m the sound designer on a local Boston production of the Adam Guettel musical Floyd Collins. Working on this show has helped inspire me to jump on the “dynamic range” bandwagon, so-to-speak. 

There are several points in our production, where, due to some combination of score, script, staging, budget, and/or layout of the theater, there are moments of intense quiet – so quiet, in fact, that the noise floor of my audio equipment, the theater’s HVAC system, and even my turning the pages in my script are real concerns. As the sound designer, I didn’t plan for these moments, nor did I seek them out,  but I can honestly say that I am glad to have had them foisted upon me; I’ve adjusted my design to accommodate them and my design is better for it. Ironically, had I had the budget to mic all of the actors like I’d wanted, the average volume of the show would have been louder and I probably would have missed these moments.

Starting out on the project, I was excited at the prospect of making a bunch of horrendously loud, building-shaking cave-in cues and scaring the crap out of people. I do get to do that and yeah, it’s awesome. But my unexpected treat has been working with these moments of quiet, where subtlety and softness can be used to impart a sense of claustrophobia, surrealism, apprehension, and dread. If you’re on a project and in a position to create a place of real silence, exploit it, because it has the potential to be as powerful as, if not more powerful than loudness.

If you’re in the area and interested in seeing it, the show runs through Apr 14. Tickets are available through: www.bostontheatrescene.com


Newsy News: Another Musical and Some Gamey Stuff I Won’t Say Much About Yet

March 1st, 2012

So March and April are shaping up to be pretty busy. I’ve signed on to sound design a second show with Moonbox Productions; this time, we’re putting on Floyd Collins. When I say “we,” I really mean “they,” because they do all the heavy lifting and are just kind enough to let me hang out with them and make noise and spend money. I think they keep me around, because I can reach things on top shelves and because I keep the lighting guy, Jeff, occupied. (hi Jeff!)

I feel a bit silly getting all gushy and excited about a project (I am a professional after all, right?), but this is such an awesome and talented crew of people, I almost worry about not appreciating the whole experience while it’s here.

Anyways, before I get too mushy and make the production meetings awkward, about the show itself – it’s a musical based on the true story of some guy in Kentucky in 1925 who got stuck in a cave and died and all the people who profited off his misfortune instead of helping him. Think Baby Jessica before tv and with a tragic ending. Yeah, it sounds gloomy, but it’s good, so you should come see it and support the arts and help us pay rent and buy beer (not necessarily in that order). It’s playing at the Boston Center for the Arts in the Plaza Theater and opens Friday April 6. We run all of that weekend and the following weekend. For more information, including gorgeous headshots and hilarious cast/crew bios, visit http://moonboxproductions.org/

Game stuff: for the last couple months, I’ve been working off-and-on (a couple days, every couple weeks) for <game company> doing <game-related stuff> and a couple weeks ago, they asked me to come work for them on a temporary, full-time basis, at least through this phase of <my particular part of the project>. So between that and the musical, I’m taking at least a 5-6 week leave of absence from Mercenary. I’ll probably be going back here and there at night and on weekends to help with some of the computer and bookkeeping things that only I know how to do, but during the days, someone else will be answering your e-mails and taking your phone calls. Actually, I try to avoid talking on the phone to customers as much as possible, so someone else was taking your calls already. But it was me who punched your info into the credit card machine, so that’ll be different. I’ve trained my replacement to copy and paste his generic responses with the same passion and concern that you’ve come to expect from me.


Hey, Now I’m a Theater Guy!

November 16th, 2011

This past weekend, I wrapped up production on my first theatrical adventure ever: a 6-show / two-weekend run of “Lucky Stiff,” put on by Moonbox Productions and performed at the Somerville Theater in Somerville, MA. The show is something of a musical combination of “Weekend at Bernie’s” and “Brewster’s Millions,” whereby a hapless shoe salesman from England is bequeathed a $6 million fortune from a dead uncle he’s never met on the condition that he take his uncle’s corpse on a trip to Monte Carlo for one last round of gambling and womanizing. Should he fail to meet all of the requirements set forth in the will, the money will be awarded to a Brooklyn dog shelter. Love, intrigue, and hilarity ensue.

My role in this production was as Sound Designer and FOH Engineer. I was assisted by System Tech/A2 Brian McCoy from Myrna Johnston Audio, who provided the PA system. The rig was (7) Meyer M’elodie cabinets over (2) Meyer 600HP subs per side with a couple of Meyer Minas as center fills.

Same system in the same room, for a different show.

Out front, I had an Avid SC48 and a computer running Stage Research SFX playback software. All of the performers were wearing Sennheiser wireless packs and lavalier microphones.

The rig sounded great. The Somerville Theater can hold about 700-900 people, depending on the configuration and this system was spec’d to cover a packed house. Our shows wound up running 10-15% capacity, so we had more than enough headroom. Interestingly enough, the subs were used more for ballast and elevation of the top cabinets than they were for actually providing low end. It’s not possible to fly speakers in this theater, so everything has to be ground-stacked. The curvature required to cover the lower seating area with a ground-stacked line array results in some precarious weight distribution – those speaker stacks were very top heavy and front heavy even with a couple of giant subs bolted to the bottom.

I had never used a digital console in a live show before, and I was a bit worried that I wouldn’t be able to grab certain controls fast enough if things got hairy. This could have been an issue with other consoles I’ve tried out in showrooms and product demos *couch*LS9*cough*, but the SC48 was great.

The Dan Cave.

If you’ve ever used a Mackie D8B, the layout and workflow is very similar. They’re both easy and fast.

But there was a little more to the show than fancy toys. In theater, the “designer” (either lighting or audio) is the person who develops the aesthetics and the cues and specs the system, but is not necessarily the person who actually operates the console during the show. I did both and, in fact, the “design” side of this show was rather minimal. There were 1-2 dozen sound effects cues that were all rather simple and straightforward. The show is a campy farce and in my opinion, that aesthetic was best served by sound cues that were simple, straightforward, and relatively familiar. The bulk of my work was actually people-wrangling and engineering the show. I was responsible for interfacing between the audio equipment providers and the eager, yet audio-inexperienced folks at the theater company. This included not just the producer (who pays for everything), but also the director and (because the system was stacked on the stage) the set designer. It SHOULD have also included the lighting designer, but that didn’t occur to me at the time (sorry Jeff!).

Engineering the show was relatively painless. Not having worked in theater before, I hadn’t developed a preferred workflow, so I had to learn as I went along. My initial thought was to ride the vocal faders during the show, but one rehearsal was enough to convince me of what a bad idea that was, so I took the time to write out and program into the SC48 all of the mix cues for the entire show. “World of difference” would be an understatement. Beyond the technical side of engineering, the talent was really, really good. If you’re reading this, you’re probably a sound guy and you know what it’s like to have to deal with lousy talent or crappy source material. This was neither. These guys showed up and sang their asses off, and I just made them louder (and some of them didn’t even need that). The pit band was fantastic. I barely had them in the house at all, because they just mixed themselves for the entire show. Oh if only every band could do that.

Everybody on the show was extremely talented and wonderful to work with. I feel really spoiled, because for my first theater gig I got good talent, great people, a good budget, a killer system, an overqualified A2, a nice room, and a paycheck. None of these are ever guaranteed on a show and many are rather hard to come by.

As of about an hour ago, I’ve signed on to work with this same theater company for their upcoming production of “Floyd Collins,” which is a musical about a guy who gets trapped in a cave and dies. Folk music, surround sound, and copious slapback delay FTW!


Farm Stuff pt 2: the Truck

August 13th, 2011

Blogging Rule #723: Don’t wait 6 weeks to write about something. If you’re like me, you’ll forget interesting details.

<:-b

As discussed in an earlier post, I spent the Independence Day weekend at my parents’ farm in central NY and one of the things I wanted to capture while out there was the engine on my father’s Ford F-250 Super Duty pickup. I mentioned in that post how I have a tendency to overdo things and, given the opportunity, I would have done so with the truck with mics aimed at the engine, at the exhaust, at the wheels, in the interior, and anywhere else I could’ve come up with. But I only have 2 channels on my 702, so I’m limited in just how crazy I can get (that is, until I get a 2nd recorder, mwahahaha).

This is/was for a game audio project in which I wanted to have the engine sampled at multiple rpm’s which would then be pitched up and down and crossfaded with adjacent samples so as to smoothly cover the entire range of engine speeds.

For those who are interested: I’m out of the loop these days so maybe things have gotten more advanced, but at least when I was in high school & college, low-mid level sample-based digital pianos would do the same thing in order to save space in memory. Keyboard manufacturers would sample, for example, each ‘C’ note and would shift the pitch of that recording upwards to cover the notes C# through F immediately above that original C, and pitch the recording down for the notes G through B directly below that C. (I’m not sure if the F# was pitched up or down, since that’s right in the middle, but you get the idea). The end result is that you only have to store the recordings of one note per octave instead of twelve.

Since I only had two tracks with which to work, I couldn’t get 8 microphones on the truck and record a half-dozen different perspectives at once. My buddy Watson Wu has more experience recording cars than anyone I know, and not crappy cars either: Pagani Zonda, Porche Carerra GT, Aston Martin DBS, many Ferraris (California, F50, Enzo, and more), Lamborghini Murcielago, Shelby GT500…. And when he’s not recording supercars, he’s recording machine guns. His Facebook photo albums are insane. But anyways, since he has a fair bit of experience with sort of thing, I asked him how he would record the car if he only had two onboard mics. His recommendation was to put one on the engine and one on the exhaust.

I decided later that didn’t actually want a mono recording (which is what you’d have if you just combined the two), so I decided to try taking one pass with a stereo pair on the engine, and another pass with a mic on the exhaust w/ the extra channel to be decided on the fly (perhaps a contact mic somewhere near/on the engine compartment), and then figure out a way to sync them up after the fact. However, when I started soundchecking, I found that there wasn’t much sound coming out of the exhaust pipe at all. It turns out that on this truck (and on many Fords, from what I’m told) the bolts holding the exhaust manifold to the engine block are rusting and causing the seal to fail. This means that the sound that would normally come out of the tail pipe is now coming out of the wheel well. It also meant that I could take Watson’s advice and get both the engine and the exhaust in one shot and in stereo:

 

Boo-yah

 

There’s another mic in the same position on the driver’s side. Here’s what it sounded like:

Next, I took another pass with the microphones pointed at the engine itself:

The audio:

Originally, I had planned on making these recordings while the truck was moving, because engines sound different when under load and accelerating, under load and decelerating, and just sitting in neutral. I wanted the real thing. I brought along a couple Latch Lake Xtra boom mic stand extenders, thinking I could mount them to the arms holding on the side-view mirrors.

I thought wrong.

The arms are too wide for the mount on the Xtra boom and even if they hadn’t been too wide, I would have still had problems. The cross-section of the arms isn’t round, it’s elliptical. Because of the way the Xtra Booms clamp on, this elliptical cross-section would have killed one of the axes of rotation that I would have needed to position the microphone, rendering the whole process futile. So the LatchLake’s went back in the suitcase and I was stuck getting the bulk of my sounds with the truck parked, in neutral.

In doing this, I learned that maintaining a steady engine speed on this truck, without any load, is incredibly difficult. In fact, the throttle was so sensitive that I couldn’t keep it steady with my feet; I had to lay down on the floor of the truck and press the accelerator pedal with my hands. I imagine this would have been easier had the truck been on a dynamometer, because the resistance would have moderated some of the finnickyness of the engine.

I did try recording the truck while out driving, but because of aforementioned mounting problems, I couldn’t use my regular microphones. Instead I used a couple of contact mics taped to the hood (or “bonnet” as some would say):

If you can’t see it well enough, here’s a closer shot:

These things aren’t marketed as “contact mics” per se; they’re drum triggers that a client left at the studio several years ago which I’d forgotten about until I stumbled upon them in a drawer the day before I left on my trip. Drum triggers and contact microphones are essentially the same thing: piezoelectric transducer elements with a preamp or impedance matching circuit. With these particular devices, the preamp is designed to clamp onto the rim of a drum, which conveniently allows it to also be clamped to those plastic shield things that keep rain from flying in your window. However, because they’re made for drums which don’t cover a lot of real estate, the attached cables are pretty short. Because of this, I had to place the transducer elements rather high up on the hood, as you can see from the pictures.

The audio:

An interesting perspective, for sure, and one that I’ll keep in mind if/when this comes up in the future. I’m pretty sure that the rattling you hear is the hood bouncing up and down as we hit bumps in the road. I never realized there was so much play in a car hood. It would, obviously, have to be secured tightly for any future attempts.

Overall, I’m happy with the quality of the recordings. The content of the audio (e.g. the engine sounds themselves) were good, but not as good as I’d hoped, though in hindsight, I suppose it was rather naive of me to think that I could hit one out of the park on my first try. As I mentioned earlier, it was very difficult to get the engine to maintain a steady speed while in neutral; this ultimately meant that I didn’t get all of the evenly-spaced incremental recordings I wanted (e.g. 1000 rpm, 1250, 1500, 1750, etc). I had to take whatever I could get. Second, when recording on the road, try to use something with a manual transmission. Because it shifts gears for you, an automatic won’t give you the consistency over time that you need. Now I understand why vehicle recordists use dynos instead of taking the cars out on the track.

For the audio nerds out there (seriously, who else would have made it this far?), the microphones were Mercenary Audio Mfg KM-69 small diaphragm cardioid condensors and the recording deck was a Sound Devices 702. I left the drum triggers at work and I don’t remember what brand they are. It doesn’t really matter, though – anything should work.


Farm Stuff pt 1: “Vacationing as an Audio Nerd”

July 20th, 2011

If you’re a fellow audio dude, you may recognize the title of this entry as a blatant rip-off of Shaun Farley’s post on DynamicInterference.com. There’s a reason for that. I’ll get to why in a bit.

I took advantage of the long 4th of July weekend by going to visit my parents on their farm. As you may imagine, there’s all sorts of wonderfully noisy machinery hanging around a farm, so I brought the main rig as well as any extra mics and other bits I could think of. I don’t get out there much, so I wanted to maximize the recording time I had, be ready for any contingencies that arose, and come away with a bunch of quality samples. Regarding contingencies, I can be pretty neurotic when it comes to covering my bases. To illustrate, this is what I brought:

  • (1) Sound Devices 702
  • (3) Mercenary Audio/MA-Mfg KM-69 cardioid condensor mics (needed 2, brought an extra just in case)
  • (1) Sennheiser MKH-416T shotgun mic
  • (1) Rode NTG-2 shotgun mic
  • (1) Beyerdynamic M88 figure-8 ribbon mic
  • (1) Shure SM57 cardioid dynamic mic
  • (2) Drum triggers/contact mics I found in a drawer at work the day before I left. (mine now)
  • (2) DIY contact mics (I didn’t trust either set of contact mics to work correctly, so I brought 2 sets)
  • (1) Palmer PDI09 DI box
  • (1) Axmax DI box
  • (2) Rycote WS-4 windscreen systems
  • (1) Sabra-som X-Y stereo bar
  • (1) K-Tek boom pole
  • (3) Mic stands
  • (?) Cables

 

For 2.5 days. <:-\

 

There’s a game mod project involving integrating engine sounds that I’ve been messing with for a while and the biggest hurdle I’ve had so far (aside from general lack of motivation & discipline) is lack of sufficiently detailed base source material: namely, steady engine recordings at small rpm intervals. So my primary targets on this trip were my dad’s two tractors and his F250 Super Duty pickup. I figured that between the 3 of them, I ought to be able to get something usable. The secondary target was the hay conveyor, with potential targets of opportunity including everything from broken motors to weapon foley to wildlife and thunderstorms.

 

No plan of operations extends with certainty beyond the first encounter with the enemy’s main strength.

- Generalfeldmarschall Helmuth von Moltke the Elder

 

Not that my parents could be described as “the enemy” (unless I’m needling my dad about politics, but that’s another matter…), but I think that in a general sense, Moltke’s famous quote about flexibility and the need to adapt to circumstances is applicable to my weekend back home. (I also unwittingly mirrored his hyper-detailed approach towards planning. Maybe I’ll have to read more about this guy.) I had a list of assets I wanted to capture, a suitcase full of gear with which to capture it, and an extended weekend of gorgeous weather in which to do it. I was good to go.

But I wasn’t at my parents place for 20 minutes before I came to the same realization Shaun did in the aforementioned post: I’m on vacation. I love hanging out with my family; I only get to see them twice a year, and I’m planning on spending the whole weekend listening to headphones and shoving microphones in things?

Fuck that. Recording takes a back seat to things that are actually important.

I did get a few things which I’ll detail in subsequent posts, but not nearly as much as I’d originally set out to record. And that’s ok. Instead of collecting sounds, I spent the weekend playing dominoes with my family, catching up with old friends, grilling steak, gorging myself on chocolate chip cookies, and sitting by the fire for hours staring at this:

 

Peace

 

It’s good to have your priorities in order, eh?

 

 

 

Some other non-audio pics from the weekend:

 

Doe in Front of a Turkey Blind

Me & Mom (I'm the one in the hat)

More mesmerizing than it ought to be.


Trains pt. 5 – The 1:15

May 16th, 2011

Why I don't sleep at night.

About a month ago, I moved into a new apartment. It’s a great apartment – it’s really close to work, the roommates are cool, the house is great, I have a whole floor to myself, so there’s a ton of space and privacy. One catch that might concern some people is that it’s close to a train crossing (like, close enough that I can look out my window and see it). I wouldn’t normally consider this a big deal – as you can tell, I like trains, and even more generally, I’m not one to get worked up over loud noises now and then. Having researched the rail traffic patterns in this area, I know this particular branch gets very little traffic. My last apartment was within sight of both the commuter rail AND the turnpike, which are both MUCH more heavily trafficked than this new one, and I never had a problem at the old place. As it turns out, this new one only gets used once a day (occasionally twice a day), and only Monday through Friday.

Perfect, right?

Well… That one time is at 1:15am. The second time is at 4:15am.

Ok, so there’s a bunch of rumbling in the middle of the night – no big deal, right?

Well… On this one spur, within a mile of my house in either direction are no less than 7 road crossings, none of which have gates that drop – only lights and bells. That means that the engineer has to keep blowing the horn as he drives through town, so none of the townies get hamburgerized. AND, because the track is so old, he doesn’t go any faster than 15mph. Given that the town is ~2 miles across, that means it takes the train roughly 8 minutes to cross town. That’s 8 minutes of regular horn blowing. Approximately 1/3 to 1/2 of that time, he’s blowing it almost continuously.

So that’s 3-4 minutes of nearly constant train horn.

5 nights a weeks.

At 1:15am.

:-\

So… If I’m not going to be sleeping at 1:15am (and I’m not), I may as well expand my train library.

The up side is that there are plenty of good places to set up that don’t have a lot of ambient noise and are easy to get to – in most cases, I can just pull up my car and unload right where I’m placing the mics.

The three clips in this post use three different sets of microphones in three different arrangements. All were recorded into a Sound Devices 702 at 24/192.

The first is a pair of Josephson C42 cardioid condensers arranged in an ORTF pattern approximately 6′ off the ground, 15′-20′ away from the train, aimed directly perpendicular to the tracks.

http://soundcloud.com/dancostello-1/trains-20110425-115-c42-ortf

Not my favorite recording. The stereo image is weird, and I recorded at way too low of a level, so there’s more noise than there ought to be. There’s no soundcheck with this to get levels, so you just have to wing it.

The second is a mono track, recorded with my Sennheiser MKH-416T at the end of a boom pole (extended about 8′) and ultimately about 8′ from the train.

Not a bad recording. I have to work on my boom skills, though, as there’s some rumble in there towards the end. I need to experiment with the aiming, too – it was good at times and at others, I thought it could be better.

The third is the start of an ongoing experiment:

http://soundcloud.com/dancostello-1/trains-20110501-115-141-spaced

The microphones are a pair of Shure KSM141 multi-pattern microphones set to cardioid (can also do omni) with one mic on each side of the tracks, about 6′ out from the rails, aimed in the direction of approach, cambered slightly inwards. I don’t have a wireless rig to reach the mic on the opposite side of the tracks, but it turns out that I didn’t need one, because it’s pretty easy to run mic cables underneath the rails.

The reason I tried this setup is because since I’ve started recording trains, I’ve been trying to figure out a way to get a stereo recording, with all of its nice ambience (great for distant horn blasts and bells), but without the horizontal motion through the soundfield that you get with something that’s physically moving from left-to-right, and without the imbalance at both the head and the tail of the recording (i.e. without having all the approach in one side and all the decay in the other). Also, I wanted to get the sound of the train coming AT you, not BY you. I’ve thought about hanging mics from overpasses to get the train as it goes under, and I’ve thought about recording from underneath an open-deck trestle, but so far neither of those have been feasible.

Then I realized that I could run cables UNDER the tracks. YAY for me! Possibilities unleashed! As far as this particular recording is concerned – it’s not bad. The sound quality is quite good, but the mic placement could use some work. The stereo image is SO wide that the left & right channels almost feel independent of each other, like I grabbed two different recordings and hard-panned them. I think that reposition the mics father away from the tracks could help with this, as could re-aiming them or switching them to omni. There’s some rumble in there, too, which makes the obvious point that I should have used shockmounts and not the standard Shure clips.

Keep an eye on the blog for future experiments with this setup, as I think there’s some potential there.


Trains pt. 4 – Amtrak

May 15th, 2011

This is where I work:

the bid'ness

At the top left (partially cropped) is the lot where the trucking guys store all their old trailers (along with, I suspect, bodies, drugs, and other assorted paraphernalia), to the north is the Glue Factory Pond with it’s mysterious white sheen (possibly a light reflection, though I choose to believe it’s some byproduct of the mutant geese that spawn there every spring), and to the right of the picture, across the street from the office is a brown stripe.

That brown stripe is the busiest passenger rail line in the country. Called the “Northeast Corridor,” it runs between Boston and Washington, DC and carries the high-speed Acela train as well as regular Amtrak and commuter rail service. When I picked up my Rycote kit last summer, my first excursion was across the street and through the woods.

These were recorded in mono with a Sennheiser MKH-416T into an Edirol R-4 Pro at 24/48. These recordings were made over a couple days and spliced together so it’s easier to listen to on the internet. Although there’s a spot at approx 1:00 in both the first 2 clips where the regular Amtrak and Acela pass by in opposite directions within seconds of each other. That was pretty cool to see.

Acela High-speed Express:

Northeast Regional:

MBTA Commuter Train:

My impressions of these recordings: meh. The source material definitely has potential, but this isn’t something I’d use to prove to the world what an awesome recordist I am. Relative to earlier recordings, I thought the sound was a bit muffled, which may have been due to the heavy windshielding I was using. The recordings also suffered from a number of technical issues: there was an embarrassing amount of handling noise, particularly as the train approaches. I edited it out of the clips I uploaded, but most of the approaches are hosed. Also, there was a weird thing going on (that would have blown the approaches even absent of any handling noise) that I think shows the recorder just dropping a certain amount of time from the recording (it’s not empty space-the two regions are spliced together. Think of it as cutting out a region while in shuffle mode). I suspect this had something to do with the pre-record buffer on the Edirol. This buffer, when enabled, was designed to store the preceding x number of seconds of audio, even when not recording – the idea being that it was save your butt if you blew a punch-in and missed the front of whatever you were trying to record. I had that buffer set to the max all the time (~23 sec IIRC), because it’s actually fairly difficult to hear trains approaching. They make much less noise than you’d think a giant, speeding hunk of metal would make. Aside from that characteristic metal whipping noise the tracks make when the train is approaching, you won’t hear it until it’s right on top of you, and at that point, it’s probably too late to hit record. It’s FAR too late if you wanted to catch any distant horn blasts. Anyways, I suspect the recorder wasn’t properly appending the buffer to the head of the recorded audio. I haven’t really listened to these recordings before and only just caught this.

The location itself is only ok. There’s a fair amount of traffic on Morse St and surrounding areas; there’s a small power substation across the tracks from where I was standing; there’s a chocolate factory (which smells more amazing than you can possibly imagine) about a quarter mile down the track; there’s a noisy stream directly behind where I was standing; and the whole area is filled with big, leafy trees that make a ton of noise when blown around by the wind coming off a 150mph train. The convenience factor, though, on a scale of 1-10 is about an 11. It would probably be better to go back in the winter when things are quieter, and perhaps closer to 8-9pm (or early in the morning) rather than at 6-7pm when I did it.


Trains pt. 3 – CSX

May 15th, 2011

The commuter rail is all fine & dandy if you want something slow and calm, but if you’re looking for a high-speed pass-by more than a couple seconds long, it will not deliver. So I set out to find a good place to record longer freight trains. Unfortunately, there are a couple problems with trying to record freight trains in the Boston area, and most of them stem from the amount of passenger train traffic in the area. Around here, CSX, Amtrak, and the MBTA all share the same rails and since happy commuters make for happy elected officials, the freight traffic gets shuffled around to accommodate the passengers, not the other way around. This means that the scheduling of freight traffic is inconsistent, and the closer you get to the city, rare. The main freight trunk into Boston roughly follows I-90 and on this line, CSX has a freight yard in Framingham that they use to break up the trains coming from points west to convert them into either smaller trains or (mostly) to load the freight onto trucks. In other words, if you want the chance of seeing more than one train a day, you have to drive out west of Framingham.

There’s actually a much larger, busier rail yard in Worcester and the line between Albany & Worcester is almost exclusively freight traffic, so if you really want to record freight trains in MA, western MA is where to do it. But there are few stations out there and as such, it takes considerably more scouting to find a place that you can set up legally & safely, while still being far enough away from civilization that other people don’t muck up your recordings. I found that the MBTA station at Grafton (just east of Worcester) was as good a place to try as any since it’s rural & secluded, but not so far away that I couldn’t drive there after work.


I really like these recordings; I think they came out well. The stereo imaging is nice and consistent – there’s a good spread without much of a hole in the middle: you can hear individual cars panning from one side to the other. Again, I took lousy notes, but I think I used a pair of Microtech Gefell M-295′s in an X-Y arrangement.


Trains pt. 2 – Commuter Rail

May 15th, 2011

A while later, I went back to the same station, but with a Mid-Side rig instead of ORTF. Having cut my teeth working in music, I’ve had “mono compatibility” drilled into my head from the very beginning and still worry about it when doing field recordings, even though it’s not much of a concern anymore in audio-for-video contexts. Actually, that’s not quite true: there are plenty of mono assets used in games and it’s conceivable that something initially recorded in stereo would need to be mono-ized. Maybe I will keep worrying about it. (For the uninitiated: Mid-Side is mono-compatible, because when it’s summed to mono, the side channels disappear and all you’re left with is the material from one microphone, so there aren’t multiple sources to interfere with each other).



I don’t have the notes from this session, but I’m almost certain that the microphones were a Microtech Gefell M-295 (mid) and a UMT70S (side). The microphones were placed about 6′ from the tracks at a 45-60 degree angle (away from perpendicular), pointing towards the direction of approach – the idea behind this being that I wanted any bells and horns to be somewhat centered in the sound field, rather than skewed way off to one side as they would have been had the mics been aimed perpendicular to the tracks. I found that the drawback to this (as you can hear in the first clip) is that parts of the train wind up behind the plane of the microphone array, which really screws up the stereo imaging – essentially, I would up sacrificing the stereo imaging at extreme angles for the sake of mono compatibility. In hindsight, I don’t think M-S is a good idea this close to a moving subject.

Other things you may notice about these recordings: the background noise on a Saturday afternoon in September (these recordings) is considerably higher than it is at 9pm on a weeknight in January (pt 1). There’s a bit of editing in the first clip both to make the track shorter (the train was parked for a while) and to remove some weird modulating distortion in the middle of the horn blast. I was completely not ready for the amount of SPL coming off the horn (the engine was about 10′ away), and you can hear me drop the gain down a notch after the first blast, in anticipation of a second. There’s a good brake squeal in the 2nd clip: some kids weren’t paying attention and almost missed their stop, so the train stopped a 2nd time to let them off.


Trains pt. 1 – Commuter Rail

May 14th, 2011

To kick off my blog, I’m going to go back to the beginning with some of my earliest field recordings, to talk about what I did and how my approach to the subject has developed.

I’ve always been fascinated by trains and since the security around railroads (relative to, say, airports) is extremely lax, it’s easy to get close enough to passing trains to get very good recordings.

My first few attempts were at recording the MBTA commuter rail, which is pretty easy as far as logistics are concerned: the trains come by frequently (~1/hr in each direction) and at scheduled times, there’s easy access to a parking lot, and there’s a large platform on which to set up. If you pick the right station and the right time of day, there are almost no people or vehicle traffic to make noise. Because the trains stop at each station, you can get some interesting braking, idling, and accelerating sounds. Here are two passes from attempt #1:


These were recorded with a pair of Microtech Gefell M-300 cardioid condenser microphones in an ORTF configuration, into an Edirol R-4 Pro, recording at 24-bit/48kHz. The mics were within 4-6′ of the tracks. My overall impression is that the sound quality is good and the stereo imaging quite nice, though potentially too wide for use in some contexts (e.g. integration into a game). Also obvious is the inadequate wind protection.

Here’s a shot of the station from another time I tried recording there: