I have Sonar X3d producer, and version 7.4 of UAD's powered plugins.  Everything worked great in Sonar X2 with my UAD plugs, both in the FX bin and in the Prochannel FX chains.  After the X3 upgrade (all versions - x3b, x3c, x3d), every time I open a project which has UAD plugins inside an FX Chain in the Prochannel, the UAD plugins are not active (though they appear to be).  The blue button next to them is engaged, but I have to toggle the plugin off, then back on to get the plugin to 'engage' and audio to route through it.  If I do this with the UAD plugins individually, I can get them to 're-engage' one at a time, but I that's painful when I have 10+ instances like this per project.

One workaround I found was to add a new UAD plugin anywhere in a Prochannel FX chain - this seems to re-engage all the UAD plugins for the whole project at once.  You can then delete the one that just got added and all the rest of the UAD plugins for the project will stay enabled and engaged.  A bit of a pain, but much less headache than trying to disable/re-enable them individually every time you close/re-open the project.  Just to be clear, I've tried globally bypassing all FX and re-enabling them.  That doesn't work.  Neither does toggling the UAD button on/off on the UAD's control panel (this disables/re-enables all UAD plugs globally, but any that were 'disengaged' in the Prochannel FX Chain after re-opening the project will stay disengaged until they're individually disabled/re-enabled via the blue toggle button or a UAD plugin is added to an FX chain somewhere in the project).  Based on how my ACT controller sees UAD plugins differently if they're in the FX Bin or in an FX Chain in the prochannel, I'm guessing Sonar sees them differently and somewhere therein lies the problem...
 
I have also verified that this behavior does not happen if the UAD plugins are in the standard FX bin - they're enabled & engaged as soon as I close/re-open the project; but I like being able to use a combination of them in the FX bin and in FX chains in the Prochannel so this issue is getting to be a pain.

I had hoped the X3d patch would fix this issue, but it doesn't appear to have changed any of the behavior.  I upgraded my UAD plugins in hopes that would fix it, which it did not.
 
Any ideas on other workarounds or when this issue will be resolved (or if it's a UAD issue)?
 
Any ideas on when/if we'll be able to program a set of ACT controls for plugins and have them respond the same way whether they're in the FX bin or in a prochannel FX chain?

Other than this issue, I'm really loving X3, and especially X3d.

Thanks for all your hard work!

I have to ask. Have you RESET and rescaned your plugins? Thx

I have them set to rescan every time I open sonar but will try resetting them tomorrow and then rescanning and will report back. Thx

I have the same issue, a real bummer.

I checked again tonight and after resetting and rescanning my plugins, unfortunately I have the same issue.
 
I have, however, figured out a few more things with some testing, so hopefully that'll point you guys in the right direction.  I verified that adding any UAD plugin to a prochannel FX chain seems to engage all of the UAD plugins in that PC FX chain 'bin' that are already enabled, on all channels of the project, as long as they were cloned tracks.  It's as if the Prochannel FX Chain gets assigned a CLSID and all behave in a linked fashion with regard to UAD plugins in them when the channel gets cloned.  Adding a UAD plugin to one will 're-awaken' all of them that are in PC FX Chain 'bins' that share the same ID.  
 
However, if I clone a channel that has a prochannel FX chain with UAD plugins in it, then add a 2nd FX chain 'bin' & move the UAD plugins to it (so they're in a bin with a separate ID), save and close the project, when I re-open, I can't re-engage all the plugins at once by adding a UAD plugin to a PC FX Chain 'bin' like I could before.  Only those PC FX Chain 'bins' that seem to have the same ID as the original will 're-engage' when I add a UAD plugin.  Adding a non-UAD plugin doesn't seem to 'wake up' the UAD Plugins on that channel either - only adding a UAD plugin does it.  So, I guess that saves a bit of time if I have multiple plugs in a single bin, but really a lot of extra work at this time on projects that have a lot of this going on.
 
This is going to be painful using UAD plugs with Sonar X3 - real bummer as I love a lot of the new features and was looking forward to finishing this project in X3 when I bought the upgrade. 

Would it be helpful if I brought up the issue with UAD as well?  I'd love a solution from either/both of your companies and I'm happy to help troubleshoot as I have a bit of programming background & understand how to hunt bugs.

Thanks

Just a silly idea.


Go to the synth rack and disable MIDI OUT for all synths if available (right click).
See if anything changes, and then try:
Enable MIDI OUT for all synths.
 
Also is this reproducible in brand new projects?

Thanks

Hi Alex, 
 
After noticing the issues I did all my testing in a brand new project, after the reset & rescan of all plugins.  I don't have the option to disable midi out for all synths because there aren't any midi or synth tracks/fx in this project - audio only.  I look for that option in the synth rack & there isn't one unless I add a synth...

Also, if I open my test file in X2, I get a warning that the file is from a newer version, but after I OK that warning, the file plays as expected - all UAD plugs in Prochannel FX Chains work fine and are enabled/engaged immediately on all channels.  The same file in X3 displays the issues.  Seems to definitely be an X3 thing or an issue with upgrading from X2, perhaps?  I wish I had the time/ability to wipe out Sonar & install X3 from scratch but that's a bit time prohibitive at the moment...
 
Any other ideas/workarounds would be greatly appreciated - even if there's just a way to re-engage all the UAD plugins at once with a single action would be a decent workaround for now...

Try renaming your AUD.INI file....

Isn't this stuff with UAD usually something to do with the way they accommodate Sonar in general? I haven't felt like UAD plugs have been working right in X3 from the beginning compared to X2. UA has quite a lot on their hands trying to get AAX versions of their plugs for PT 11, Mac Pro's won't work with their legacy PCI-E inventory, and now X3 is asking more of them. It's too bad everyone is pirating their software and they can't pay their programmers... oh wait...
 
Anyway, I bet this is a UA issue and not a Sonar problem. Of course, I could be wrong.