On Windows it also installs a service (UAHelperService) so it isn’ t enough just to rename the app - you’d have to disable the service too.I renamed the Mac UA app and all seems well. I tried the same trick in Windows but the process was still going somehow
On MacOS the equivalent is under General / Login Items / Allow in Background, so you’ll have a Universal Audio entry there too. That's pointed at the com.uaudio.bsd.helper launch daemon (MacOS, itself, won't tell you this). So you can turn that off, if you want, too.
In this case, I think (It has definitely put me off buying any UA native plugins. It just introduces an extra layer of faff I don't need if it mucks around with iLok cloud even if you dont use the bloody thing.
As it is, the LA-2A stands apart, the only Native product that uses machine authorisation and it does seem you can uninstall UA Connect and have it working just fine.
) the issue might be that their manager has been coded with the expectation of either dongle or cloud, and you can set the priority of those per machine. But this doesn't do you much good when you've got the one plugin those settings don't apply to Whilst, personally, I'd rather not have all of these managers that want to permanently run and think they know what they’re doing - until they don’t, I wouldn’t let it put you off the UA plugins overall. They’re fairly solid, usually good on CPU, and the rename “trick” is an annoyance but easy enough. IMO UA Connect is far from the worst of its type.
Statistics: Posted by PAK — Sun Mar 24, 2024 11:44 am