We've tracked-down an issue where if you have a *mono* Audio input device connected to your Mac, where it is configured via Audio MIDI Setup to be the default audio input device; Noatikl will crash. I don't know if this explains your problem? The workaround for now is simply to set your Mac to use e.g. the built-in default audio input device, which is two-channel ... we're planning to release a new version that fixes this problem in the coming weeks.

Meanwhile the symptom I was seeing was that Noatikl didn't crash, but it managed to reset the CoreAudio Aggregated Device (and the corresponding hardware devices) as soon as it launched, which of course affected any other software that was configured to use it for I/O.

Let me know if I can send you any logs or anything else that might help explain what is going on.

Yes, I noticed that comment from you, and it *really* perplexed me - I haven't got a clue how that could happen, as all that Noatikl is doing is query the available audio devices at start-up, so it can present them in the list of available devices...!

If there are any other CoreAudio experts who read this and have any bright ideas, please feel free to chip-in to the thread!