What version of UAD are you running?

This was happening with sonar x2 and an update of UAD to version 6.5 finally fixed it.

If you use a lot UAD plugs then this can get really annoying, I even had it when exporting or bouncing tracks that had no UAD plugs. The message would come up for every instance in the project regardless.

I'm using

stoutlyric
What version of UAD are you running?

This was happening with sonar x2 and an update of UAD to version 6.5 finally fixed it.

If you use a lot UAD plugs then this can get really annoying, I even had it when exporting or bouncing tracks that had no UAD plugs. The message would come up for every instance in the project regardless.

I believe its version 7.2  Iv'e been using UAD for three months now with no problems till X3

So sad that this message has popped back up with x3, i'll have to wait then for it to get resolved until i can try out the new car.

Last time I contacted UAD and Cakewalk about this and the issue then was on the UAD side. I had to wait for the new 6.5 release that fixed the issue.

stoutlyric
So sad that this message has popped back up with x3, i'll have to wait then for it to get resolved until i can try out the new car.

Last time I contacted UAD and Cakewalk about this and the issue then was on the UAD side. I had to wait for the new 6.5 release that fixed the issue.

I have notified our team about this subject  We are currently looking into it.  I apologize for the wait on this.

That message is coming from the UAD plugins and not from SONAR. SONAR uses a custom UAD plugin chaining API to let the plugins optimize streaming on the DSP bus when there are side by side UAD plugins in the bin. The driver is warning you that there will be plugin latency when you insert another plugin that is not a UAD plugin.
If that message appears in SONAR X3 and not X2 that it is likely that the UA plugins are checking for a specific SONAR version and silencing that message. Since X3 is a new version the message is unmasked. You will have to contact UA for a resolution to the message issue if it bothers you. 
 
There is an independent issue with using UAD plugins alongside other VST3 plugins in the bin. That will be fixed in the next update. 

Hello Noel,
 
Thank you for verifying the UAD / VST 3 issue, do you have a timeline on when the patch will be issued? I rely on UAD and Waves plugins, but I suppose I can use X2 for the time being.
 
 

Phonic
Hello Noel,
 
Thank you for verifying the UAD / VST 3 issue, do you have a timeline on when the patch will be issued? I rely on UAD and Waves plugins, but I suppose I can use X2 for the time being.
 
 

There's a setting in Preferences that prevents Sonar from replacing VST2 plugs with their VST3 counterparts. Use this until the update and you won't have to go back to X2.

Noel Borthwick [Cakewalk]
You will have to contact UA for a resolution to the message issue if it bothers you. 
 

I live in a dream world, where UA monitors this thread and will resolve this issue without my sending out user concerns about my plugin not plugging in right with X3.  Then I can lay back, have a drink with an umbrella in it, and know that all is good in the universe.
They also don't officially test their plug-ins with Sonar, so I'm happy that it works with X2, I smile, and I'll get back to writing music.
Just a little frustrated, but I'll get over that.

GTex62

Noel Borthwick [Cakewalk]
You will have to contact UA for a resolution to the message issue if it bothers you. 
 

I live in a dream world, where UA monitors this thread and will resolve this issue without my sending out user concerns about my plugin not plugging in right with X3.  Then I can lay back, have a drink with an umbrella in it, and know that all is good in the universe.
They also don't officially test their plug-ins with Sonar, so I'm happy that it works with X2, I smile, and I'll get back to writing music.
Just a little frustrated, but I'll get over that.

I reported it a couple days ago. UA said it would be fixed in a near-future release.

The main problem with using UAD plugins alongside VST3 plugins has been fixed in X3B. 
After reading this thread its not clear to me what the remaining issue is. From SONAR's side there have been no changes in how UAD plugins themselves are handled. Also UAD plugins themselves are not VST3 so as such its all being handled very similarly to X2.
 
Regarding the message, that is a warning that is displayed from the plugin itself telling you that if you sandwich non UAD plugins in a UAD plugin chain you will incur latency. The plugin knows this because of SONAR's support for the UAD chaining API. As I said earlier any such message can be suppressed only from the plugin so the fix needs to come from UA. Unless we disable the integration completely which would result in less efficient streaming. 
 
So what is the remaining issue besides this? Latency is expected if you sandwich other plugins between UAD plugins. Thats how their design works and you will see exactly the same behavior in any version of SONAR.