V Studio 700 / X1 gremlins

I am having a few issues with my setup and I am not sure where the problem is occurring.  

I have:
V studio 700 with latest firmware and other updates
X1 with latest updates.  


Windows 7 ultimate
Intel Duo Core E4700 @ 2.60 GHz
4 Gig of ram
64 bit OS
setup for performance.  (this machine only does music)

3 internal SATA HD's 7200 rpms

The problems are mainly pops and glitches.  They do not record when I record audio but they are annoying.  They mostly go away when I change the ASIO driver settings to Max Stability but then the latency make it very hard to play live.  If I add more ram will this take away the latency issues?  I realize a duo core processor is not really ideal for this setup but it's what I have right now. 

Any advice would be greatly appreciated.  

Thanks,

V 

Thanks for the reply.  

Yes I have noticed the same thing.  A reboot usually fixes it and will check to see if I am sharing the ASIO drivers.  

V

Upgrading to a Quad core processor would certainly help. There are several things which can cause this. Is your internal sound enabled? Are you running Sonar as an administrator? Do you have the V700R selected as your default device? Do you have your Lan or wireless broadband enabled? There are several other background services which can interrupt the audio streaming -> ASIO. Are you running the 32 bit version of Sonar or the 64 bit version? Just a short list.
Rather than go through a reboot scenario, turn on the V700R, then the V700C, before you boot the computer. Boot the computer to the desktop and then turn on any Midi controllers.

Hi Craig,  

Thank you for getting back to me.  The internal sounds are disabled.  At least in the sound control panel I have it set to "no sound," and the VS 700 is the only device for sound on this machine.  To run Sonar as an admin does that mean that every time I start Sonar I need to right click it and run as admin?  Yes the V700R is the only device.  I did have the Lan enabled because I often bounce mp3s from my music computer to my general desktop so I can email them out.  
I am running the 64 bit version of Sonar.  I'll try your suggested boot sequence and get back to you.  


The Latency checker tells me "this machine should be able to handle real-time streaming audio and or video data without dropouts.  The current latency is 1072 with the max at 1219.   

V

Boot should simply be turn on the V-Studio stuff and THEN turn on the DAW. If USB devices are seen AFTER Windows has booted, you 'may' see weirdness and the way to eliminate this (assuming there are no related system issues) is to have them powered up before the DAW. Check that you have a connect light on your 700R and 700C... if the controller isn't recognized (in Sonar?), it may have lost the config/device which you can check in the usual way via Sonar. Check that the controller is actually still selected. One other thing to do if you still have pops etc... delete the aud.ini file from inside Sonar.. this cleaned a few repeat issues I had before X1C. Cheers.

Thanks Mully,  Yeah it's strange but unless I follow the boot/power on sequence in the V studio manual, the 700c will not make the connection.  The V700R works as it should but the console will not connect and can't be found in the midi devices preferences.  

So just to be clear, this is my start up sequence.
1. boot computer
2. power on V700C
3. power on V700R and wait for USB connection (usually a few secs)
4. Start up Sonar.

One other thing I noticed is the popping and clicking happen more often when I am using soft synths.  

Thanks again for info and insight.  I really appreciate it.  

V

Hey V.... I would def recommend turning your 700 gear on first... THEN the DAW. Think of it like this.. the 700C is powered on making it's USB port alive, the 700R then powers up and sees the 700C during it's own power up cycle (best time for connection IMO). You then power up the DAW and then IT sees the powered up connection ready and waiting for the it. All goes well. When the DAW is already powered up and resources assigned during this boot up, to then connect another USB device (in this case the 700 connection) can introduce a level of error as the DAW 'reshuffles' to accommodate. Obviously this should NOT be the case and this is only my poor interpretation of what's actually happening but in this way, I get zero glitches when then running Sonar. I'm sure there are incompatibilities between the MOBO s/w and W7 64 bit that will be revealed at some stage as this is possibly the best reasoning why this is known to happen IMO... however, this sequence prevents the issue for me at least. Startrat1 and I definitely agree! Cheers V.