Pro Fire 2626 Clock issue maybe??

[necjamc]

I was recording a internet radio broadcast tonight that some of my friends were on. I successfully captured the first 198 min and then suddenly the sound became robotic. Now I was not at home while recording any of this, and when I returned home, not only did my recording become robotic but all sounds in windows and PT sounded this way afterward till a reboot. Does any one have some insight as to what causes this. Drivers, Clock issues, Windows 8. I'm not grasping for straws here, more if someone might have some insight and maybe a starting point to figure out why.

Here is a clip of the issue. At around 14 seconds in.

Thanks for any insight
Neil

[necjamc]

No ideas huh. Unfortunately I don't know where to start troubleshooting, out side of maybe recording another 200 min broadcast, It works flawlessly under normal circumstances. But I hate an unsolved issue that will only come up when I'm probably not watching. Like this or if I'm recording a show where I am playing.

[cwsand]

It does sound like a clocking/sample rate problem. How are your interfaces set up to record and how are they all clocked?

[necjamc]

Originally Posted by cwsand

It does sound like a clocking/sample rate problem. How are your interfaces set up to record and how are they all clocked?

This was direct via FireWire clocked internally. I had all other interfaces turned off. I was recording via a SPdif loop back cable, but clocked internally. I'm floor by this. I spent a couple hours tonight mixing a 42 track session without a hiccup. Also played around with my keyboard with Superior drummer, kontact 5, and hybrid open.

I thought heat, but a reboot solved the issue, and I continued the recording.

Thanks, I'm trying to think what might have tried to steal the clock causing it to screw up.

Edit, I was playing this back with Internet explorer. I had screensaver off, no wifi, and no other programs open.
Do you think that a failing firewire card (it's a TI chip, older card I've used since 7.4 when I first got Pro Tools), or cable. Or maybe windows losing control of the FW chip driver????