Hoping for a second stroke of luck, I changed the Clock Source back to internal and the power light remained solid.
Emboldened, I launched into Pro Tools without incident and continued along without incident.
What was the real cause of the problem? I may never know…
Is there a lesson in all this? Absolutely! Knowing where to go when any program, especially Pro Tools, gives you errors is crucial.
My first stop is always the DUC because it provides real-world solutions and advice from Pro Tools users, followed by the Digidesign Support page, which allows you to search by error number and error phraseology.
If I still haven’t found an answer, that’s when I hit Google. Hopefully, if your issue isn’t documented in the DUC or the Digidesign KB, then someone has documented their experience in a blog post.
Who knows - maybe that’s the precise reason you’re here? Either way, I hope you’ve found this information useful, and happy error quashing!
Have a thought on DAE or other errors? Have a tried and true method of troubleshooting these masters of darkness other than Knowledge Base spelunking?
The Technologist, a.k.a. Kyle P. Snyder, is an audio engineer with innumerable credits in the public and private sector, writing about audio engineering, recording technology, and a multitude of other tropics for ProSoundWeb. Find out more about Kyle at his website.
.
More posts by The Technologist:
Firewire Device Hierarchy: Does It Really Matter?
“Go To” Sources For Important & Necessary Microphone Data
Don’t Come Unglued; Bake A Tape!
Spotlight Versus Pro Tools - The Devil Is In The Details
An in-depth yet easy-to-understand discussion of wireless systems, how they operate, issues that can plague performance, and solutions that do the trick in the vast majority of situations.
Petition google to change their ways!