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

PrevNext  Index
DateMon, 18 Apr 2011 10:24:34 +0200
From Stéphane Letz <[hidden] at grame dot fr>
ToNedko Arnaudov <[hidden] at arnaudov dot name>
CcJack devel <[hidden] at lists dot jackaudio dot org>
In-Reply-ToNedko Arnaudov Re: [Jack-Devel] Call for testing of MIDI Drivers in JACK 2
Follow-UpPaul Davis Re: [Jack-Devel] Call for testing of MIDI Drivers in JACK 2
Le 18 avr. 2011 à 10:14, Nedko Arnaudov a écrit :

>>> 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,

I think this is sill the case in jack1 since jack1 uses one thread for all on client side.

Stéphane 
PrevNext  Index

1303115092.23709_0.ltw:2,a <CDBB8A6C-003A-45F8-8E84-06659D4A9969 at grame dot fr>