I'm wondering if any Apollo/Satellite Firewire users have any issues using AutoMap 4 with their UAD plugin and SONAR ?
I have experienced a LOT of plugin dropouts since I installed AutoMap 4 onto my system. These occur even when I'm not using an auto-mapped enabled plug-in from UAD. I get constant dropouts of the UAD plugins and they won't restart if I turn them off and back on again (just get another error message that the plug-in(s) has been disabled.
 
I uninstalled AutoMap and everything seems to be working perfectly.

Hi. I do not have a Apollo/Satellite.
But when I had AutoMap installed on my pc (using X3), I had a lot of issues.
Not sure if it was Windows or SONAR related.
Mostly that SONAR would hang, and become unresponsive.
Not had those kind of issues after uninstalling.
Sorry to be of no more help.
All the best.

Thanks Zargg, that helped indeed! There does seem to be something out of sorts with AutoMap. I've uninstalled it and everything seems to run as expected. Still doing some testing to affirm this for my setup, but I think I'm on the right "road" to recovery. Thanks again!!!

Some Novation surfaces can work in MIDI mode without Automap software. Organizing them to work with plug-ins inside Sonar using ACT Plug-in Dynamic Mapping (and the rest of ACT for DAW/transport control) is for sure not "Auto", but possible. The result is almost equivalent to Automap capabilities but there is no "automap wrapper" between plug-ins and Sonar and so there is almost no compatibility issues (with recent Sonars, some bugs in X versions was preventing that way to work without massive tricks).
Unfortunately some Novation surfaces are working throw Automap only (by design), these are impossible to use with alternative approach.
 

Thanks for that insight Azslow3. Yeah it looks like I'm going to have to set this controller up using ACT instead of relying on AutoMap. A little tedious but hopefully it will pay off on the back end!!!

I can describe which possibilities you have if you write the controller model.
In general, "using ACT" is possible with 4 approaches  (only 3 are practical):
1) "Cakewalk ACT MIDI" plug-in
2) "Cakewalk Generic Surface" plug-in
3) my own AZ Controller plug-in
4*) using ACT C++ API write own plug-in
To work with VST mappings (independent from 1-4 plug-in choice) you will need AZ ACT Fix or MarKo ACT Editor (or edit XML manually). "Default" Sonar approach without external tools, while at least possible in Sonar 2017 (some long existing critical bugs was fixed), can be frustrating.