VX-64 Vocal Strip Problem

A lot of the time when I insert VX-64 vocal strip onto a clip track it just freaks out and immediately cuts all audio (in that one track) off and starts puting out a high pitched ringing or noise that doesn't stop unless you turn the plugin off or remove it. Stop playback wont stop it.
 
Anybody else have this problem and fixed it?
 
edit: it's Sonar X3 Producer

I also use the VX-64 a lot and haven't had the problem until very recently. It doesn't happen every time, only rarely, and doesn't happen on every machine where I have SONAR installed. I am trying to come up with steps to reproduce to send to support. Perhaps you and I can figure it out.
 
It does seem to be dependent on some other condition. What happens if you start a new project and insert the VX-64? 
 
I have a feeling this is one of those "UFO bugs" where people who've experienced the bug believe it exists, but most people don't experience it.

Anderton
I've been working on it this afternoon and stumbled on a project where the bug isn't 100% repeatable, but close enough that I've sent it to the Bakers for analysis. Hopefully it will screw up on their system and not be something system-specific.
 
The workaround for now is not to ctrl-drag the VX-64 from one FX bin to another, but save the preset (call it "temp" or whatever), open a new instance in the other track, and call up the preset.

When it happens to me I just drag the plugin from the Browser to the FX bin. It either immediately freaks out (not usually) but when it usually happens is when I start changing the settings and going through the presets.
So for me it's usually adding it to the FX bin from browser and then changing the presets and settings.

Just tried it on my Win8.1 PC and I dragged and droped from browser and then Ctrl + draged from that FX bin to three other bins and then changed presets and settings. Worked fine.
 
I am not saying that it ain't happening to ya'll. Just reporting what's happening here.

So, dragging from one FX bin to another and dragging from the browser can cause this.  For now, I would add it from the menu instead of by dragging.  I realize I am stating the obvious--just noting that it you don't get the problem unless you are dragging it, that may help them zero in.

OK, DragonBlood.  M misunderstanding based on some other comments.
 
Sounds like this is a tricky one.  Good luck.

I had the same problem with VX-64.  I am using Sonar X3 and although I am about to upgrade my computer, I have been using it successfully on an older laptop.  It was fast enough but I only had 4GB RAM.  I suspect that this is the problem with some plugins that may be memory hungry.  It doesn't matter how you instantiate VX-64, whether by dragging or selecting from the menu, if there is not enough RAM, it just freaks as the OP said.  What I get is a click when I instantiate the plugin and no more audio.  I have one project that uses VX-64 but I wanted another instance of it in another track and that was the result.  I tried getting more RAM for this machine but there were compatibility problems, even after a BIOS update.  So I thought I would just upgrade the whole lot.  New computer this week with 16GB RAM and hopefully no more issues with VX-64 or some other heavy plugins.

Yep, I have had it do that too.  I could instantiate the plugin but as soon as I enabled EQ, I got the click and no audio. 

GuitarLegend
Yep, I have had it do that too.  I could instantiate the plugin but as soon as I enabled EQ, I got the click and no audio. 

Wow. Two cases can't be a coincidence.
 
Problem is, there's no recipe to reproduce the issue.
 
It comes and go as a ghost .
 
Disabling the internal EQ seems to be the only workaround.

Tried to load it yesterday on a 48khz project and the VX caused a feedback on the strip (meters cliping and all). Loaded it on another project (44 kHz) and it was fine... Could sampling rates be a cause?
 

I have had it happen in Platinum several times already. It really is hard to nail it down because the same fix doesn't work every time. Sometimes just removing the vx64 and reinserting does the trick, sometimes it is another plug in that has to be removed and reinserted. I have had to remove and reinsert a console emulator or a nomad factory plugin before to get it going again, but for sure the only time it happens is when inserting the vx 64.

i get it sometimes using sonar platinum.. turned off the delay in the strip and clears the problem.. turn delay back on and it pops again rendering the plug in useless.. needs fixing coz happening more often now

I've been trying to provide a recipe to reproduce so the Bakers can fix it. The intermittent nature is a problem. Just when I think I've created something where it screws up, I'll load the project once more just to make sure before sending it off, and of course, then it works fine and continues to do so...
 
If anyone can come up with a way to reproduce this problem, it can get solved but for whatever reason, they can't get it to misbehave at the mothership. 

Like 'Kukitron' above i get it sometimes using sonar platinum.. turned off the delay in the strip and clears the problem.. turn delay back on and it pops again rendering the plug in useless
 
Then I saw 'musicroom' post above and moved the VX-64 from the fx bin to the prochannel and its works. 
If I swap from a 44 track project to a project with a lower track count (22) it's ok.
 
Sonar Platinum
Windows 7 Home Premium
Service Pack 1
Intel(R) Core(TM) i7-2600K CPU @3.40Ghz
16.0Gb RAM
64bit OS

Had the problem for the first time today.  I deleted VX-64 from the track and then re-substantiated it.  Seems to work fine at the moment.  As a matter of fact, when I last closed the project yesterday, it was acting normally.  I was only when I opened up the project today that it started acting up.