The Folly Of Jumping To Conclusions

brandonshireConceptsLeave a Comment

Today’s myth to bust:
“There’s no reason you should need that in your chain, I can’t see it yielding usable results.”
Since when can we judge the sound of a chain on a specific source without hearing the actual audio?
Since when does a picture of a chain give you enough information to know exactly how it would sound without hearing the actual audio?
Since when can we say with certainty that our audio must sound like garbage in the first place if we need x-y-z without hearing the actual audio?
You can’t.
We’re audio engineers, damnit! Why are so many engineers so hard lined about how to engineer their audio? Everyone has to be right, but they make assumptions with incomplete information.
If you don’t hear the audio, you cannot judge a picture of a recording chain. If someone wants to post a picture of a chain to talk about how they enjoy using it, but they don’t post the audio, you can legitimately ask questions about why they might’ve chosen a certain chain. But you cannot make statements about the quality of the persons audio without hearing the actual audio.
Imagine if structural engineers acted like audio engineers. “You shouldn’t need that. There must be a problem.” Well, you maybe didn’t see how it was used. You maybe didn’t know what problems were being addressed by it. And as a structural engineer, you should know better than to judge with incomplete information because an error in that field can cost lives if a building collapses.
But since the stakes aren’t nearly as high in audio, and it’s largely a creative field, we get people who like to tout their ability to know instinctively that a piece of audio is full of problems and sounds like crap based on a picture of a signal chain.
There’s no way a person can judge the quality of the audio based on a picture of a chain.
Remember. Jumping to conclusions is a horrible idea.

Share this Post