serial midi driver (oh no!)
serial midi driver (oh no!)
- Subject: serial midi driver (oh no!)
- From: email@hidden
- Date: Tue, 10 Jul 2007 17:58:29 -0400 (EDT)
hello all,
I'm trying to develop a user space midi driver based on apple's serial
midi driver code. I'm using a piece of hardware with an ftdi chip, and
for the actual drivers, I'm using ftdi's virtual comm port drivers
(ftdi-chip.com). the callout bsd path for my device shows up as
"cu.mydevice001"
right now I'm just trying to get my user space driver to match my device.
I'm getting as far as SerialMIDIDeviceManager::MatchDevice. where my
project fails is at the following lines:
if (MIDIGetSerialPortOwner(serDevice->GetPortName(), &portOwner) != noErr)
return false;
result = CFEqual(portOwner, mDriver->GetIdentifier());
...
return result;
at first, portOwner would be set to CFSTR(""). MatchDevice would return
false because mDriver->GetIdentifier() would return CFSTR("mydevice001").
then to info.plist I added the following key value pair.
<key>MIDIDriverUsesSerial</key>
<string>YES</string>
I did this because I read in the documentation for MIDIDriver.h, 'This
constant, "MIDIDriverUsesSerial", when defined to "YES" in a driver's
bundle, tells MIDIServer that the driver uses serial ports and is eligible
to have serial ports assigned to it,' and that was the best sense I could
make of it.
anyway, now MIDIGetSerialPortOwner just returns false.
I guess I'm confused about a couple of things. I don't understand what it
means for a MIDI driver to own a serial port. I also don't understand how
the midi server decides which drivers own which serial ports.
can anyone explain these things to me? or does anyone have any
suggestions or ideas about what's going on? thanks a lot!
Joe
_______________________________________________
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