Tempo and pitch shift upon retrieval

I've run into a glitch that's driving me quite mad. I'm running 6.1 TDM on a G4 with 888 I/O's. My recordings sound good, my mixes sound good, until I save them. When I pull things back up, sometimes, not always, they sound like Alvin and the chipmunks. I've tried manually adjusting the tempo to compensate and while I can revert the tempo, it does not correct the pitch. This is seriously throwing a kink in my program. I need some thoughts on: A. Why this is occuring and how to stop it. and B. How to effectively fix the files that have been affected. Thanks.

Altghough I don't understand in detail your problem, I can only guess that something is wrong with the clock source. A classic is when using an external word clock. If you start a new session at 48kHz BUT forgot to set the wordclock which is still running at 44.1kHz, you get 44.1k files with a 48kHz header. NOW if you BTD and ask Pro Tools to convert this file to 44.1 kHz, and the load the result in your favorite cd burning software you get a wrong playback speed. Hope this helps !

Thanks Mark, I also thought it could be a clock related issue. My clock source is internal and I use no external hardware at all. All my work is in the box. Could the same sort of clock conflict be working against me here? What really has me baffled is that this error is not exclusive to BTD but also occours in session playback, sometimes on files that I've opened half a dozen other times with no problem. I typically record @ 48, Could it be defaulting to 44.1 somehow? I'll be running some emperical tests using different settings to see if it resolves. If that is the case, is the a proscess to convert the affected files to the proper bit depth?

If it's not a misclocking issue as described then trash all your prefs, etc (see the troubleshooting sticky thread).. and verify all your BNC cables are good (and not too long or miswired/incorrectly connected). Rail

Ive had clocking issues (and others) related to my 888 not syncing but I solved it by putting it last in the line after ADAT24 annd 882. This might not be possible with yours but its a thought. I also had problems with PT6 12db sessions... I ONLY use 6db sessions now.