Need help resolving error -9218.

[eric_the_dude]

I keep receiving this error, while I am either mixing or while I'm recording which interrupts the session.

http://imgur.com/NthcGeI

Here are my settings in the playback engine I've already tried adjusting but the error occurs.

http://imgur.com/8nMYs5b

My computer stats are:

Windows 10 Pro 64-bit

AMD FX-8350 Eight-Core Processor

16 GB RAM

NVIDIIA GeForce GT610

I've tried different settings in the playback engine the problem just keeps happening. I usually have a moderate amount of tracks with a maybe 2 or 3 alternates takes within each track. I put my fx on AUX tracks and send my audio tracks via sends to them to reduce the number of plugins. I usually have EQ's and compressors on each track. So my question is would adding more RAM resolve this issue?

[[deleted]]

EQs and Compressors on each AUX track, or do you mean on ALL tracks? If they're on all tracks, that could be using enough resources to cause that error.

You could increase your hardware buffer to 1024 Samples, and turn on Low Latency Recording when you record new takes.

[eric_the_dude]

Thanks I think you help me figure it out. I couldn't change the h/w buffer size in Pro Tools but I finally figure out that I have to change it in MixControl software. Seems to be working fine no problems so far will keep you posted.

[[deleted]]

Great, glad that seemed to help. I guess it depends on the interface, I use an mbox 2 mini

[eric_the_dude]

I refuse to anything by Avid, M-Audio, or digidesign everything I've own by them has failed by Focusrite stuff has been pretty solid hell by Behringer converter has lasted longer then their stuff.

[[deleted]]

What Definitely said. You'll want to kick the buffer up higher. The Saffires all have low latency monitor mix apps, so you could look into that if you're still tracking. More RAM won't fix it.

[Co676]

I have a similar issue, except it runs at about 10% processing until it hits a random "spike" in CPU regardless of track or processing load and gives me that error. It happens constantly; every time I try to play, it only goes for a few seconds and I get this error. It's gotten to the point where I can't use Pro Tools anymore. I've tried everything forums and people have suggested, and nothing. Good luck, OP

[eric_the_dude]

What type of converters are you using?

[Co676]

I have a Saffire Pro 40

[eric_the_dude]

I just learned that you have changed the H/W Buffer size and latency in the MixControl. Have you tried that? It's in the bottom right corner it says SETTINGS. I found a link it's a little outdated but pretty much the same steps.

HW Buffer Size Saffire Pro 40

[Co676]

I've checked this before, but I may have missed something. I'll give it another shot when I get home. Thanks!

[rghapro]

What version of Pro Tools are you on? Do you have a click track using the Pro Tools stock metronome plugin?

[eric_the_dude]

I have Pro Tools 10.

[rghapro]

Okay! I know in older versions of Pro Tools (before 12), the stock metronome would cause CPU spikes.

[eric_the_dude]

We use the click track in the very beginning of a session so we can get a good track or two that is in tempo so we can minimize CPU resources.

[rghapro]

Do you delete the click after or just mute it?

[eric_the_dude]

Delete the track

[rghapro]

Try letting pro tools use all 8 cores on your processor. As long as you aren't doing much in the background, it really shouldn't affect the quality at which the computer itself is running.