28 May
2010
28 May
'10
10:18 p.m.
Paul-
Thanks for the tip. I must have done some stupid mistake before, b/c I
didn't see the ports with 'jack_lsp', but now I do. Now that I have this
software, I'm actually going to use jack for MIDI from now on...not only is
the interface more elegant, you've convinced me of the technical virtues as
well.....
BTW, once it has all the features you'd want, perhaps you could distribute
my python script with each jack release? It is a convenient front-end to he
CL tools already there....some folks might like an alternative to a big GUI
with loads of dependencies, esp. those in a console environment, or those
who don't use KDE or many other QT-based programs.
Thanks again!
AKJ
On Fri, May 28, 2010 at 11:21 AM, Paul Davis <paul(a)linuxaudiosystems.com>wrote;wrote:
On Fri, May 28, 2010 at 12:16 PM, Aaron Krister Johnson <
aaron(a)akjmusic.com> wrote:
--
Aaron Krister Johnson
http://www.akjmusic.com
http://www.untwelve.org
I have not figured out how jack MIDI works---and I never use it (I don't
really see the point when there's ALSA MIDI, frankly, but maybe someone
knows better). I'm willing to add Jack-MIDI access as a feature, but someone
has to tell me how I can connect it and test it from the command line using
jackd (right now, 'jackd .... -X alsa' didn't work for me)
jackd .... -d alsa .... -X seq
the "point" is that it works just like audio, and provides sample-accurate
MIDI delivery with very, very little overhead.