Re: [Jack-Devel] JACK1 / JACK2: Application UI behaves differently

PrevNext  Index
DateWed, 01 Feb 2012 20:27:12 +0100
From Stéphane Letz <[hidden] at grame dot fr>
ToHarry van Haaren <[hidden] at gmail dot com>, Paul Davis <[hidden] at linuxaudiosystems dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-To[hidden] at gmail dot com Re: [Jack-Devel] JACK1 / JACK2: Application UI behaves differently
Follow-UpPaul Davis Re: [Jack-Devel] JACK1 / JACK2: Application UI behaves differently
Le 1 févr. 2012 à 20:13, [hidden] a écrit :

> Issue fixed: Apologies Stephane for wasting your time.
> 
> JACK1 will repeatedly call process when you return "true" from the process function.
> JACK2 will call process() *once*, and if you return "true" not call you again.

> 
> This was stopping my RT thread from inserting the relevant components into engine,
> and hence not updating the GUI, because the actions weren't being achieved.
> 
> Docs contains the following on returning from process():
> " Returns:
> zero on success, non-zero on error"
> 
> Perhaps a note that JACK1 will continue to call you, while JACK2 will not would be good?
> -Harry
> 

Well this was my understanding of how it was supposed to behave, so I implemented that way. I mean what would be otherwise the reason to return "something"?

But I may be wrong.. Paul what do you think?

Thanks.`

Stéphane 
PrevNext  Index

1328124443.12654_0.ltw:2,a <22939414-A562-4FB4-9DA6-9B73C04B909D at grame dot fr>