Clicks and pops in background - nothing on

Are you using optical connections by chance?
 

Can you please list your reported latency values in Sonar Preferences?
 
Also, are any effects or plugins (even Pro Channel) loaded into the project experiencing these issues?  If so, please list them.
 
Can you also list your current Driver Mode in Sonar, as well as your audio interface's ASIO Buffer Size (might be shown as a slider for performance or something like that, if not actually shown as a buffer size directly), as well as the Sample Rate for the interface and for the project?
 
Do you happen to have a Wi-Fi adapter on this computer?  (even if you do not have a browser open).
 
If you hit 'E' on your computer keyboard, just before recording, (which will disable any loaded effects), does the recording of your mic then come out clean?  (hit 'E' again to turn effects back on after testing this).
 
Bob Bone
 

Thanks for the quick responses  - I will address as many as I can
Albert
 
1.  No trial VSTs on my computer
 
Bob -
1. - The computer has no wireless and is not connected unless I plug in the cable.
With regard to plug ins - first of all, this is happening on my computer even before Sonar is loaded.  My software mixer shows input activity intermittently on all 8 inputs.  STILL - with plugins taken out and prochannel turned off - clicks persist
 
Settings: I have tried various settings.  but here is the breakdown -
DRIVER - For some reason ASIO does not work with RME-Audio Multiface and Sonar - RME suggests using the WDM/KS driver.  I have tried Asio4all and there is no sound
 
LATENCY - 92.9 ms - 4096 SAMPLES.  ( I have experimented with this, no change)
  
BUFFER SIZE IN RME SOFTWARE - now at 1024, but I have tried all kinds of settings here as well.  Remember - these are not your typical pops and clicks from mismatched driver settings.
 
Dr. Avalance - I never tried latencymon
   I have tried disabling virus protection, etc.  Actually, I went into processes and services and turned off everything that I did not absolutely need.
   Several days ago I updated the flash and the drivers for the Multiface. For two take of a song, I was able to record without clicks and pops.  By the third take they were back and the fourth take they were back to popcorn!  I tried to recreate that session by uninstalling and reinstalling all the drivers, etc.  Still, no good.
Also - I defrag and optimize the C drive every week.  I do nto defrag the SSDs as I was told that was not only not necessary, but can do damage to the drive.
 
ONE THING I HAVE NOT TRIED - but I will - is moving the project to a different drive.  I will post what I find out. Also, tomorrow I try a different audio interface.
 
THANKS EVERYONE!
 
 

That latency will KILL your chances of tracking/recording without issues.  It is WAY too high.
 
To give you an example, my system is set to record with a total round trip latency of 9.7 milliseconds, and I could lower that if I needed to, but running at 9.7 milliseconds works GREAT for my needs.  TO achieve this latency, I set my audio interface's ASIO Buffer Size to 128 for recording, and either 1024 or 2048 when mixing/mastering.
 
If this link is showing YOUR audio interface, it looks like a really nice one:
 
http://www.rme-audio.de/en/products/multiface_2.php
 
And, IF that is the same interface, it quite clearly indicates it has ASIO driver mode available for it.
 
If you are unable to change the driver mode in Sonar to ASIO, first try DE-selecting the interface altogether in the Sonar Preferences - under Audio>Devices, both for input and output, then click Apply.  Sometimes ASIO does not show up as a viable driver mode if WDM is already selected, so if that is the case, first de-selecting it, then changing the Driver Mode in Sonar Preferences, under Audio>Playback and Recording, from WDM to ASIO, then click Apply.  THEN, go back and see if Sonar automatically selects your audio interface for you, but this time running under ASIO driver mode.
 
But FIRST, BEFORE trying the above, I would recommend that you COMPLETELY uninstall ASIO4ALL - it can and DOES frequently interfere with other ASIO drivers that are present, and is for most folks at best a band-aid.  So, because we want you to try getting your audio interface to use its own ASIO drivers, you should completely uninstall ASIO4ALL.
 
I am also hoping that you  have the latest and greatest drivers installed for your audio interface, so if that is not the case, you should look into making sure those get updated too.
 
Soooooooo, please review and test things out per the above steps, first removing ASIO4ALL, then updating your audio interface's drivers, if needed, and then trying the other de-selection/selection steps I described above.
 
If you DO get your interface set to use ASIO for your audio interface, also try setting the ASIO Buffer Size to 128, which should be a reasonable setting when recording, and then try recording something, without adding any effects - just raw mic input - to see how that works.
 
AND, also at that point, please list the Sonar-reported latency values when you are running with the ASIO Buffer Size set to 128.
 
Thanks,
 
Bob Bone
 

Another suggestion, run Sonar with full admin right, especially if you just upgraded.
 
It happens to me after a Sonar upgrade some version back. A few of my fully authorized VST still need admin right to ..settle down at least the first run after upgrading.

Thanks again all.
 
