removing ReferenceID as log in item MAC OS

Sean Richards yes, you can disable the “Launch on startup” setting in the standalone app Preferences:

Disabling “Launch on startup” does not work for me. It starts everytime. annoying.

same for me, no way of avoiding soundid launch at startup. 

tried as described above and all macos places where these login items hide. no success

macos 12.7.6, soundid 5.12.1

same for me. I hate that! it is like being hacked!

If anyone figures this out, please post a “how to.” For now, Everytime I boot up, the first thing I do is "quit" Sonarworks. I want to control when it's used.

Same here. “Launch on startup” is set to OFF.  Still, every time I start my computer it opens.

Same here - “Launch on startup” is switched to OFF, yet it starts up everytime I launch, plus it overrides my interface as default sound input/output!

I think it is related to having a UAD Apollo Interface connected to the Computer. What “launches” on startup is needed to dump the settings into the Apollo Interface for the new “Monitor/Headphone Correction” in UAD Console.
https://www.youtube.com/watch?v=9F3aUd4IcUw

That would make sense, Gerald, if this was a new development. However, Sonarworks auto-launching on startup has been an issue long before the new UAD/Sonarworks partnership. Also, I believe it is also the case for those who don't use UAD interfaces.

Same Problem here! Please fix it

OSX ventura 13.4.1  

Same for me ! 

Sequoia  15.1.1 

delete it and buy ARC System Advanced…I did 

same problem here!

Could it be related to the latests UAD plugins installers? 

same problem on Windows 11 UAD 11.5.2

Same problem!!!

Since I've posted a couple of times on this thread, I keep an eye on it and get notifications when someone new posts. What mystifies me is why Sonarworks themselves have not posted a comment. This is their forum, it's not The Gear Page or UAD's forum. This is a legitimate issue that is great annoyance to users and, depending on the project and other output software I need to use, causes me to have to re-boot my computer so I can quit Sonarworks before launching other software. This issue isn't just a bunch of whinny users complaining because a GUI light is green rather than blue. The comment above about ditching Sonarworks and just buying an ARC is becoming a real possibility for me.

same here… 

Skip Burzumato exactly! Come on sonarworks: it's time to step up your game! 

Guys, ARC system advanced is the key! 
I simply forgot that I installed it. 

You don’t need any support for UAD! 

It’s a hardware solution. You save your measurements on a stereo in/out box. This sits between your PC/Mac and your monitors.

And you also get software if you want to use headphone presets, etc.

No more on/off actions and updates, etc. It’s a game changer for me.

I always struggled with Sonarworks.

I don’t know how well or poorly Sonarworks works with the new UAD hardware implementation.

But this wasn’t an option for me: 1. I don’t want to buy new hardware just for this solution. 2. I don’t know how to route my system sound for OBS and other online programs using Sonarworks with UAD.

My system:

MacBook M1, Ventura, UAD Apollo 8 (not 8x, this is the minimum setup you need to save Sonarworks settings directly on it), Studio One 7.

Get more info on the web, but trust me, those 200 bucks have been one of the best investments I’ve made so far!
Cheers 

It's still an issue - I have Loopback for routing and UAD Apollo for interface and I don['t want it auto starting.  as when it does it then after a short time crashes CoreAudio.  I don't wna or need Sonarworks to start as it's used as a plugin either on my UAD or GingerAudio depending on my location. - this absolutley needs fixing as it means I have to quickly shut it down on login to stop it creating issues with CoreAudio

Im on Mac OS 15.1 keeps happening for me as well, its very frustration as have the ‘Launch on startup’ software set to off. This thread is 4 months old, has there been any response from Sonarworks support?

Hey all, I reached out to Sonarworks with a help ticket. Arty at SW responded pretty quickly. He said they have seen the forum posts here and elsewhere, are aware of the issue of SoundID automatically launching on system start-up even when it's not selected as a start-up app, and are working on it. I I'm confident they will get it sorted. 

