Re: CoreMidi question
Re: CoreMidi question
- Subject: Re: CoreMidi question
- From: Doug Wyatt <email@hidden>
- Date: Mon, 8 Nov 2004 11:27:21 -0800
There is no way to reroute the MIDI of applications using input and
output ports (a driver like MIDIMonitor's can obtain a copy of the
output to the hardware driver, but that's as far as you can go).
I understand the benefits of a modular approach -- Apple's MIDI Manager
had it. But when designing OMS at Opcode, we looked at how the 90%+ use
case is to want to route to/from the hardware driver, and decided that
the best user experience is to be able to manipulate those connections
directly, within the app. We made the same decision for CoreMIDI.
For apps like the one you're porting, you could create virtual
endpoints in the app, and then write a routing app that creates
MIDIThruConnections to route between virtual endpoints and driver
endpoints ...
Doug
On Nov 8, 2004, at 3:07, Stéphane Letz wrote:
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