First - Bob - I can't find an ASIO driver on the RME website for my interface.     Did you see one somewhere?
 
 
I will try all suggestions - but, for clarification:
 
1.  There is no Asio4all on my system.
2. I tried the an Asio driver, but it was not working with Sonar.  when I contacted RME, they said just to use the WDM/KS driver.   I will go and try to get the ASIO to work. the WDM/KS will not allow for a latency lower than 96 ms
3. I updated all drivers before the original post.
4. My computer has been set up for audio according to the directions ion the web - all Windows system sounds were turned off long ago. Also the "share drivers" - I have tried this both ways to no avail.
 
 
I think the electrical glitch is what is happening.  To clarify something:
 
 The source of the clicks and pops are not there because of the microphone, they are there before a microphone is plugged in - they only come out in tracks through the Multiface II interface.  I will try to put an instrument through the interface as well and see if the same things happens.  As stated above - when I first turn the computer on, before I open Sonar, or anything, I open the software mixer that is always running in he background and is associated with the audio interface.  When the mixer comes up - in channels 1-8 analog, you can see the impulses jump up and down at random.  
 
I meant to go borrow another audio interface today, but did not get there, I will do so tomorrow. I will also try all of the other suggestions, starting with the ASIO driver. 
 
STILL - for clarification:
 
The clicks and pops a

This sure sounds like 100% hardware to me. Time for a new interface I guess. I would contact RME and see what they say first. 
The fact that it's glitching in a stand alone state say's it all. 

Double post.
 
 

THANKS again guys
 
1.  Yes - the MultifaceII in the picture is the same as mine. 
2.  It is powered by firewire.  I will try an external source.
3. I have contacted RME.
4. I will try a new interface later today.  I have a Steinberg UR22 - USB interface from school that I can try.  It is brand new.
5.  I downloaded the latest drivers from RME.  For this until, they offer the WDM drivers, which state that they include ASIO drivers; however, when I set it to ASIO, all the analog channels are not usable.
6. I so know how to switch to the build-in motherboard sound, so, if the UR22 does not work, I will try the onboard sound.  I do, however, seem to remember that the onboard sound was not compatible with the DAW.  I do not quite remember why.
Mr. Rabeach - sounds like you have a handle on the electrical part, but I took my last electrical engineering class in 1975.  Can you translate to either English or New Jersey for me?
 
Thanks to all of you for your help.  Although I do not do a lot of recording with my microphones, I have several projects that will require their use, so I want to resolve this.
 
Thanks again - I will update later.

Thank Jon - will do later today!

DumbGuy56
THANKS again guys
 
1.  Yes - the MultifaceII in the picture is the same as mine. 
2.  It is powered by firewire.  I will try an external source.
3. I have contacted RME.
4. I will try a new interface later today.  I have a Steinberg UR22 - USB interface from school that I can try.  It is brand new.
5.  I downloaded the latest drivers from RME.  For this until, they offer the WDM drivers, which state that they include ASIO drivers; however, when I set it to ASIO, all the analog channels are not usable.
6. I so know how to switch to the build-in motherboard sound, so, if the UR22 does not work, I will try the onboard sound.  I do, however, seem to remember that the onboard sound was not compatible with the DAW.  I do not quite remember why.
Mr. Rabeach - sounds like you have a handle on the electrical part, but I took my last electrical engineering class in 1975.  Can you translate to either English or New Jersey for me?
 
Thanks to all of you for your help.  Although I do not do a lot of recording with my microphones, I have several projects that will require their use, so I want to resolve this.
 
Thanks again - I will update later.

Your PC power supply may be failing or you have a power problem associated with firewire on the PC side or in the device itself. Just a guess though. 

OK - forget that one - the clicks are back.
 
The system had been off for about 18 hours, so when I turned it on - it took a while for the clicks to starrt up.  OK - on to the new interface
 

One Idea - Put your moblie phone in another room.
 
 
It is amazing how much trouble they can cause when recording.

If you get the same issue with a second AI, I would pull the power supply and check it,
assuming you have a meter, or take it to a shop for a bench check. It could easily be
giving you the noise you're seeing. For a replacement, your specs indicate you could
operate perfectly well with less than half of that 1200w beast, unless you have a really
insane video card.

At this point I would clean up around your system, Disconnect everything. 
If you have a hardwired mouse and keyboard use them. 
Get all sources of RF interfearance out of the room. 
Don't even plug in the speakers,, nothing. 
 
Now fire it up and open the software mixer and see if those spikes return. 
If they are there , change the audio interface. 
 
If they are not there then you start adding equipment until there return. 
 
This thread is long but did anyone get you to run Latency Monitor? 
http://www.resplendence.com/latencymon
 
 
Back before I had an audio interface I noticed certain PC's or Laptops would show action  ( noise floor) if I opened Wave Lab and put it in record standby.  This is with nothing plugged in. A PC is potentually a noisey place. USB and Firewire is easily contaminated too.