Two drumsticks laid end to end on a snare head, about forty inches, is the entire measuring system behind the Recorderman overhead placement. It works because it produces a number rather than a memory.
That's the whole problem with the rest of a session. Knob positions can be stored. A microphone eighteen inches off a guitar cabinet, angled slightly away from the dust cap, cannot.
None of this is the desk's fault. Even a console that reloads every knob position has no idea where you put the overheads, which preamp fed channel nine, or why the singer's headphone mix had that much reverb in it.
It also asks for the stage plan and routing table to be updated so they match what actually happened, not what was planned that morning. Those two versions drift apart by lunchtime on almost every session.
Stereo pairs get their own line. If you ran mid-side, the document has to say whether the mid capsule was omni or cardioid, which way the figure-eight was facing, and how the decode was done. Get any of those wrong on the way back in, and the image collapses.
Then there's the human layer. Names, emails, and roles for the engineering team, the same again for every musician along with the instruments they played, and a list of the pieces recorded with composers attached. Dull to write. Impossible to reconstruct a year later when somebody needs a credit sorted out.
The take log matters more than people expect. A chronological account of how the day actually ran, with each take described as it was captured, is the thing that tells you why take seven sounds different from take six.
The Recorderman approach fixes that by making placement measurable. One mic sits roughly two drumstick heights above the kit, pointed straight down at the snare, and the second goes over the ride-side shoulder, also aimed at the snare.
Then you check it with a cable. Hold one end against the kick head where the beater strikes, pinch the cable where it reaches the first mic, and swing that pinched point across to the second. If both distances match, the overheads stay in phase with the kick and the snare instead of fighting them.
The trick generalizes. Anything you can write as a distance, an angle, or a fixed reference point will survive a teardown, and anything you can only describe as roughly where it was last time will not.
For amps, note the distance from the grille cloth, the offset from the center of the cone, and the height off the floor. Three numbers. It costs you twenty seconds and saves an afternoon.
The graphics are good enough that one reviewer said they put some plug-in interfaces to shame. The base application is free, and you buy the individual device panels you need.
It has gaps. A small number of manufacturers won't allow their names to be used, so those boxes simply aren't in the library. Export quality has also been flagged as thin, which starts to matter when the sheet has to print or travel as a PDF.
Plenty of engineers build their own instead. Templates float around with a session info block for artist, track title, date, engineer, studio, and notes, plus boxes for the input and output details on every channel. Some are published blank, carrying nothing but the equipment diagrams, so you can drop them into a drawing app and add your own header.
Those exist because the commercial coverage is patchy. The person who published one such set made it after failing to find recall sheets anywhere for a couple of boutique preamps, and that gap has a habit of showing up around exactly the gear you care most about getting back.
That's the whole problem with the rest of a session. Knob positions can be stored. A microphone eighteen inches off a guitar cabinet, angled slightly away from the dust cap, cannot.
None of this is the desk's fault. Even a console that reloads every knob position has no idea where you put the overheads, which preamp fed channel nine, or why the singer's headphone mix had that much reverb in it.
The signal chain is the part worth writing down
One university recording course spells out what a session document should contain, and the list is longer than most working engineers keep. Students have to file the complete signal chain for every recorded file, including microphone and preamp choice, channel numbers, and patchbay connections.It also asks for the stage plan and routing table to be updated so they match what actually happened, not what was planned that morning. Those two versions drift apart by lunchtime on almost every session.
Stereo pairs get their own line. If you ran mid-side, the document has to say whether the mid capsule was omni or cardioid, which way the figure-eight was facing, and how the decode was done. Get any of those wrong on the way back in, and the image collapses.
Then there's the human layer. Names, emails, and roles for the engineering team, the same again for every musician along with the instruments they played, and a list of the pieces recorded with composers attached. Dull to write. Impossible to reconstruct a year later when somebody needs a credit sorted out.
The take log matters more than people expect. A chronological account of how the day actually ran, with each take described as it was captured, is the thing that tells you why take seven sounds different from take six.
A tape measure beats a photograph of the kit
Photos are useful and insufficient. They flatten distance, hide angle, and never show you the one number you needed.The Recorderman approach fixes that by making placement measurable. One mic sits roughly two drumstick heights above the kit, pointed straight down at the snare, and the second goes over the ride-side shoulder, also aimed at the snare.
Then you check it with a cable. Hold one end against the kick head where the beater strikes, pinch the cable where it reaches the first mic, and swing that pinched point across to the second. If both distances match, the overheads stay in phase with the kick and the snare instead of fighting them.
The trick generalizes. Anything you can write as a distance, an angle, or a fixed reference point will survive a teardown, and anything you can only describe as roughly where it was last time will not.
For amps, note the distance from the grille cloth, the offset from the center of the cone, and the height off the floor. Three numbers. It costs you twenty seconds and saves an afternoon.
Software can hold the knobs you can't recall
There are applications built specifically for analog devices without memories, and they all chase the same goal, which is a written record of everything the desk can't hold. One of them draws detailed front panels for real hardware, lets you drag the virtual knobs and faders to the positions you actually used, then files the whole rack as a named session you can pull back up later.The graphics are good enough that one reviewer said they put some plug-in interfaces to shame. The base application is free, and you buy the individual device panels you need.
It has gaps. A small number of manufacturers won't allow their names to be used, so those boxes simply aren't in the library. Export quality has also been flagged as thin, which starts to matter when the sheet has to print or travel as a PDF.
Plenty of engineers build their own instead. Templates float around with a session info block for artist, track title, date, engineer, studio, and notes, plus boxes for the input and output details on every channel. Some are published blank, carrying nothing but the equipment diagrams, so you can drop them into a drawing app and add your own header.
Those exist because the commercial coverage is patchy. The person who published one such set made it after failing to find recall sheets anywhere for a couple of boutique preamps, and that gap has a habit of showing up around exactly the gear you care most about getting back.
