VO Workflow: Things Go Wrong – Tuesday Tech Tip
I’ve been thinking a bit about failure modes recently. Because the worst thing to assume is that nothing will ever go wrong. Even the simplest of systems contain a multitude of variables. And it only takes a mere minimum of things going the wrong way to cast us adrift.
That moment when things fail can be unsettling. Perhaps our computer does nothing when we press the “on” button, or we might try to open our recording application and have it just sit there. Maybe we recorded with the wrong mic, incorrect settings, or – and I will proudly raise my hand here – we “recorded” a brilliant take without actually hitting Record.
Depending upon the circumstances, stuff like that can generate a bunch of extra work. How we react can determine what happens next. Will the issue be a simple hiccup during the production process or stop the session dead in its tracks?
We often have much more control in those situations than we realize. What can we do to land on our feet? Here are some of the steps I lean on when glitches occur:
Recognize the shock
We first have to both recognize and acknowledge the problem. Shock leads to panic. Panic often leads to freezing up. When something happens, I find just taking a moment to say, “Ok…that happened” can prevent the panic from setting in. It also allows a clearer focus upon what actually happened. That lets us move on the finding a solution.
Can we backtrack?
Sometimes my hands get a couple steps ahead of my brain and I’ll accidentally nick the Delete button when the entire audio file is selected. Nothing like seeing a 2 hour chunk of audio vanish from the screen to snap you back to the here and now. In the computer, “Undo” can be your best friend. That idea works in the real world as well. Is there a way to step back to the moment before everything failed?
Am I understanding the problem?
Sometimes what stops working is not what has actually failed. I’ve had clients spend days trying to track down noises in their studios only to realize their headphones had been damaged and actually buzzing. Take the time to clearly define what the problem is, and be open to the possibility that things may be masked or aggravated by a separate issue.
What steps can I take?
A simple recording setup reduces the number of variables. Having a plan, a preflight checklist, a fallback option, or a logical way of troubleshooting can nudge you out of deer-in-the-headlights mode. For example, knowing a client can always listen to you over the phone can save you if the internet goes down during a Source-Connect session.
The more you depend on your studio for work, the more important it is to honestly ask what your fallback positions might be. Identify each item in your recording chain and ask yourself – “what if that didn’t work?” to help identify weak points. A simple backup item like an extra cable or connector could help solve things while the clock is running. Those dress rehearsals for your studio should let you create a list of things to check, which in turn will give you more confidence as you prep for projects.
Because, stuff fails…
Computers crash. Cables kink. Electronics age out. Sometimes you will just have to reschedule. Pros know: things go wrong.
The key difference is that the true VO professional will focus on what needs to be addressed to get things right and provide a solution.
A client can deal with – “this bad thing happened, and here’s what I’ve done to fix it…
This information recently went out directly to my email community.
If you would like to join in to receive those emails the day they publish, please take a moment to share your contact information through this sign up form.
Thank you.
Hi, Jim –
First, THANK YOU (I think I’ve said this before to you in a post) for your no-nonsense, easy-to-understand explanations of microphones, their operating principles, their pickup patterns, and other information. As I think I’ve written to you before, I’m on old guy who’s been a mic nerd for a long time, yearning for (for 40 years) and finally being able to “justify” buying a U87 11 years ago.
As I read your Tuesday Tech Tip I noticed that you used the term “preflight checklist.” Are you a pilot? Just wondered. We might have something other than audio in common.
You are quite welcome, Rob – glad that has been helpful for you.
I’m not a pilot (though I have played them in video games…) but the idea of a “preflight checklist” is one I return to in almost every class. It has to do with how easy it is to miss something simple in the moment. Having a clear, honed list of things to confirm has given me the ability to focus better upon sessions (or classes) as I know that everything has been checked.
Also, I have found that as I put those preflight lists together, I have a better understanding of how things fail – so it makes any in-session troubleshooting more focused and efficient.