Without looking at the setup it's hard to tell, but some possible causes include:
The All-in-One has too many devices (you can try to remove devices that are not in use).
The All-in-One is not correctly synchronised, which will make CoreAudio work extra hard. This can be fixed within SoundDesk from the AIO Setup window or the Audio MIDI Setup application (Utilities Folder).
It can also be caused by other Applications that connect to any of the devices in the AIO and is forcing a different sample rate. If you have the option, ensure all applications are running at the same rate to prevent resampling.
Or a particular device that uses a lot of CPU, you can try and disable one device at a time in the AIO setup and see if the consumption goes down.
I have the minimum required devices - Mic, Headset, SoundDesk Virtual Cable (Stereo) and SoundDesk Virtual Driver (Master). Should I make a different device Master or doesn't it matter?
Everything is in Sync with 44.1 kHz
I suspect it might have been caused by the Microsoft Teams Audio driver. It seems to be a piece of garbage and I had it in the All-in-One before but removed it now.
It seems to run more stable but I still get the random time where SoundDesk just freezes up for a few seconds - there is no audio and then it starts working again.
Comments
Any idea what could be causing my coreaudiod to go up to 539 % CPU usage? I simply restart SoundDesk and it goes back to normal.
Without looking at the setup it's hard to tell, but some possible causes include:
The All-in-One has too many devices (you can try to remove devices that are not in use).
The All-in-One is not correctly synchronised, which will make CoreAudio work extra hard. This can be fixed within SoundDesk from the AIO Setup window or the Audio MIDI Setup application (Utilities Folder).
It can also be caused by other Applications that connect to any of the devices in the AIO and is forcing a different sample rate. If you have the option, ensure all applications are running at the same rate to prevent resampling.
Or a particular device that uses a lot of CPU, you can try and disable one device at a time in the AIO setup and see if the consumption goes down.
Hi - thanks for getting back to me.
It seems to run more stable but I still get the random time where SoundDesk just freezes up for a few seconds - there is no audio and then it starts working again.
+1 on thinking teams audio driver is crapware