Hi all,
 
I'm a little hesitant to bring this to the table - cuz it's a little mysterious.  I recently did an X2 reinstall, to clean up something and import some files.  Problem is now I have latency issues like crazy!   I can't playback or record without getting at least 4 or 5 dropouts and am also having problems getting the drum tracks to line up with the click -- although my drummer is really good and he has great time - when ever we do a track of his - it just won't like up with the click on playback!
 
I'm way frustrated b/c I never ever had latency issues in the past with X1 or X2 - I was able to leave my Antivirus and everything running in the Windows sys tray with no problems.    Now I get dropouts and slow-downs all the time and I've even tried disable the entire sys tray and antivirus (AVG) - but it doesn't help very much.
 
I'm using X2 with a Tascam US600 in a Win7 64bit environment.   Used to be very solid, now it's flaky.   Any tips or advice?
 
thanks much, ryan

Me too Ryan.  Very frustrating.  Someone help us please !!!
 
Dan

Did you do a clean reinstall removing everything from the drive and the registry that is sonar related? If not you may want to consider that if we can't get your issues corrected easily.
 
Some details about your setup would be helpful. Perhaps you can update your signature to include the details of your computer/ram/hard drive/sound card/video etc.
 
Are you using asio or wdm. What are the settings in preferences>driver settings?
Be sure you have the playback and record timing masters set to the same thing.
 
Verify that the default sampling rate for new projects is what you want it to be.
 
If you are using wdm run the profiler.
 
with either wdm or asio  I have found it it best if you only have your main sound card selected under devices. Check to make sure the build in sound card is not selected in devices unless that is your only sound card.
 
there is more that can be checked but these are a good place to start troubleshooting.
 
Good luck

To me, this is a big one.. simply putting the disk in or restarting the installer is not necessarily sufficient. After using "add/remove programs", manually delete all folders and if you don't wish to edit the registry, do a restart then run a registry cleaner
 
THEN reinstall.
 
 

Tom Riggs
Did you do a clean reinstall removing everything from the drive and the registry that is sonar related?

 
Why doesn't the uninstaller just uninstall everything?
 
That always seems like the final insult when I am removing a program that has earned itself an uninstall.

oh yeah, I removed all folders and spent 15 minutes hacking through the Registry.  (I used to be a Windows admin professionally - so I know a fair amount of the ol' tricks)
 
I'm wondering if Buffer size doesn't have something to do with it?  I never had a problem with it before - I just left close to the left side under "Fast".     

mike_mccue
 
Why doesn't the uninstaller just uninstall everything?
 
That always seems like the final insult when I am removing a program that has earned itself an uninstall.

I agree, and have never understood why the uninstall process couldn't be automated to look for the Registry entries and the folders and just take care of it - or at least locate them and present the user with an option to keep or remove them.
 
Bob Bone

I'm using Sonar X2 in a Win7/64 environment.  Tascam US600 interface WDM drivers.     AMD A4 3300 19.GHZ chip.  8GB of RAM.   Running AVG Anti-virus.

mike_mccue
 
Why doesn't the uninstaller just uninstall everything?
 
That always seems like the final insult when I am removing a program that has earned itself an uninstall.

I agree...
But an uninstaller almost always leaves lots of remnants behind (folders and registry).
 
It sounds like the OP might be experiencing a driver related issue (for the Tascam unit).
I'd check the system's DPC latency.
Also, make sure the Tascam isn't connected via a USB3 port.  Many USB2 audio interfaces have issues when connected via USB3.
This is especially true if those USB3 ports are 3rd-party (not integrated into the Intel chipset).
 
If the OP has a backup image file (prior to the issue), I'd recommend reloading that backup image file... and checking performance.
Once the issue is resolved, I'd use True Image or similar to create an up-to-date backup image file.
That's cheap insurance against this type of issue (moving into the future).
 

Try switching the driver mode to ASIO.