On Mon, Feb 22, 2010 at 06:06:55PM -0500, Paul Davis wrote: > >> But why is your app giving midi-ports both for jack and > >> alsa at the same time? > > > > Why not? I think that doing this actually serves users > > better, especially since JACK MIDI adoption is still on the > > up-swing. > > 1) it makes the app quite a bit more complex > 2) it introduces yet another name mapping scheme from ALSA<->JACK > 3) its a job best left for specialized clients like a2jmidid > 4) it makes it harder to write an app that can be used with or without JACK
Aeolus also provides both when used in Jack mode. As regards (1), it's mainly the Jack interface that complicates things as many of the MIDI messages can't be handled in the process callback. Ciao, -- FA O tu, che porte, correndo si ? E guerra e morte ! _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
