Is it possible for a Sonar project to get a virus?  Ok, not really, but...
 
I'm not so sure it's the specific VST, maybe Sonar, maybe even a combination of the VST and effects, but I can only get this to happen when using Cinesamples Cinebells VST.  I can work all day on a project, but at some point, when I load up to start again, as soon as cinebells sounds a note, the meter maxes out and locks in that position and you can no longer hear the instrument, along with the Main and any sub busses (currently EW Spaces) I have it running through.  If I mute the channels, the sound meter will slowly lower to zero and playback will work again until I un-mute Cinebells.  I can no longer use Cinebells for that project.  All other instruments (including other CS instruments) work fine.  I can start a new project, drop in CB and spaces or whatever and it works fine.  I have shut down Sonar, my interface and MIDI equipment, and completely restarted everything and still get the same result in the same project.  
 
Anyone see this before?
 
 
 

It may not be Cinebells. Various others (including me) have had similar problems with various plugins. See this thread.
 
http://forum.cakewalk.com/The-good-old-Loud-click-peaking-VU-meters-DC-output-horrible-noise-problem-m3500258.aspx#3501909
 
Cheers, Peter.
 

Thanks.  Strange indeed.
 
It has happened to me 3 or 4 times, but every time it has, Cinebells triggered the overload.
 
I do hope Cakewalk is looking into this.  May be time to get 1 or 2 backup DAWS.  Time is money.

It's likely not Cinebells since that would mean Kontakt is the problem, which is highly unlikely. You could have a corrupt sample, but that's not likely either. The more likely scenario is you a an FX plugin on a track somewhere that is causing it. You should, track by track, disable all your plugins, test that your project is stable, then slowly, track by track, enable one plugin at a time and test. Eventually, you'll find the plugin and you can decide then to stop using it or live with the problems that it causes.
 
Unless you submit a crash dump to Sonar, or give a detailed report about which plugin is the cause and how to consistently make the issue arise, I doubt Cakewalk is looking into it since they wouldn't know where to start.
 
Regards,
Dan

Thank you.  I understand the point about submitting a crash dump, but I thought this was an existing issue as noted above in another thread.  Unfortunately, it doesn't cause Sonar to crash and generate a report, so I don't really have anything to provide.  It just peaks the meters and stops my workflow completely.  I did take your advice and bypass all FX to start adding in 1 effect at a time.  However, even with all effects bypassed, as soon as I hit play, the meters peak and sound stops.  However, when I mute Cinebells, playback resumes normally, even with all effects on.
 
I do have 2 cinebell instruments stacked in 1 instance of Kontact.  Maybe I'll try separating them into their own tracks next.  That, or just stop using cinebells :/  

CdrDave
Thank you.  I understand the point about submitting a crash dump, but I thought this was an existing issue as noted above in another thread.  Unfortunately, it doesn't cause Sonar to crash and generate a report, so I don't really have anything to provide.  It just peaks the meters and stops my workflow completely.  I did take your advice and bypass all FX to start adding in 1 effect at a time.  However, even with all effects bypassed, as soon as I hit play, the meters peak and sound stops.  However, when I mute Cinebells, playback resumes normally, even with all effects on.
 
I do have 2 cinebell instruments stacked in 1 instance of Kontact.  Maybe I'll try separating them into their own tracks next.  That, or just stop using cinebells :/  

It is not a common problem. I have only ever experienced it with a wonky plugin and I stopped using those as soon as I could find suitable replacements.
 
Try disabling any internal effects in Cinebells itself. May be a buggy bit of code in there...
 
Regards,
Dan
 
 

Well, this is strange.  Maybe found the culprit - will continue working today and see if it happens again.  At the moment, in this project, Sonar does not like Cinebells using Neutron on its channel and feeding into a bus with EW Spaces.
 
I setup a new file with just CB, Neutron, and Spaces, and it works just fine.  So maybe something with this FX chain in combination with more tracks and various other effects at the same time.  :/    

CdrDave
Well, this is strange.  Maybe found the culprit - will continue working today and see if it happens again.  At the moment, in this project, Sonar does not like Cinebells using Neutron on its channel and feeding into a bus with EW Spaces.
 
I setup a new file with just CB, Neutron, and Spaces, and it works just fine.  So maybe something with this FX chain in combination with more tracks and various other effects at the same time.  :/    

Neutron can be somewhat of a CPU hog, so it may be that it is causing an "almost dropout"...
 
So, it sounds like you are using mixing plugins with virtual instruments? I generally don't do that until I have bounced everything down to audio. I do understand the desire to keep your options open, but I don't like dealing with creativity-killing issues like you are seeing. I don't start mixing until tracking is complete.
 
Regards,
Dan
 

You are absolutely correct.  I know that would be the best way to do it, but at this point I still find myself wanting to make musical changes based on things I hear during the mix.  That, and I often do library work, starting with the "long" arrangement, getting it really close on the mix, then chopping it down to 2-3 other versions (normal, short, loop, etc) that are basically the same in the mix without having to start over on each.
 
That would be a great goal for myself this year.  Commit!   lol 
 

An effect plugin would seem the most likely culprit. Or conceivably an effect within Kontakt, although it seems unlikely such a bug would have escaped broader notice given Kontakt's ubiquitousness.
 
A corrupt library is very unlikely, at least on its own, as extreme levels are only possible with floating-point data. I can, however, envision a scenario where a corrupt wave file (e.g. every sample is FFFFFFFFFFFF) might trigger a floating-point math error in a plugin. This would give the illusion of being an intermittent problem, since you'd have to hit a specific sample in order to see it.
 
For your test project, try creating a MIDI track that hits every note and every velocity. I know, that's going to be time-consuming (copy-and-paste will speed it up) and you probably won't bother - unless you're like me and can't let go of a mystery until it's solved.