[LAU] JACK MIDI - where? how?

[David Baron]

On Tuesday 05 June 2007, Dmitry Baikov wrote:
> On 6/5/07, David Baron <d_baron at 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.
>
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. 

> > I can send you the modified sources if you want
>
> Yes, please.
>
Attached zip.

> > 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.
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)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jack_alsamidi-0.5_(2007-06-05_21-07-39).zip
Type: application/x-zip
Size: 55269 bytes
Desc: not available
Url : http://lists.linuxaudio.org/pipermail/linux-audio-user/attachments/20070605/25d08e90/attachment.bin