In the meantime, I have a sticky note I put on my screen every time I shutdown to remind me to quit SW when I boot up before launching PT or any of my DAWs. An “analog” solution to a “digital” problem. : )

I HAVE APPLIED THE ACTIONS LISTED BELOW AND RESOLVED THE ISSUE. THIS WAS SENT TO MY BY TECH SUPPORT THIS MORNING.

For now, I can only recommend reverting back to the previous version of SoundID Reference, which doesn't feature the integration. Follow these steps:
 
 

1. Uninstall SoundID Reference fully: [MAC] How to uninstall SoundID Reference
2. Download and reinstall the previous version here: SoundID Reference 5.12.0.50.pkg

This is becoming ridiculous, and extremely unprofessional. Any company in their support page they will at least tell you that they are working on it. This is pretty bad bug. Going back to a previous version is not a solution, but thank you Bennis Sims for sharing it.

Anyone has some news?

Were you able to download the version in the link and if so it didn’t work? It absolutely worked for me but you have to do the full uninstall.

Hey Gang, I've been one of the main drivers of this thread. I've been communicating back and forth with Arty from Sonarworks who is a total professional and very helpful. I went through the uninstall/reinstall process of 5.12 about three days ago, and the problem has cleared up. I feel confident that they are working on the issue. However, it requires some cooperation with other hardware and software vendors as well, in my case, the Universal Audio. It's not just Sonarworks that caused this problem. I know I'm only one case, but I'm satisfied for now until UA updates Console and SonarWorks follows with an update to SoundID.

Best,

Skip

Hi all, 

Thanks for contributing and my apologies for not responding here sooner. Some of you wrote in already, and we were able to provide a workaround for those of you. Bennie Sims and Skip Burzumato thanks for sharing. Yes, indeed, this is an issue we’re aware of and we are communicating with UA to get this resolved in a future update. Meanwhile, installing the last version before the integration was published will be a good workaround: 
 

1. Uninstall SoundID Reference: [MAC] How to uninstall SoundID Reference
2. Install version 5.12

For those cases that are not related to UAD, here are steps to follow to ensure a smoother experience:  

1. In SoundID Reference app > Preferences > and ensure that "Launch on startup" is disabled.
2. Access System Preferences > Launch items > and confirm that SoundID Reference is disabled.
3. Open Finder > Go > Go to Folder.
4. Enter ~/Library/LaunchAgents.
5. Delete the file named com.sonarworks.soundid.reference.systemwide.plist.

If any issue persists, certainly let us know by submitting a support request. Thanks! 

Just an update. Closing down soundid after login is not enough because it keeps reopening upon interaction with uad console.

So finally I deleted the systemwide app but not the vst/au. No issue so far for me but I have to remark that in this way the software is crippled and suggesting an unsigned download from a google drive is not what I expect from sonarworks.

Cheers,

Lorenzo

I use a simple set and forget workaround on MacOSX for that. You can create an Automator workflow that quits a specific application on Mac startup. You can use the "Quit Application" action in the "Utilities" Library and then schedule the workflow to run on login via the "Login Items" in System Settings. 

Steps:

1. Open Automator and create a new Application: Launch Automator and choose "New Application". 
2. Add the "Quit Application" action: In the "Utilities" Library, drag the "Quit Application" action onto the workflow window.
3. Select the application to quit: In the "Quit Application" action, choose the specific application you want to close on startup. 
4. Save the Automator application: Save the workflow as an application (e.g., "Quit [Application Name]"). 
5. Add the Automator app to Login Items:
   • Go to System Settings > General > Login Items. 
   • Click the "+" button and find the saved Automator application. 
   • Add it to the Login Items list. 
6. Verify on startup: After logging in, you should see that the selected application is closed automatically. 

As soon as Sonarworks got it sorted out with UAD simply delete this Login Item