Core Audio and launchd- 80% CPU Usage all the time.

I solved this. App called SoundID by SonarWorks. Remove it if this CoreAudio thing ever occurs. It calls for coreaudiod basically 100% - whether it's "open" or not. Happy to have scored a victory stumbling on this after analyzing each item in Activity Monitor and when clicking on coreaudiod for a sampling of the real-time processes, this app's stuff showed up in the string - so -- deleted every file i could find with its name in it, and the coreaudiod processes totally disappeared. FYI. Thanks!

Replying to my own question here to say, after poking around with Terminal and in Activity Monitor, looking at what was eating up the CPU by using the "Sample" process option on coreaudiod in this case...the constant-80% CPU 'user' -- i scanned through what came up and noted the name of an audio app that was installed about a month ago designed to analyze audio recording for equalization of room dimensions - trashed everything i could find related to that app using FindMyFile - and voila, no more coreaudiod in the Activity Monitor. At all. Hate to speak to soon but i gotta think that did it. The app, btw is SoundID by Sonarworks. I deleted everything under either of those names. (and will not be toying with that ever again). And all this as i was just about to reinstall my OS for the second time...as well as reading multiple 'solutions' involving creation of an Audio Prefs folder which apparently others have seen cause an issue --but I never had that folder where they suggested it needed to be - so it didn't add up. Hope this might help anyone else who might ever encounter the issue. Thanks

Just an edit to say...when I just look at where core audio components reside on my MB Pro on High Sierra... I'm seeing the elements in totally different locations than where they show up in the Mini/Mojave.... I have never had any issues on that Mac and CoreAudio does not even show up in Activity Monitor most of the time.and if so, neglible usage, and no "launchd" activity...but i have most of the same older apps on the MBPro. Would it make sense - and i don't even know if i can do this - to somehow copy the coreaudio components from the laptop, transfer them over to the Mac Mini - and plant them in the corresponding folders on the Mini - basically just replicating where the key components are found on a machine which has no issues with CoreAudio. BTW I did reinstall Mojave already on the Mini and it didn't at all resolve the problem described. Really don't know why this has to be so complicated.