Crackle from VSTs

Hey guys, Merry Christmas and cheer in spite of the close of Cakewalk :(
I am in need of some assistance with issue I've gone up and down the wall with.
 
Specs

• Win 10 64-bit
• 8 gb RAM
• 1 TB HD
• Intel Core i7-4700MQ @ 2.4GHz (8 CPUS)

Now, the 8 cpus thing is recent, I used to only have 4 but then this last windows update (1709) hit.
PROBLEM:
I'm getting a consistent, echoey crackle from my VSTs in playback, recording, and input echo (Only XLN and KONTAKT. DPro and Rapture work fine). WAVs appear unaffected.
When playing a VST, crackle/pop plays with it, sample error?
Crackle doesn't show up in the bus.
Using a Scarlett 2i4 1st Gen as a preamp in SONAR Plat. Used to run everything fine, but noticed trouble after the win 10 update.
 
I've uninstalled/reinstalled the sound drivers,
Messed with buffer sizes (low gets worse crackle, going higher still has it.)
Uninstalled/Reinstalled XLN and Kontakt.
Switched from ASIO to MME and WDM only for the quality to get WORSE. 
 
Looked all over the internet and found little on how to deal with the problem.
 
Thanks, 
Cable
 

@Cactus
Ran the check and everything was fine.
Disabling Wi-fi didn't do it either.
 
Addictive Keys, Addictive Drums 2, and Kontakt 5 still have the crackles.

The problem is that something is interrupting the stream of data to your audio interface. The crackles are not happening internally in Sonar, they happen because the audio interface waits for a fraction of a second for more data to feed the DA converter.
 
So, because Dimension Pro and Rapture work fine, but the two others not, let's think about the difference: XLN and Kontakt use HUGE sample sets, so big they will typically not load all the way into RAM. This means that it's somewhat likely that accessing the sample sets on whatever drive they're on, is keeping the sound card driver from feeding the interface.
 
What SATA driver are you using? Are the samples on the C: drive?
 
R

eikelbijter
What SATA driver are you using? Are the samples on the C: drive?

The data flow makes sense, I'm using the C: Drive. Should I put them on one of External HDs?
 

rogeriodec
...the only solution I found was to create a 64-bit version using JBridge.

How'd you go about doing that?

Do you use f.lux by any chance? It has been the cause of many unexplained crackles among those who work with audio on PC's.

I had this issue and contacted XLN about it. When using addictive keys I would get that crackle. I tried to find the emails in the trash but couldn't. I just remember that the .dll file had to be replaced. Contact them to help with that unless you can do it. I was told to delete the file(s) and re install them from the online installer. Go to (advanced) and see the path that they install to and delete them. Then I remember to run the vst scan in sonar to refresh it. Then go back to the installer and re install the keys. I had no problem with AD drums, just the keys. For you I would imagine I would do both. Hope this helps

sharke
Do you use f.lux by any chance? It has been the cause of many unexplained crackles among those who work with audio on PC's.

No, I'm not a user.

OK simple, don't use 32 bit plug ins on a 64 bit version of Sonar unless you want issues. Either find 64 bit replacements or install the 32 bit version of Sonar. Bit Bridge is well know to not work all the time. And for me it causes Sonar to crash randomly on any project I was still running 32 bit plugs. I hated to have to stop using my beloved Mr Tramp but that's progress, gotta keep movin on. 

Cactus Music
 
but that's progress, gotta keep movin on. 

 
That seems at odds with your recent leading of the charge to keep SONAR locked away on a frozen system for years into the future? You don't see the 2 at odds?, something a little off here? perhaps a little selectivity in practice?, one might even dare say hypocrisy? just a little mind you, . . .  you know just a smidge,  . . . a hair,  . . . just a tickle?
 
Amazing, these forums never cease to provide, the SONAR faithful are always good for a good old belly laugh, far better value than a night out at a comedy festival, and it's continuous daily impromptu performances. . . hilarious 

ccable

Cactus Music
OK simple, don't use 32 bit plug ins on a 64 bit version of Sonar unless you want issues.
 

That did it! Thanks so much Mr. Cactus
 
Also, Mr Tramp, God rest it's soul.

Or, as I said, if your 32-bit plugin is indispensable, convert it to 64-bit using JBridge (https://jstuff.wordpress.com/jbridge/).

But the OP was using a completly resonable buffer, If you get crackles at 256 on a computer that is capable like the OP's and he even ran Latency monitor it sort of rules that out. And that leaves us at 32 bit VST's. 
 
And Roger I was to understand that jbridge is a process that runs in the background like bitbridge? 
I didn't know it was a convertor. If it works then why don't the vendors of 32 bit plug ins use it? 
 
OK I was right, it is a background app and so the same as bitbridge and looks like you have to purchase it. 
Only $15 so that's OK and there's a demo. But myself I'm done with 32 bit. Mr Tramp has been replaced with a few others I found like Air's Velvet and even SI Eletric Piano and Lounge Lizzard are doing fine.