Re: MIDI driver hibernation problem
Re: MIDI driver hibernation problem
- Subject: Re: MIDI driver hibernation problem
- From: Daniel Mack <email@hidden>
- Date: Thu, 27 Mar 2008 11:42:12 +0800
Hi Doug,
On Mar 27, 2008, at 7:05 AM, Doug Wyatt wrote:
The backtrace shows MIDIServerMessagePort::ReceiveMessage() calling
the internal implementation of MIDIPortDisconnectSource(). It only
does this when some client calls MIDIPortDisconnectSource().
Ok, so now I stripped down my MIDI driver to the max, only leaving
very basic functionality like ::Start(), ::Stop()
and ::EnableSource(). I also added a timer which outputs a note on
event once a second in case ::EnableSource(1) was called before. The
implementation derived from MIDIDriver has around 100 lines of code
now. I put that online for you to have a look at: http://caiaq.de/download/SimpleMIDIDriver.zip
(~11kb).
For the client side, I also chose the most dumb application I could
find which is Echo.cpp with enabled debug prints. The Echo process is
the only one which is attached to the MIDIServer (e.g., as soon as I
kill it, the MIDIServer quits).
However, putting the machine to sleep still shows the behaviour I
described, even though neither the driver nor the client handles
hibernation in any way.
So tell me - did I do anything terribly wrong in my implementation? Is
there any basic knowledge I missed?
Thanks,
Daniel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden