4 Jun
2007
4 Jun
'07
2:48 a.m.
I just downloaded dino, and it became pretty clear that I don't have
jack midi working. I'm running jack version 0.103.0 on debian sid.
is there a way to enable jack midi functionality to my existing jack
without having to pull the whole thing apart and put it back together?
thanks,
--
Josh Lawrence
http://www.hardbop200.com
http://www.joshlawrencetrio.com
4 Jun
4 Jun
2:55 a.m.
On 3 June 2007 at 23:48, "Josh Lawrence" <hardbop200(a)gmail.com> wrote:
I just downloaded dino, and it became pretty clear
that I don't have
jack midi working. I'm running jack version 0.103.0 on debian sid.
is there a way to enable jack midi functionality to my existing jack
without having to pull the whole thing apart and put it back together?
qjackctl has a MIDI tab. Is that of any use to you?
--
Kevin
2:59 a.m.
On Sun Jun 03, 2007 at 09:55:15PM -0700, Kevin Cosgrove wrote:
On 3 June 2007 at 23:48, "Josh Lawrence" <hardbop200(a)gmail.com> wrote:
no, and neither is qjackctl. how do you get it to realize jackd is already running and
therefore show the start button dimmed (so it doesnt error out trying to launch another
one). wheres the input for a custom command string?
to get jack midi going, you can add jackmidi to your USE flags on gentoo. im not sure how
to do it on debian - i guess you just hope they enabled midi in their binary, or compile
it yourself?
to get jackd to see your alsa midi devices, you have to do some extra work. namely use
http://subversion.jackaudio.org/jack/branches/midi/jack and add the -X flag to jackd
initiation (i could only get raw working)
I just downloaded dino, and it became pretty
clear that I don't have
jack midi working. I'm running jack version 0.103.0 on debian sid.
is there a way to enable jack midi functionality to my existing jack
without having to pull the whole thing apart and put it back together?
qjackctl has a MIDI tab. Is that of any use to you?
--
Kevin
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
6:04 a.m.
On 6/4/07, carmen <_(a)whats-your.name> wrote:
to get jackd to see your alsa midi devices, you have
to do some extra work. namely use http://subversion.jackaudio.org/jack/branches/midi/jack
and add the -X flag to jackd initiation (i could only get raw working)
Midi driver is the the trunk already :)
http://subversion.jackaudio.org/jack/trunk
Seems, it's better to remove midi branch to prevent confusion.
Dmitry.
2:29 p.m.
On Mon, 2007-06-04 at 12:04 +0400, Dmitry Baikov wrote:
On 6/4/07, carmen <_(a)whats-your.name> wrote:
agreed, wholeheartedly. please svn remove it ...
to get jackd to see your alsa midi devices, you
have to do some extra work. namely use
http://subversion.jackaudio.org/jack/branches/midi/jack and add the -X flag to jackd
initiation (i could only get raw working)
Midi driver is the the trunk already :)
http://subversion.jackaudio.org/jack/trunk
Seems, it's better to remove midi branch to prevent confusion.
9:20 p.m.
On 6/4/07, Dmitry Baikov <dsbaikov(a)gmail.com> wrote:
On 6/4/07, carmen <_(a)whats-your.name> wrote:
so just to make sure I understand you correctly, to get jack midi
working on my box I would need to completely uninstall the debian
version and install from source, correct?
--
Josh Lawrence
http://www.hardbop200.com
http://www.joshlawrencetrio.com
to get jackd to see your alsa midi devices, you
have to do some extra work. namely use
http://subversion.jackaudio.org/jack/branches/midi/jack and add the -X flag to jackd
initiation (i could only get raw working)
Midi driver is the the trunk already :)
http://subversion.jackaudio.org/jack/trunk
10:12 p.m.
On Mon Jun 04, 2007 at 06:20:44PM -0500, Josh Lawrence wrote:
On 6/4/07, Dmitry Baikov <dsbaikov(a)gmail.com>
wrote:
no.. you can install your version in parallel - typical user compiled software ends up in
/usr/local/ by default, and /usr/local/bin is usually in $PATH before /usr/bin.
what this means is you shouldnt have to uninstall anything, at most you wil need to add
/usr/local/bin to your PATH variable.
you probably dont even need to compile jackd if you dont want alsa-midi (and are using a
bridge like alsaseq2jackmidi)
On 6/4/07, carmen <_(a)whats-your.name>
wrote:
so just to make sure I understand you correctly, to get jack midi
working on my box I would need to completely uninstall the debian
version and install from source, correct? to get jackd to see your alsa midi devices, you
have to do some extra
work. namely use
http://subversion.jackaudio.org/jack/branches/midi/jack
and add the -X flag to jackd initiation (i could only get raw working)
Midi driver is the the trunk already :)
http://subversion.jackaudio.org/jack/trunk
--
Josh Lawrence
http://www.hardbop200.com
http://www.joshlawrencetrio.com
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
11:02 p.m.
On Mon, 2007-06-04 at 20:12 -0400, carmen wrote:
On Mon Jun 04, 2007 at 06:20:44PM -0500, Josh Lawrence
wrote:
you should be banished from LA* forever for this comment.
no regular user should EVER EVER EVER EVER install JACK in two locations
on their machine. we deal with endless problems with this attempt.
please do not recommend it.
if you want to install from source, you need to use --prefix=/usr at the
configure step. or face all kinds of puzzling and irritating behaviour.
--p
On 6/4/07, Dmitry Baikov
<dsbaikov(a)gmail.com> wrote:
no.. you can install your version in parallel - typical user compiled software ends up in
/usr/local/ by default, and /usr/local/bin is usually in $PATH before /usr/bin. On 6/4/07, carmen <_(a)whats-your.name>
wrote:
so just to make sure I understand you correctly, to get jack midi
working on my box I would need to completely uninstall the debian
version and install from source, correct? to get jackd to see your alsa midi devices, you
have to do some extra
work. namely use
http://subversion.jackaudio.org/jack/branches/midi/jack
and add the -X flag to jackd initiation (i could only get raw working)
Midi driver is the the trunk already :)
http://subversion.jackaudio.org/jack/trunk 
5 Jun
5 Jun
5:40 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Jun 04, 2007 at 06:20:44PM -0500, Josh Lawrence wrote:
On 6/4/07, Dmitry Baikov <dsbaikov(a)gmail.com>
wrote:
I am using synths that require JACK MIDI support, such as AZR3, using the Debian Sid
binary package of the released 0.103 jackd. Haven't had any need to compile anything.
JACK MIDI seems to work just fine in the released jackd package. I use the
alsaseq2jackmidi utility to access it. The connections show up in the released QJackCtl,
jack_lsp, and aconnect. I connect my synth to alsaseq2jackmidi using MIDI, then connect
alsaseq2jackmidi to the synth using jack.
I'm told that yet-to-be-released SVN versions of jackd do the bridging within itself,
obviating the need for this alsaseq2jackmidi kludge, but I haven't had any need for
that yet.
- -ken
On 6/4/07, carmen <_(a)whats-your.name>
wrote:
so just to make sure I understand you correctly, to get jack midi
working on my box I would need to completely uninstall the debian
version and install from source, correct?
to get jackd to see your alsa midi devices, you
have to do some extra
work. namely use
http://subversion.jackaudio.org/jack/branches/midi/jack
and add the -X flag to jackd initiation (i could only get raw working)
Midi driver is the the trunk already :)
http://subversion.jackaudio.org/jack/trunk -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGZRNZe8HF+6xeOIcRAhKVAKDLqArSVRMOKKc2Atm0DjkKIij81wCg6YrF
MbpcF0pxVBHPaYX8kgu0oqw=
=eiRr
-----END PGP SIGNATURE-----
10:35 a.m.
On Tuesday 05 June 2007, Ken Restivo wrote:
On Mon, Jun 04, 2007 at 06:20:44PM -0500, Josh
Lawrence wrote:
Where can one get alsaseq2jackmidi ?
On 6/4/07, Dmitry Baikov
<dsbaikov(a)gmail.com> wrote:
I am using synths that require JACK MIDI support, such as AZR3, using the
Debian Sid binary package of the released 0.103 jackd. Haven't had any need
to compile anything.
JACK MIDI seems to work just fine in the released jackd package. I use the
alsaseq2jackmidi utility to access it. The connections show up in the
released QJackCtl, jack_lsp, and aconnect. I connect my synth to
alsaseq2jackmidi using MIDI, then connect alsaseq2jackmidi to the synth
using jack.
I'm told that yet-to-be-released SVN versions of jackd do the bridging
within itself, obviating the need for this alsaseq2jackmidi kludge, but I
haven't had any need for that yet.
On 6/4/07, carmen <_(a)whats-your.name>
wrote:
so just to make sure I understand you correctly, to get jack midi
working on my box I would need to completely uninstall the debian
version and install from source, correct? to get jackd to see your alsa midi devices, you
have to do some extra
work. namely use http://subversion.jackaudio.org/jack/branches/midi/jack
and add the -X flag to jackd initiation (i could only get raw working)
Midi driver is the the trunk already :)
http://subversion.jackaudio.org/jack/trunk
11 a.m.
Oops, I attached the current one :)
I will work only with SVN jack (and with it you don't need a bridge).
2:18 p.m.
Most of the jack_midi_... functions here need a nframes argument.
I had seen a funcion to get this from jack_get_buffer_size(_client) or from
info->nframes. Subtracted frame offsets if I knew them?
I can send you the modified sources if you want
When jack is running and I start it, I get ports created for everything that
shows in qjackctl's midi connections pane. I see nothing different in
qjackctl. If this what it should be doing and then, how do I connect them?
3:34 p.m.
On 6/5/07, David Baron <d_baron(a)012.net.il> wrote:
Most of the jack_midi_... functions here need a
nframes argument.
I had seen a funcion to get this from jack_get_buffer_size(_client) or from
info->nframes.
Right.
Subtracted frame offsets if I knew them?
Sorry,
don't understand.
I can send you the modified sources if you want
Yes, please.
When jack is running and I start it, I get ports
created for everything that
shows in qjackctl's midi connections pane. I see nothing different in
qjackctl. If this what it should be doing and then, how do I connect them?
Jack
MIDI ports do show up in qjackctl's audio pane.
You can connect them as usual (but only midi to midi).
I use patchage here, it shows ports in different colors depending on port type.
Dmitry.
4:16 p.m.
On Tuesday 05 June 2007, Dmitry Baikov wrote:
Attached zip.
Did not see them here. Qjackctl knows the jack_alsa is running because when I
stop jackd, I get messages like:
subgraph starting at alsa_midi timed out (subgraph_wait_fd=10, status = 0,
state = Triggered)
On 6/5/07, David Baron <d_baron(a)012.net.il>
wrote:
Check the sources. In one case, I start at nframes - 1 so I assume I am
looking at 1 frame. In another case, the frame_offset is calculated
explicitely--I moved this forward--so I subract from info->nframes.
Most of the jack_midi_... functions here need a
nframes argument.
I had seen a funcion to get this from jack_get_buffer_size(_client) or
from info->nframes.
Right.
Subtracted frame offsets if I knew them?
Sorry, don't understand.
I can send you
the modified sources if you want
Yes, please.
When jack is
running and I start it, I get ports created for everything
that shows in qjackctl's midi connections pane. I see nothing different
in qjackctl. If this what it should be doing and then, how do I connect
them?
Jack MIDI ports do show up in qjackctl's audio pane.
You can connect them as usual (but only midi to midi).
I use patchage here, it shows ports in different colors depending on port
type. 
4 Jun
4 Jun
6:23 a.m.
carmen <_(a)whats-your.name> writes:
On Sun Jun 03, 2007 at 09:55:15PM -0700, Kevin
Cosgrove wrote:
As alternative to svn jackd, you could use alsaseq <-> jackmidi progies
too. They are bridges between alsa midi and jack midi.
And make sure you dont use qjackctl-0.2.22 (latest ATM). It does not
list jack midi ports. You may want to consider svn patchage as GUI
patchbay. Also jack_lsp will list jack midi ports too. And jack_connect
should work on them too. IIRC both are command line progies comming with
jack itself. Patchage is at http://wiki.drobilla.net/Patchage
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
On 3 June 2007 at 23:48, "Josh
Lawrence" <hardbop200(a)gmail.com>
wrote:
no, and neither is qjackctl. how do you get it to realize jackd is
already running and therefore show the start button dimmed (so it
doesnt error out trying to launch another one). wheres the input for a
custom command string?
to get jack midi going, you can add jackmidi to your USE flags on
gentoo. im not sure how to do it on debian - i guess you just hope
they enabled midi in their binary, or compile it yourself?
to get jackd to see your alsa midi devices, you have to do some extra
work. namely use
http://subversion.jackaudio.org/jack/branches/midi/jack and add the -X
flag to jackd initiation (i could only get raw working) I just downloaded dino, and it became pretty
clear that I don't
have jack midi working. I'm running jack version 0.103.0 on
debian sid. is there a way to enable jack midi functionality to
my existing jack without having to pull the whole thing apart and
put it back together?
qjackctl has a MIDI tab. Is that of any use to you?
6171
days inactive
6172
days old
linux-audio-user@lists.linuxaudio.org
16 comments
8 participants
participants (8)
-
carmen -
David Baron -
Dmitry Baikov -
Josh Lawrence -
Ken Restivo -
Kevin Cosgrove -
Nedko Arnaudov -
Paul Davis