Clicks and pops with saffire pro 10

OK, I think I solved it. I did not have the sample rate in the saffire control panel matched with the sample rate in the sonar project.

I just got my focusrite pro 40 yesterday and it runs great at 128. do you get a click when you change sample rates EN?

yeah its the asio buffer....I have not played with the sonar settings yet...sorry should have been more clear.

ORIGINAL: EN

Thanks for the info :)

For my Saffire the latency settings for ASIO Buffer Size range from 2.0ms to 40.0ms, I currently have it set at 2.0ms. Then there is firewire buffer size, which ranges from .1ms to 20ms, I vave it at .5ms.

So for the playback buffer in Sonar, does higher = better? Where is the cutoff? Changing it hasn't seemed to make much difference for me so far, however I have not made any big projects yet.

Here's what I've discovered -- it may not apply to everyone. By using an i/o playback buffer of 512 (again, this is my sweet spot), I was able to more accurately determine my audio device's latency sweet spot. Unfortunately, I cannot get below 5ms without glitches/pops/clicks, but I also found out that it doesn't matter that much as there is a balance met.

So while many try to get the absolute lowest audio latency they can get, it doesn't always work out - and more importantly I think, is what can work.

So I have found I can live with the 5 to 8ms latency ... my human abilities allow me to adjust, so to speak; and then I get the benefit of other things working well together without the pops/clicks/glitches. It's a give and take thing.

ORIGINAL: CJaysMusic

Raise your latency and experiment with different settings and driver modes. Try wdm and asio with different settingsd. Yuoll find your pc's "G" Spot...
Cj

I think you meant to reply to the other guy ;)

For my Saffire the latency settings for ASIO Buffer Size range from 2.0ms to 40.0ms, I currently have it set at 2.0ms. Then there is firewire buffer size, which ranges from .1ms to 20ms, I have it at .5ms.

I have the Saffire 26 (uses the same driver) with the FireWire Buffer Size set to 1.0ms. With that setting, I can use different ASIO Buffer sizes depending on the system load, etc. without clicks/pops. I currently have it set at 20ms for full mixes.

Also, I'm using an older beta driver: SaffireControl PRO Version 1.1.7789, Firmware version 1.1.7530, with an AMD 4000+ (single core) system. The version 2x drivers increased the internal hardware buffer a tiny bit, and they weren't as stable for me.

Keep trying different ASIO and FireWire buffer sizes in the ASIO Control Panel, and find your sweet spot. You have a faster system than I, which means you should be able to do more at the lower settings. FYI, I had some fun playing thru amp sims, and hearing the plug-in effects, etc, at your settings, but had to increase the latency once I had just a few tracks recorded, so I don't often bother with "Input Monitoring" with plug-ins anymore. Just add some external hardware reverb in the cans if needed during tracking. It would be different if keyboard was my main instrument and playing soft-synths real-time was a must-have. I'll try again when I build a new system, or get a different interface. Please note that the way I use it, it's a very stable, and great sounding interface.

Peace.
Rigel

I actually had this nightmare a while ago, same situation; audio clicks no matter what the latency, **** acting up when I did GFX stuff.

Oddly enough disabling my wireless card solved the problem. You might try that...

OK, I enabled all the 'visual fluff' in Vista under advanced settings and it made the clicks and pops worse, so I know it is something to do with the graphics.

What I don't get is how my graphics card, which handles big 'ol 3D games perfectly, is screwing me up on a very graphics-non-intensive program... Isn't the GPU meant to take the load off of the CPU and RAM??