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

Never had this problem. And I use VX-64 a lot.

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.

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.

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.

Thanks for the additional info, I'll pass it along. What I'm finding in general is that a bug can manifest itself in several ways. So if there's a way to make the bug repeatable, then often when it's fixed the corollary issues will be fixed as well.

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.

Grem
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.

Well I'm on an AMD chipset so maybe that has something to do with it.

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.

konradh
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.

I think this one is responding to me. Didnt bring up dragging it from other FX bins but alright. I dont think they dragging has much of anything to do with it though, because I think it has more to do with how it starts up internally.
The real problem is changing the settings and it freaks out and stops working. Think it's more of a coding and programming issue really.