Ring Modulator kind of sound/semi crash

[tribase]

I'm on PT HD 10.3.10, HDX, a 16x16 Avid HD IO and a 192 16in 8out, OSX 10.9.5 (on a Hackentosh).

Everyday about 5-10 times I'm working in a session and all of a sudden, the WHOLE session starts sounding like a feed backing ring modulator of sorts. When this first happened, the only solution I could find was restarting ProTools (not the whole computer). It would go away and then hit me a little later again, often after being AWAY from the computer, i.e. protools only idling.

A week ago I figured out that if I go to playback engine and just change the buffer size from my regular 512 to 256 AND THEN BACK, it would go away, meaning I didn't have restart protools. So I have the workaround, but not the fix.

Even though I use internal clocking over loop sync between the two interfaces, I believe this has something to do with clocking freaking out (I used to get a lot of 9172 error on the same rig but different computer), because I believe the buffer change forces protools to resync all interfaces. This is just a guess.

Anybody see that? And maybe a solution?

[tribase]

Nobody has had this problem?

I feel special.

Help?

[albee1952]

Maybe more details will help. Shooting from the hip:
What drive are you recording to(and how full is it)?
How much RAM and CPU does the 'puter have?
When you leave the system idle, is that with a session open, or just PT?
Have you trashed prefs and database files?
Have you run Digitest?
Any programs running in the background?
All plugins up to date?

[tribase]

512GB SSD drive 200GB available. But does the same if I use a 1TB data drive.
32gb of ram, over clocked 4.7GHz CPU

When I idle, I mean pt is open, I just step away.

digitest is fine.

Have trashed prefs and databases multiple times.

programs running in the background sometimes (Safari, iTunes), does the same thing either way. I FEEL like it happens more often with Safari on, but I can't be sure.

native processing is at 15 to 25% never higher.
11 processors, 99% (tried 6 and 7 as well)512 buffer.

New system (2 months) so all plugins have very current installers.

Thanks!

[albee1952]

Just my 2 cents, but I would revert to stock speeds(no overclock) and double-check temps. Once the system is stable and consistent, THEN overclock. Also, how big is the power supply, especially the 12V rail(s)?

[tribase]

This system was built for me, not sure about the power supply. Though I remember the guy saying that it was a power supply bigger than necessary.

[tribase]

Have now dropped the overclocking. Still doing it. Any more ideas, please?

[bigmikebass]

Hey guys... any progress on this? I'm having the same experience exactly, except I use an Apollo quad, so I have to quit pro tools to reset the buffer.

Apollo Quad Firewire, i7 6 core/12 thread, Win7, PT10

[Darryl Ramm]

Originally Posted by bigmikebass

Hey guys... any progress on this? I'm having the same experience exactly, except I use an Apollo quad, so I have to quit pro tools to reset the buffer.

Apollo Quad Firewire, i7 6 core/12 thread, Win7, PT10

You are posting on a 3 year old thread for a different OS, different computer, different interface, Pro Tools 10 is common. You don’t provide any of the expected systems info or describe what troubleshooting you have done. Or be clear what exactly hits you... if it’s a crash what exact DAE error or other type of crash do you get.

Weird behavior like this I would examine plugins... so be sure to do standard plugin troubleshooting.

Start at “Help us Help You” up the top of each DUC web page.

[tribase]

Still doing it. Fully new system latest protools build. So basically that means only HDX card and interfaces the same. I gave up on chasing it. Resetting buffer every now and then.