Serious Problem After Installing X1b

I'm having real problems after installing the patch for X1b. Basically, the audio from Sonar is full of pops and crackles of digital distortion, like it's having loads off buffer issues. The thing is, everything works perfectly up to X1a.
 
I have tried increasing the latency. I've got the latest drivers installed (Tascam US-800). I've tried removing all effects. I've done a full re-install of my system (Windows 7 Home Premium 64bit). I've even tried sticking my old Creative Labs X-fi card in instead, and this exhibits the same problem, i.e. works fine up to X1a. The latest hot-fix does nothing to change this situation.
 
The project I am using to test is only 2 guitar tracks, a bass track and a drum track. The guitars and bass are using Guitar Rig 4 LE and the drums are done with Submersible Kit Core.
 
A similar project recorded in REAPER is fine, so it does seem to me that it is something in the X1b update. Anyone have any ideas?
 

Nyorai


I'm having real problems after installing the patch for X1b. Basically, the audio from Sonar is full of pops and crackles of digital distortion, like it's having loads off buffer issues. The thing is, everything works perfectly up to X1a.
 
I have tried increasing the latency. I've got the latest drivers installed (Tascam US-800). I've tried removing all effects. I've done a full re-install of my system (Windows 7 Home Premium 64bit). I've even tried sticking my old Creative Labs X-fi card in instead, and this exhibits the same problem, i.e. works fine up to X1a. The latest hot-fix does nothing to change this situation.
 
The project I am using to test is only 2 guitar tracks, a bass track and a drum track. The guitars and bass are using Guitar Rig 4 LE and the drums are done with Submersible Kit Core.
 
A similar project recorded in REAPER is fine, so it does seem to me that it is something in the X1b update. Anyone have any ideas?
 

I don't really care about reaper.
Did you install both Quick Fix patches for X1b?


Thanks,
-D

I don't really care about reaper.


Thanks,
-D

Fortunately plenty of people do. Did you have something real to say? 

Thanks for the replies. I'm using ASIO drivers, but it makes no difference what driver type I use other than WDM is worse. I have tried deleting the AUD.INI and that doesn't make a difference either. The latest build of X1b (246) still exhibits the problem.

@DJSur
I only mentioned that everything works in REAPER simply to point out that another DAW does not exhibit this problem so I presume the problem is an issue between my system and Sonar X1b.

I am going to try out setting up X1b on my laptop and see how that goes, it's a similar spec to my PC.

2.13GHz Core 2 Duo, 2GB RAM

This MIGHT be related to your problem, though if you've frozen your tracks, I can't see the RAM being a problem.

I have also read that the Tascam drivers aren't the best in the world.

@Bristol_Jonesey
It might, it is an old but faithful PC, but X1a works perfectly.

I think there must be something in my project files that X1b doesn't like. I've created a new empty project and copied all audio and MIDI from the projects I have a problem with and everything works perfectly. Creating new projects seems to be OK so far as well.

twoifbysea

I don't really care about reaper.


Thanks,
-D

Fortunately plenty of people do. Did you have something real to say? 

Good for them. Reaper is not germaine to the man's issue. 


Good day, Sir.


-D 

After further investigation I also found I get crackles when opening or scrolling the Sysx view while playing so I'm pretty sure it's GUI update related. I've run everything on my Dell laptop (similar spec to my PC) and everything is fine, even with the tempo view open. The main difference is that the Dell uses an Nvidia chipset whereas my PC is an ATI. I do have an old Nvidia card knocking about which I will try if I can find it.

I don't know if this will lighten things but I have also used a ¨custom/empty tracks¨ template ie. a template from older sonar version. I haven't had time to test if the error remains if I open a new project with a ¨standard¨ template. About the graphics I have nvidia gt120.

Glad to see that you may be on your way to solve this.

Hello Nyorai,
I don't know what the heck is going on but after testing open up a new project with the original ¨normal¨ template all seems to work perfect. Since I got Sonar X1 I thought that there where no good templates to start a project with and thus moved a ¨blank¨template from my old sonar installation and all was working fine until for a while ago, I didn't connect it with x1b but I must say that you might be right in your conclution, at least it seems so right now. I will continue to look in to this and in the mean time a big thank you.
Regards Jörgen

Windows 7 Home Premium 64 bit 2.13GHz Core 2 Duo 2GB RAM

 
Are you sure the machine isn't RAM starved?
Open up Task Manager and have a look at the RAM usage.
If the machine is hitting the VM swapfile (in lieu of physical RAM), that would explain the poor performance.
 
Reaper has a smaller footprint... so it may just be "skating by" with the 2GB of RAM.
 
FWIW, 2GB of RAM is really not enough to comfortably run Win7x64.
I'd want 4GB bare minimum...