Re: DebugAssert when disconnecting a USB MIDI Interface
Re: DebugAssert when disconnecting a USB MIDI Interface
- Subject: Re: DebugAssert when disconnecting a USB MIDI Interface
- From: Doug Wyatt <email@hidden>
- Date: Tue, 11 Sep 2001 05:12:05 -0700
On Tuesday, September 11, 2001, at 12:01 , Scott Ruda wrote:
I get the following when I disconnect my MIDISport interface while my
Java CoreAudio MIDI application is running:
DebugAssert: Third Party Client: asyncReadResult== noErr [-536870163]
done [line 347, file USBMIDIDriverBase.cpp]
Is this a driver problem, or a problem in the CoreAudio code? Should I
contact MIDIMan?
You could ask MIDIMan to please build their driver without DEBUG
defined. It's a harmless, expected error.
I was hoping that instead I would get a MIDINotification in the
MIDIClient's notification callback when this happens so that I could
shut down my application cleanly.
The 10.0 MIDI driver API didn't have good plug-and-play support. The
driver interface has been extended for 10.1...
Doug
--
Doug Wyatt
work: email@hidden (CoreAudio)
personal: email@hidden
http://www.sonosphere.com
"Premature optimization is the root of all evil."
-- Knuth