Looked for the post but can't find it, maybe somebody else can. There was some specific issue with a third party plugin and vst3 to be fixed next release.. Confirmed by a baker.

I have no idea about the scope of the VST3 issue, whether other plugins are effected or not.

Doktor Avalanche
Looked for the post but can't find it, maybe somebody else can. There was some specific issue with a third party plugin and vst3 to be fixed next release.. Confirmed by a baker.

I have no idea about the scope of the VST3 issue, whether other plugins are effected or not.

Okay, I thought you said there was some "some issue with VST3 going on with JP," which implied more than a single plug-in with a problem that's already been identified. So I don't think anyone has to worry about whether the CA-2A works with VST3 or not, and I believe the CA-2A was the topic of this thread.
 
Carry on. 

Well it wasn't stated that the VST3 issue was just specific to a specific plugin or not, it certainly was confirmed as a JP issue and not the plugin.

As stated I don't know the scope nor was it made clear by the baker from memory. So no full conclusion.

Ta.

There are zero JP specific issues with VST3. There was one issue with VST3 which we have addressed for the next update which dates back to X3. And with regard to CA-2A there are no issues that have been officially logged that I am aware of.

CA-2A also works for my purposes, responses appreciated, this is not meant to be mean, but it is true.

What issue/s are you having?

Called tech support to fix Silent hardware + VST re-link issue.
When opening a project containing CA-2A, there was a link issue even after the project was saved. Not a big deal, but annoying and time to resolve. Was told the plugin was old (as if that had anything to do with the OP) Tech then guided me on a journey to resolve the issue, which is still happening.

 

Noel Borthwick [Cakewalk]
There are zero JP specific issues with VST3. There was one issue with VST3 which we have addressed for the next update which dates back to X3. And with regard to CA-2A there are no issues that have been officially logged that I am aware of.

Thanks Noel. Nice to have information instead of speculation.

sadicus
Was told the plugin was old (as if that had anything to do with the OP) Tech then guided me on a journey to resolve the issue, which is still happening.

Did they tell you to reset and re-scan, or something else?

Doktor Avalanche
Looked for the post but can't find it, maybe somebody else can. There was some specific issue with a third party plugin and vst3 to be fixed next release.. Confirmed by a baker.

I have no idea about the scope of the VST3 issue, whether other plugins are effected or not.

 
This is the post that stated the vst3 issue. See Dan Cate's post within:

http://forum.cakewalk.com...-m3311157.aspx#3311360

Did they tell you to reset and re-scan, or something else?

Manual Scan + Rescan Failed + Rescan Existing (doing that again, right now)

always get the support person's name ;-)