27 Oct
2007
27 Oct
'07
11:41 a.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.
New in this release is addition of configure script (autotools) that
enables compatibility with different JACK MIDI API variants.
Planned features/improvements:
* One JACK client per ALSA sequencer client
* 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>
27 Oct
27 Oct
12:50 p.m.
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.
New in this release is addition of configure script (autotools) that
enables compatibility with different JACK MIDI API variants.
Planned features/improvements:
* One JACK client per ALSA sequencer client
* 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/
hallo nedko, the v2 builds good here, but either there is something
wrong or i am doing something wrong, but i do not get any sound out of a2j.
what i am doing:
-starting a2j
-starting specimen or zynjacku(with zyn)
-starting vkeybd
-now connecting vkeybd from the a2j-midi-tab with the synth (specimen/zyn)
-the synth is connected to alsa-audio, but plying with vkeybd - no sound.
if i connect the same vkeybd with the same specimen via alsa-midi i can
play specimen, or if i start jack-keyboard and connect to zyn, i also
get the sound out of the machine.
i did some experiments with muse too, but no success.
reading this email, do you have a feeling that i am doing sth wrong?
cheers,
doc
5:13 p.m.
Dragan Noveski <perodog(a)gmx.net> writes:
Nedko Arnaudov wrote:
Unfortunately I have no idea why it does not work at your computer. As
first step I'd try with some monitoring app connected to a2jmidid output
port. The two ones I know about are jack_mididump that I think comes
with jack itself and gmidimonitor (GTK app). Also zynjacku, unless
started with synth URL at command line, has MIDI indicator in upper
right corner.
--
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.
New in this release is addition of configure script (autotools) that
enables compatibility with different JACK MIDI API variants.
Planned features/improvements:
* One JACK client per ALSA sequencer client
* 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/
hallo nedko, the v2 builds good here, but either there is something
wrong or i am doing something wrong, but i do not get any sound out of
a2j.
what i am doing:
-starting a2j
-starting specimen or zynjacku(with zyn)
-starting vkeybd
-now connecting vkeybd from the a2j-midi-tab with the synth (specimen/zyn)
-the synth is connected to alsa-audio, but plying with vkeybd - no sound.
if i connect the same vkeybd with the same specimen via alsa-midi i
can play specimen, or if i start jack-keyboard and connect to zyn, i
also get the sound out of the machine.
i did some experiments with muse too, but no success.
reading this email, do you have a feeling that i am doing sth wrong?
29 Oct
29 Oct
10:55 a.m.
Nedko Arnaudov wrote:
Dragan Noveski <perodog(a)gmx.net> writes:
it is really strange - i got a2jmidid to work like:
jack-keayboard->a2j->specimen-alsamidi,
but i cannot get it to work another way, like:
vkeybd ->a2j->zyn/specimen/or gmidimonitor.
also in muse, i cannot find the 'a2j' port in the settings dialog....
cheers,
doc
Nedko Arnaudov wrote:
Unfortunately I have no idea why it does not work at your computer. As
first step I'd try with some monitoring app connected to a2jmidid output
port. The two ones I know about are jack_mididump that I think comes
with jack itself and gmidimonitor (GTK app). Also zynjacku, unless
started with synth URL at command line, has MIDI indicator in upper
right corner.
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.
New in this release is addition of configure script (autotools) that
enables compatibility with different JACK MIDI API variants.
Planned features/improvements:
* One JACK client per ALSA sequencer client
* 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/
hallo nedko, the v2 builds good here, but either there is something
wrong or i am doing something wrong, but i do not get any sound out of
a2j.
what i am doing:
-starting a2j
-starting specimen or zynjacku(with zyn)
-starting vkeybd
-now connecting vkeybd from the a2j-midi-tab with the synth (specimen/zyn)
-the synth is connected to alsa-audio, but plying with vkeybd - no sound.
if i connect the same vkeybd with the same specimen via alsa-midi i
can play specimen, or if i start jack-keyboard and connect to zyn, i
also get the sound out of the machine.
i did some experiments with muse too, but no success.
reading this email, do you have a feeling that i am doing sth wrong?
2:55 p.m.
Dragan Noveski <perodog(a)gmx.net> writes:
it is really strange - i got a2jmidid to work like:
jack-keayboard->a2j->specimen-alsamidi,
but i cannot get it to work another way, like:
vkeybd ->a2j->zyn/specimen/or gmidimonitor.
also in muse, i cannot find the 'a2j' port in the settings dialog....
ALSA MIDI has "feature" that allows sending MIDI events without
connecting to the port. It may be related somehow.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
27 Oct
27 Oct
4:03 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, Oct 27, 2007 at 04:40:59PM +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.
New in this release is addition of configure script (autotools) that
enables compatibility with different JACK MIDI API variants.
Planned features/improvements:
* One JACK client per ALSA sequencer client
* 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/
Now, just to make sure I understand: this is for people who are using released versions of
jackd that *do* suppport JACK MIDI (i.e 0.103.0), but aren't using the lastest jackd
from SVN which has suport for the -X option to do this functionality within jackd,
correct?
Once there's a new jackd release, with the -X option, will this too be needed anymore?
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHI3zze8HF+6xeOIcRAv6UAKCwu8bxsVlsHRKEbb9acNewp8nUxgCgnIQE
ZP929ulUvr8bajCzCC84xo0=
=COQu
-----END PGP SIGNATURE-----
5:23 p.m.
Ken Restivo <ken(a)restivo.org> writes:
On Sat, Oct 27,
2007 at 04:40:59PM +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.
[snip]
Now, just to make sure I understand: this is for
people who are using
released versions of jackd that *do* suppport JACK MIDI (i.e 0.103.0),
but aren't using the lastest jackd from SVN which has suport for the
-X option to do this functionality within jackd, correct?
It will help them, but not with hardware ALSA seq MIDI ports, because
currently a2jmidid ignores them. This can be fixed easily in code until
a2jmidid gets more configurable.
Once there's a new jackd release, with the -X
option, will this too be
needed anymore?
It will still be needed for users that want using raw ALSA MIDI backend
(and skipping additional ALSA sequencer layer). This is setup I have
here, I use -X raw but I still need connecting legacy ALSA MIDI apps to
JACK MIDI apps.
Althrough not intentional, it may help for JACK drivers that don't
support JACK MIDI nativily yet. IIRC JACK MIDI ffado driver support is
not ready yet.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
6:36 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, Oct 27, 2007 at 10:23:23PM +0300, Nedko Arnaudov wrote:
Ken Restivo <ken(a)restivo.org> writes:
Thanks.
Will it also work with jackdmp?
I have been procrastinating trying out jackdmp because JACK MIDI hasn't been merged in
to it yet, but if this will bridge that gap for me, I'll try it out.
- -ken
On Sat, Oct 27,
2007 at 04:40:59PM +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.
[snip]
Now, just to make sure I understand: this is for
people who are using
released versions of jackd that *do* suppport JACK MIDI (i.e 0.103.0),
but aren't using the lastest jackd from SVN which has suport for the
-X option to do this functionality within jackd, correct?
It will help them, but not with hardware ALSA seq MIDI ports, because
currently a2jmidid ignores them. This can be fixed easily in code until
a2jmidid gets more configurable.
Once there's a new jackd release, with the -X
option, will this too be
needed anymore?
It will still be needed for users that want using raw ALSA MIDI backend
(and skipping additional ALSA sequencer layer). This is setup I have
here, I use -X raw but I still need connecting legacy ALSA MIDI apps to
JACK MIDI apps.
Althrough not intentional, it may help for JACK drivers that don't
support JACK MIDI nativily yet. IIRC JACK MIDI ffado driver support is
not ready yet.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHI6EEe8HF+6xeOIcRAlkUAJ92M4m/1Zc/JgRTvsY9iy5b9tcbpwCgsftQ
vFrNFuntUjKboSsSuKvCdk4=
=c2pl
-----END PGP SIGNATURE-----
6:44 p.m.
Ken Restivo <ken(a)restivo.org> writes:
On Sat, Oct 27,
2007 at 10:23:23PM +0300, Nedko Arnaudov wrote:
I never used jackdmp, so I really have no idea.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Ken Restivo <ken(a)restivo.org> writes:
Thanks.
Will it also work with jackdmp?
I have been procrastinating trying out jackdmp because JACK MIDI
hasn't been merged in to it yet, but if this will bridge that gap for
me, I'll try it out. On Sat, Oct 27, 2007 at 04:40:59PM +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.
[snip]
Now, just to make sure I understand: this is for
people who are
using released versions of jackd that *do* suppport JACK MIDI (i.e
0.103.0), but aren't using the lastest jackd from SVN which has
suport for the -X option to do this functionality within jackd,
correct?
It will help them, but not with hardware ALSA seq MIDI ports,
because currently a2jmidid ignores them. This can be fixed easily in
code until a2jmidid gets more configurable.
Once there's a new jackd release, with the -X
option, will this
too be needed anymore?
It will still be needed for users that want using raw ALSA
MIDI
backend (and skipping additional ALSA sequencer layer). This is
setup I have here, I use -X raw but I still need connecting legacy
ALSA MIDI apps to JACK MIDI apps.
Althrough not intentional, it may help for JACK drivers that don't
support JACK MIDI nativily yet. IIRC JACK MIDI ffado driver support
is not ready yet.
6706
days inactive
6708
days old
linux-audio-user@lists.linuxaudio.org
8 comments
3 participants
participants (3)
-
Dragan Noveski -
Ken Restivo -
Nedko Arnaudov