26 Aug
2007
26 Aug
'07
9:06 p.m.
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/
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
29 Aug
29 Aug
6:39 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG1dlve8HF+6xeOIcRAusDAKDl7zwgCpHFGkFSPcOA1LLWa6+CswCgtpOa
GCT2LRuJO/ySe2Uyy6+ldZg=
=BFTr
-----END PGP SIGNATURE-----
30 Aug
30 Aug
8:05 a.m.
Ken Restivo <ken(a)restivo.org> writes:
On Mon, Aug 27, 2007 at 02:05:55AM +0300, Nedko
Arnaudov wrote:
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>
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?
6253
days inactive
6257
days old
linux-audio-user@lists.linuxaudio.org
2 comments
2 participants
participants (2)
-
Ken Restivo -
Nedko Arnaudov