parent
7240871ec9
commit
a6777d8279
|
@ -0,0 +1,102 @@
|
|||
= Overview =
|
||||
Main goal of this project main is to ease usage of legacy, not
|
||||
JACK-ified apps, in a JACK MIDI enabled system.
|
||||
|
||||
There are two ways to use legacy ALSA sequencer applications in JACK
|
||||
MIDI system.
|
||||
|
||||
The first approach is to use automatic bridging. For every ALSA
|
||||
sequencer port you get one JACK MIDI port. If ALSA sequencer port is
|
||||
both input and output one, you get two JACK MIDI ports, one input and
|
||||
output.
|
||||
|
||||
The second approach is to static bridges. You start application that
|
||||
creates one ALSA sequencer port and one JACK MIDI port. Such bridge is
|
||||
unidirectional.
|
||||
|
||||
First approach works almost always except when legacy ALSA sequencer
|
||||
application does not create ports and/or wants existing port to exist
|
||||
so it can capture from or playback to it. Such programs are using the
|
||||
feature of ALSA sequencer framework that allows sending and receiving
|
||||
MIDI events to/from port, without creating connection to it.
|
||||
|
||||
= a2jmidid =
|
||||
a2jmidid is daemon that implements automatic bridging. For every ALSA
|
||||
sequencer port you get one jack midi port. If ALSA sequencer port is
|
||||
both input and output one, you get two JACK MIDI ports, one input and
|
||||
output.
|
||||
|
||||
a2jmidid has two modes of operation, running bridge manually and
|
||||
background D-Bus service.
|
||||
|
||||
To start a2jmidid in manual mode, just run it (and don't supply the
|
||||
special "undocumented" dbus parameter). a2jmidid will start bridging,
|
||||
and you will get output on stdout and stderr. You can stop the bridge
|
||||
using ctrl-c.
|
||||
|
||||
Usually you want to bridge software ports and not bridge hardware
|
||||
ports (they are handled by JACK itself). In case you want to force
|
||||
a2jmidid to bridge hardware ports, you can use the export-hw option:
|
||||
|
||||
a2jmidid -e
|
||||
|
||||
or
|
||||
|
||||
a2jmidid --export-hw
|
||||
|
||||
In D-Bus service mode, a2jmidid works in background. When service
|
||||
access is requested by some application (like a2j_control), dbus
|
||||
session bus daemon activates the object by executing the service
|
||||
executable. The object has methods for starting and stopping the
|
||||
bridging. You can use a2j_control to do this:
|
||||
|
||||
a2j_control start
|
||||
a2j_control stop
|
||||
|
||||
You can deactivate (that may cause later reactivation) the service
|
||||
like this:
|
||||
|
||||
a2j_control exit
|
||||
|
||||
You can query the bridge status using this command:
|
||||
|
||||
a2j_control status
|
||||
|
||||
There also methods (and corresponding a2j_control commands) that can
|
||||
be used to query mapping information.
|
||||
|
||||
a2jmidid implementation is based on jack-alsamidi-0.5 that is [almost]
|
||||
same as jackd ALSA "seq" MIDI backend), both created by Dmitry
|
||||
Baikov.
|
||||
|
||||
= a2jmidi_bridge =
|
||||
a2jmidi_bridge is static bridge that creates one ALSA sequencer
|
||||
playback port and one JACK MIDI capture port. MIDI events sent to ALSA
|
||||
sequencer playback port can be read from the JACK MIDI capture port.
|
||||
|
||||
a2jmidi_bridge has optional argument that allows overriding name used
|
||||
for JACK and ALSA client:
|
||||
|
||||
a2jmidi_bridge "my precious bridge"
|
||||
|
||||
a2jmidi_bridge implementation is based on alsaseq2jackmidi by Sean
|
||||
Bolton.
|
||||
|
||||
= j2amidi_bridge =
|
||||
j2amidi_bridge is static bridge that creates one JACK MIDI playback
|
||||
port and one ALSA sequencer capture port. MIDI events sent to JACK
|
||||
MIDI playback port can be read from the ALSA sequencer capture port.
|
||||
|
||||
j2amidi_bridge has optional argument that allows overriding name used
|
||||
for JACK and ALSA client:
|
||||
|
||||
j2amidi_bridge "my precious bridge"
|
||||
|
||||
j2amidi_bridge implementation is based on jackmidi2alsaseq by Lars
|
||||
Luthman.
|
||||
|
||||
= Contact info =
|
||||
If someone wants to contribute please, contact me (Nedko Arnaudov), or
|
||||
send patches, or request inclusion (Gna! a2jmidid project).
|
||||
|
||||
Packagers are more than welcome too.
|
128
README.rst
128
README.rst
|
@ -1,128 +0,0 @@
|
|||
========
|
||||
a2jmidid
|
||||
========
|
||||
|
||||
This project aims to ease the usage of legacy, non |jack| enabled applications,
|
||||
in a |jack| MIDI enabled system, when using |jack2|
|
||||
|
||||
There are two ways to use legacy |alsa| sequencer applications in a |jack| MIDI
|
||||
system:
|
||||
|
||||
**Automatic bridging**: For every |alsa| sequencer port you get one |jack| MIDI
|
||||
port. If an |alsa| sequencer port is both an input and an output, you get two
|
||||
|jack| MIDI ports, one input and output.
|
||||
(*This approach works almost always except when the legacy ALSA sequencer
|
||||
application does not create ports and/or wants to use an existing port to
|
||||
capture from or playback to. Such programs are using a feature of the |alsa|
|
||||
sequencer framework that allows sending and receiving MIDI events to/from a
|
||||
port, without creating a connection to it.*)
|
||||
|
||||
**Static bridges**: You start an application that creates one |alsa| sequencer
|
||||
port and one |jack| MIDI port. Such a bridge is unidirectional.
|
||||
|
||||
For details on how to build and install this project, look at `INSTALLATION.rst
|
||||
<INSTALLATION.rst>`_.
|
||||
|
||||
a2jmidid
|
||||
--------
|
||||
|
||||
a2jmidid is a daemon that implements **automatic bridging**.
|
||||
|
||||
It has two modes of operation: Running a bridge manually or as a backgrounded
|
||||
|dbus| service.
|
||||
|
||||
Start daemon
|
||||
____________
|
||||
|
||||
To start *a2jmidid* in manual mode, just run the executable.
|
||||
*a2jmidid* will start bridging, and you will get output on stdout and stderr.
|
||||
You can stop the bridge using *ctrl-c*.
|
||||
|
||||
Usually you want to bridge software ports and not bridge hardware
|
||||
ports (they are handled by |jack| itself). In case you want to force
|
||||
*a2jmidid* to bridge hardware ports nonetheless, you can use the according
|
||||
flags::
|
||||
|
||||
a2jmidid -e
|
||||
|
||||
or::
|
||||
|
||||
a2jmidid --export-hw
|
||||
|
||||
Start D-Bus service
|
||||
___________________
|
||||
|
||||
In D-Bus service mode, a2jmidid works in the background. When service access is
|
||||
requested by some application (such as *a2j_control*), the |dbus| session bus
|
||||
daemon activates the object by executing the service executable.
|
||||
|
||||
The object has methods for starting and stopping the
|
||||
bridging. You can use *a2j_control* to do this::
|
||||
|
||||
a2j_control start
|
||||
a2j_control stop
|
||||
|
||||
You can deactivate (that may cause later reactivation) the service
|
||||
like this::
|
||||
|
||||
a2j_control exit
|
||||
|
||||
You can query the bridge status using this command::
|
||||
|
||||
a2j_control status
|
||||
|
||||
There also methods (and corresponding a2j_control commands) that can
|
||||
be used to query mapping information, ivoke without parameters to see help text::
|
||||
|
||||
a2j_control
|
||||
|
||||
The *a2jmidid* implementation is based on *jack-alsamidi-0.5*, which is
|
||||
(almost) identical to the jackd |alsa| *seq* MIDI backend), both created by
|
||||
Dmitry Baikov.
|
||||
|
||||
a2jmidi_bridge
|
||||
--------------
|
||||
|
||||
*a2jmidi_bridge* creates a **static bridge** between one |alsa| sequencer
|
||||
playback port and one |jack| MIDI capture port. MIDI events sent to the |alsa|
|
||||
sequencer playback port can be read from the |jack| MIDI capture port.
|
||||
|
||||
*a2jmidi_bridge* has an optional argument that allows overriding the name used
|
||||
for the |jack| and |alsa| client::
|
||||
|
||||
a2jmidi_bridge "my precious bridge"
|
||||
|
||||
The *a2jmidi_bridge* implementation is based on *alsaseq2jackmidi* by Sean
|
||||
Bolton.
|
||||
|
||||
j2amidi_bridge
|
||||
--------------
|
||||
|
||||
*j2amidi_bridge* creates a **static bridge** between one |jack| MIDI playback
|
||||
port and one |alsa| sequencer capture port. MIDI events sent to |jack|
|
||||
MIDI playback port can be read from the |alsa| sequencer capture port.
|
||||
|
||||
*j2amidi_bridge* has an optional argument that allows overriding the name used
|
||||
for the |jack| and |alsa| client::
|
||||
|
||||
j2amidi_bridge "my precious bridge"
|
||||
|
||||
The *j2amidi_bridge* implementation is based on jackmidi2alsaseq by Lars
|
||||
Luthman.
|
||||
|
||||
.. |jack| raw:: html
|
||||
|
||||
<a href="http://jackaudio.org" target="_blank">JACK</a>
|
||||
|
||||
.. |jack2| raw:: html
|
||||
|
||||
<a href="https://github.com/jackaudio/jack2" target="_blank">jack2</a>
|
||||
|
||||
.. |dbus| raw:: html
|
||||
|
||||
<a href="https://www.freedesktop.org/wiki/Software/dbus/" target="_blank">D-Bus</a>
|
||||
|
||||
.. |alsa| raw:: html
|
||||
|
||||
<a href="https://alsa-project.org/wiki/Main_Page" target="_blank">ALSA</a>
|
||||
|
Loading…
Reference in New Issue