Ken Restivo <ken@xxxxxxxxxxx> writes: > On Mon, Aug 27, 2007 at 02:05:55AM +0300, Nedko Arnaudov wrote: >> a2jmidid is daemon for exposing legacy ALSA sequencer applications in >> JACK MIDI system. It is based on jack-alsamidi-0.5 (jackd alsa seq midi >> backend) by Dmitry Baikov. The main purpose is to ease usage of legacy, >> not JACK-ified apps, in JACK MIDI enabled systems. >> >> It is tested, and works, here, with current SVN jack. ATM it may or may >> not work with other variants. >> >> Planned features/improvements: >> * One JACK client per ALSA sequencer client >> * Improved build system (autotools) and support (better handling) for >> other JACK variants (older MIDI API variants, jackdmp) >> * More control on what ports to bridge (currently bridging is fixed to >> non-hardware ports). >> * Real daemonization with log file, init.d script, etc. >> >> If someone wants to contribute please, contact me, or send patches, or >> request inclusion (Gna! a2jmidid project). As usual, packagers are more >> than welcome too. >> >> Homepage with screenshots: http://home.gna.org/a2jmidid/ >> >> Tarball download: http://download.gna.org/a2jmidid/ >> > > What is the difference between this application, and running jackd -X seq? With current codebase, none (or minor, non-essential). Main purpose it to handle hardware devices through raw midi in jackd and alsa seq apps through a2jmidid simultaneously. -- Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Attachment:
pgp5OvxwuPueB.pgp
Description: PGP signature
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
