On Sun Jun 03, 2007 at 09:55:15PM -0700, Kevin Cosgrove 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)

carmen &lt;_(a)whats-your.name&gt; writes: 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 Mon, 2007-06-04 at 12:04 +0400, Dmitry Baikov wrote: agreed, wholeheartedly. please svn remove it ...

On Mon Jun 04, 2007 at 06:20:44PM -0500, Josh Lawrence 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)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Jun 04, 2007 at 06:20:44PM -0500, Josh Lawrence 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/5/07, David Baron &lt;d_baron(a)012.net.il&gt; wrote: If you wait a little bit (several hours), I will post current version to the site (and/or to the list) when I get home. It needs minor fixes to work with pre-SVN jack. Dmitry.

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?

On Tuesday 05 June 2007, Dmitry Baikov 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. 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)