Re: Mapping external devices to non-external devices
Re: Mapping external devices to non-external devices
- Subject: Re: Mapping external devices to non-external devices
- From: Doug Wyatt <email@hidden>
- Date: Tue, 30 Sep 2003 15:40:50 -0400
On Sep 27, 2003, at 22:33, Ilya Maykov wrote:
Hi everyone,
I'm sorry if this has been asked before, but I have what I hope is a
pretty simple question. First, let me describe the situation:
- Machine running Mac OS X, using MOTU USB Fast Lane MIDI interface.
The interface has 2 MIDI-in ports and 2 MIDI-Out ports.
- Roland XP-10 connected to port A (or port 0, whatever) of the Fast
Lane.
- In my app, to access the XP-10 it seems that I have to use the fast
lane and I cannot send to or receive from the XP-10 directly. That is,
the XP-10 shows up as external device 0 but has no MIDI entities or
endpoints, while the Fast Lane shows up as MIDI Device 0 and has 2
entities (these are the ports), and each entity has a destination
endpoint and a source endpoint.
Here is the problem - I want my application to be able to present the
user with the names of all connected hardware MIDI devices (i.e.
external devices), and give the user the ability to send or receive to
and from these devices. So it seems that there are two solutions -
either create entities and endpoints on the external device (not sure
if this is possible / is a good idea?),
you should leave creation of entities/endpoints to AMS and drivers
unless you REALLY know what you're doing, it's not worth the trouble
or somehow map the external device to the actual non-external device
that it is connected to. That is, the user will be interacting with
external device 0, the XP-10, but behind the scenes the program will
actually be working with non-external device 0, MOTU Fast Lane, and
interact with the XP-10 through the appropriate MIDI Entity / Endpoint
on the Fast Lane. Obviously, this needs to be portable to work with
any MIDI Interface and any MIDI Device. Does anyone have any ideas?
Let me know if you want me to clarify anything, but I am just really
frustrated with CoreMIDI's documentation and figured that someone on
this forum must have done something like this at some point. Thanks
for the help.
There are some intricacies here but you have the right idea. I just
last week wrote some sample code to cover this issue. I will see about
getting it out ASAP.
Doug
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.