10 Mar
2016
10 Mar
'16
1:26 p.m.
Hello,
I’m working on a project where we’d like to interface a MIDI board (livid’s brain jr.) to
the IDJC application (http://idjc.sourceforge.net <http://idjc.sourceforge.net/>).
As of by now, we’re able to configure the board and send MIDI commands through the USB
port to the Ubuntu Studio that is our development box.
However, and as you’ll see in the attached screenshot
(https://www.dropbox.com/s/ss9i5bwaqzs5ays/idjc.png?dl=0), IDJC is only able to retrieve
MIDI Commands from JACK and not from ALSA.
I understand that there’s a way to route the MIDI channels from ALSA to JACK and this can
be done through ALSA PATCH BAY (http://pkl.net/~node/software/alsa-patch-bay/
<http://pkl.net/~node/software/alsa-patch-bay/> ) for example.
I’d be glad if you could drop some lines to this conversation, I have in fact two
questions:
1.- Does anybody have an experience with the livid brain jr, ALSA, JACK and IDJC?
2.- Is there a possibility to route directly midi commands to JACK avoiding ALSA?
Thank you very much for your time and help.
Cheers,
Nacho
10 Mar
10 Mar
1:42 p.m.
Nacho Otal, Mar 10 2016:
...
2.- Is there a possibility to route directly midi
commands to JACK avoiding ALSA?
Not avoiding ALSA, since ALSA drives the hardware
and JACK sits ontop of ahrdware drivers. BUT...
You can start JACK with the -xseq or -xraw commandline options and it will give you your
hardware MIDI ports. Tried and tested.
Or you use a2j_midibridge or a similar tool, and if necessary its reverse, which will
bridge JACK MIDI ports to the ALSA sequencer system, also tried and tested. Sorry, I have
no URL for those extra packages, but you should be able to find them on the net.
...
Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter: http://twitter.com/ffanci_silvain
* GitHub: https://github.com/fsilvain
2:16 p.m.
On Thu, Mar 10, 2016 at 7:42 AM, Ffanci Silvain <silvain(a)freeshell.de>
wrote:
Nacho Otal, Mar 10 2016:
...
Not strictly true. Applications which use JACK MIDI can exchange MIDI data
directly, without ALSA. But yes, if you want to use MIDI hardware, ALSA
will always be involved.
2.- Is there a possibility to route directly midi
commands to JACK
avoiding ALSA?
Not avoiding ALSA, since ALSA drives the hardware and JACK sits ontop of
ahrdware drivers. BUT...
You can start JACK with the -xseq or -xraw commandline
options and it will
give you your hardware MIDI ports. Tried and tested.
Or you use a2j_midibridge or a similar tool, and if necessary its reverse,
which will bridge JACK MIDI
a2jmidid -e
Note that JACK1 has this functionality built in, and using -X seq will
activate it.
1:48 p.m.
Hello Nacho,
On 03/10/2016 01:26 PM, Nacho Otal wrote:
Hello,
I’m working on a project where we’d like to interface a MIDI board (livid’s brain jr.) to
the IDJC application (http://idjc.sourceforge.net <http://idjc.sourceforge.net/>).
As of by now, we’re able to configure the board and send MIDI commands through the USB
port to the Ubuntu Studio that is our development box.
However, and as you’ll see in the attached screenshot
(https://www.dropbox.com/s/ss9i5bwaqzs5ays/idjc.png?dl=0), IDJC is only able to retrieve
MIDI Commands from JACK and not from ALSA.
I understand that there’s a way to route the MIDI channels from ALSA to JACK and this can
be done through ALSA PATCH BAY (http://pkl.net/~node/software/alsa-patch-bay/
<http://pkl.net/~node/software/alsa-patch-bay/> ) for example.
I’d be glad if you could drop some lines to this conversation, I have in fact two
questions:
1.- Does anybody have an experience with the livid brain jr, ALSA, JACK and IDJC?
2.- Is there a possibility to route directly midi commands to JACK avoiding ALSA?
Thank you very much for your time and help.
You can try using JACK with -Xseq, this will trigger the JACK internal
ALSA-JACK MIDI bridge. There's also a direct JACK option for this but
that depends on the JACK version you're using. IIRC for Jack2 this is
-Xalsarawmidi. You can also use a2jmidid but then you need to start that
in the background after having started JACK.
Jeremy
2:01 p.m.
On Thu, 10 Mar 2016 13:48:09 +0100, Jeremy Jongepier wrote:
IIRC for Jack2 this is -Xalsarawmidi. You can also use
a2jmidid but
then you need to start that in the background after having started
JACK.
No, -Xalsarawmidi does reduce MIDI jitter, but requires a2jmidid for the
routing. If needed I run
jackd --sync -Xalsarawmidi -dalsa -r48000 -p256
and
a2jmidid -e
$ man a2jmidid | grep -A2 OPTIONS
OPTIONS
-e | --export-hw
forces a2jmidid to bridge hardware ports as well as software ports
As already pointed out, newer versions of jack 1 provide an option that
also reduces MIDI jitter and a2jmidid isn't needed, but I didn't use it.
2:18 p.m.
On Thu, 10 Mar 2016 14:01:25 +0100, Ralf Mardorf wrote:
On Thu, 10 Mar 2016 13:48:09 +0100, Jeremy Jongepier
wrote:
My apologies, if no ALSA software ports are needed at all, I seem to be
mistaken.
IIRC for Jack2 this is -Xalsarawmidi. You can also
use a2jmidid but
then you need to start that in the background after having started
JACK.
No, -Xalsarawmidi does reduce MIDI jitter, but requires a2jmidid for
the routing. 
5:31 p.m.
On Thu, 10 Mar 2016, Nacho Otal wrote:
Hello,
I’m working on a project where we’d like to interface a MIDI board (livid’s brain
jr.) to the IDJC application (http://idjc.sourceforge.net).
As of by now, we’re able to configure the board and send MIDI commands through
the USB port to the Ubuntu Studio that is our development box.
However, and as you’ll see in the attached screenshot
(https://www.dropbox.com/s/ss9i5bwaqzs5ays/idjc.png?dl=0), IDJC is only able to
retrieve MIDI Commands from JACK and not from ALSA.
a2j_control ehw start
This command can be run from qjackctl as a script so that starting
jackdbus also starts a2jmidid.
a2jmidid allows jack to see alsa's midi ports.
--
Len Ovens
www.ovenwerks.net
3208
days inactive
3208
days old
linux-audio-user@lists.linuxaudio.org
6 comments
6 participants
participants (6)
-
Ffanci Silvain -
Jeremy Jongepier -
Len Ovens -
Nacho Otal -
Paul Davis -
Ralf Mardorf