CoreMidi question
CoreMidi question
- Subject: CoreMidi question
- From: Stéphane Letz <email@hidden>
- Date: Mon, 8 Nov 2004 12:07:39 +0100
Hi,
I'm porting an application coming from Linux where the ALSA API is used
to handle MIDI.
On Linux the ALSA sequencer API allows Midi Inter Application
Communication similar to what CoreMidi does. But people usually use an
external connection manager like "qjackctl"
(http://qjackctl.sourceforge.net/) to handle connections/deconnections
between physical Midi devices and applications or between applications.
For what I understand from reading the documentation, using the
CoreMidi API, an application can :
- either create an input/output port, scan the available endpoints and
possibly connect to them to send/receive Midi data. In this case the
*application* has to present the user (with a User Interface) a way to
decide what he wants to connect to the application input/output port.
- or create "virtual" input/output endpoints so that other applications
can connect to. In this case other applications can connect to the
given application.
The question is : is there a *generic* way to handle connections
between Midi devices/applications without having to implement a
connection manager in each application? Is there a way to implement an
application that would handle connection for all running CoreMidi
applications in a similar way that a tool like "qjackctl" allows on
Linux?
Thanks
Stephane Letz
_______________________________________________
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