Hi again, I'm back with this callback problem
quick summary: a jack client have to set a callback so the jack server can call
it when the client is supposed to do something. Here, the callback call is
supposed to trigger some scheme code execution.
Today I tried a different approach: writing the
2011/3/31 Tomtom :
> [...]
> quick summary: a jack client have to set a callback so the jack
> server can call it when the client is supposed to do
> something. Here, the callback call is supposed to trigger some
> scheme code execution.
> [...]
Hello,
the problem is that callbacks only work if t
Hi,
Thomas Chust writes:
> Your only option in the out of luck situation is not to use regular
> callbacks at all but to implement a sort of in-process remote
> procedure call system where a C stub registered as a callback
> transfers call information to a Scheme thread, waits for a reply from
>
2011/3/31 Moritz Heidkamp :
> Hi,
>
> Thomas Chust writes:
>> Your only option in the out of luck situation is not to use regular
>> callbacks at all but to implement a sort of in-process remote
>> procedure call system where a C stub registered as a callback
>> transfers call information to a Sch
thank you for your very interesting answer!
I'm currently investigating the problem from another angle: there seems to be a
"non-callback API" within the JACK API! I'll see if it solves the problem.
Tom
Excerpts from Thomas Chust's message of jeu. mars 31 14:06:15 +0200 2011:
> 2011/3/31 Tomtom
