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 01:18:09 +0800
Hi,
On Mar 27, 2008, at 1:07 AM, Jeremy Sagan wrote:
I wonder if this problem may be related to a firewire audio driver
because I notice that my firewire audio device using the default
Apple driver shows a inaccessible MIDI device in AMS. Also a bunch
of MIDI messages are sent went the computer sleeps or the device is
powered off.
Do you also have a Firewire audio device Daniel?
No, it's USB based, but the implementaion is self-made, using a
propietary IOUserClient/IOConnect approach. This part is however not
the problem - debug dumps show MIDI messages arriving in the driver
after sleep and wakeup just as expected. Only they don't make it to
the application. That's also why I strongly believe the MIDIServer is
the part which misbehaves here. If there was a EnableSource(1) after
wakeup, everything would be fine.
Greets,
Daniel
On Mar 26, 2008, at 12:47 PM, Daniel Mack wrote:
Hi,
On Mar 27, 2008, at 12:18 AM, Doug Wyatt wrote:
A client application is calling MIDIPortDisconnectSource. It's not
the MIDIServer, and not the CoreMIDI client framework.
As I said, the same thing happens with Echo.cpp from the
SampleTools that ship with Xcode. Certainly, there is no
MIDIPortDisconnectSource in that code, I just double checked that.
So what else than the MIDIServer is in the chain that could be
possibly blamed for that?
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