Did syslog break for CoreAudio/MIDI server plugins?

Question

Created Jan ’22

Replies 2

Boosts 0

Views 1.1k

Participants 2

The very little and outdated 'documentation' shared by Apple about CoreAudio and CoreMIDI server plugins suggested to use syslog for logging. At least since Bug Sur syslog doesn't end up anywhere.

(So, while you seem to think its OK to not document your APIs you could at least remove not working APIs then! Not to do so causes unnecessary and frustrating bug hunting?)

Should we replace syslog by unified logging? For debugging purpose only our plugins write to our own log files. Where can I find suitable locations? Where is this documented?

Thanks, hagen.

Boost

Answer 1

DTS Engineer OP

Apple

Jan ’22

Should we replace syslog by unified logging?

Yes.

Indeed, that’s universally true. I can’t think of any circumstance where it’s better to stick with the legacy ASL or syslog APIs [1].

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] Hmmm, except if you have cross-platform code, where I can see why you might want to stick with syslog.

0

Answer 2

hagen OP

Jan ’22

Thanks, Quinn!

For debugging purpose and exchanging of logs/dumps its sometimes easier to directly write to log files. Which are suitable locations to write from CoreAudio and CoreMIDI? (We see that permissions do change between the MacOS versions.)

Thanks, hagen.

0