Hi,
macOS (latest macOS, latest HW, but doesn't matter) seems to prevent CoreMIDI driver logging with standard logging procedures (syslog, unified logging).
The only chance to log something is writing to a file at one of the rare write-accessible locations for CoreMIDI.
How is this supposed to work? Any hint is highly appreciated. Thanks!
Though this seems to generally work, the system (CoreMIDI?) can come into a situation where logging just stops.
can come into a situation where logging just stops.
Is that system wide? Or just for the process running your CoreMIDI driver?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
One possible explanation for the behaviour you’re seeing is log quarantining. If a process logs way too much, the system log will protect itself by quarantining that process, preventing any of its log entries from being recorded. When that happens, you’ll see a log entry like this:
type: fault
time: 2025-10-28 10:58:03.178550 +0000
process: Test783965
category: -
message: QUARANTINED DUE TO HIGH LOGGING VOLUME
So, if you see this again, check the system log for an entry like this.
ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"