Re: [Jack-Devel] Rust Bindings

Gotcha.  Thanks for your patience, Mr. Davis. :)


The api documentation lists several callbacks which were seem to be related
to error conditions: jack_on_shutdown, jack_on_info_shutdown, and
jack_set_xrun_callback.  Regarding the first two, which conditions would
cause the Jack server to shutdown my client thread?

Xruns, as I understand it, are the result of Jack server having
insufficient time to process its entire call graph and thus result in a
loss of audio.  Does the server take any action in the event of an xrun?
 Would it, for instance, penalize a long running client thread by removing
it from the processing graph?

Thanks,
-Paul SC


On Sat, Jun 22, 2013 at 2:19 PM, Paul Davis <[hidden]>wrote:

>
>
>
> On Sat, Jun 22, 2013 at 2:14 PM, kesserich1 <[hidden]> wrote:
>
>> Hi Paul,
>>
>> Sent from my iPhone
>>
>> On Jun 22, 2013, at 1:03 PM, Paul Davis <[hidden]>
>> wrote:
>> audio delivered to h/w JACK ports should be in the range -1.0 .. +1.0 ...
>> behaviour outside that range with h/w ports is undefined (and actually this
>> is true of s/w ports also).
>>
>> Sure, that makes sense. I was just assuming that jack would somehow alert
>> my client of its improper behaviour. Does such mechanism exist(even for
>> general purpose errors) and if so what is the nescessary API call to
>> establish subscription to these notifications?
>>
>
> we don't consider it an error. clients can do whatever they wish.
>

1371941544.16019_0.ltw:2,a <CAFg+83MXYgtO0j=jx1chntEzBtq96B4rkuYqvStVG8v6SfAKCw at mail dot gmail dot com>