Re: [Jack-Devel] Call for testing of MIDI Drivers in JACK 2

PrevNext  Index
DateMon, 18 Apr 2011 11:14:13 +0300
From Nedko Arnaudov <[hidden] at arnaudov dot name>
ToDevin Anderson <[hidden] at charityfinders dot com>
CcJack devel <[hidden] at lists dot jackaudio dot org>
In-Reply-ToDevin Anderson Re: [Jack-Devel] Call for testing of MIDI Drivers in JACK 2
Follow-UpStéphane Letz Re: [Jack-Devel] Call for testing of MIDI Drivers in JACK 2
Follow-UpDevin Anderson Re: [Jack-Devel] Call for testing of MIDI Drivers in JACK 2
>> I'd be happy if jack_midi_latency_test had an option for disabling the
>> autoconnect behaviour. Instead, the test could be started when both
>> ports are connected. What do you think about this idea?
>
> I think that's a great idea.  I'm actually nearly done doing that now,
> though I may go to sleep before pushing the code.

Great! Please let me know when you publish it. I'd like to setup a
ladish studio for measuring midi and audio (via jack_iodelay)
latency/jitter.

> Question: Is the callback function set via
> 'jack_set_port_connect_callback' supposed to be realtime safe?  I
> can't find the answer in the JACK documentation.

For jack2 you can sleep in the connect callback. I'm not sure for latest
jack1. I know for sure that older versions of jack1 required rt-safe
connect callback. I think this is not the case anymore but i'm not sure
if this improvement is in jack1, tscack or both.

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
PrevNext  Index

1303114450.22334_0.ltw:2,a <87ei50ht7u.fsf at usbix dot spacelabs dot org>