Re: [Jack-Devel] Windows: Problem running Jack Server and Clients with DLLs

PrevNext  Index
DateMon, 30 Apr 2012 20:45:59 +0200
From Stéphane Letz <[hidden] at grame dot fr>
To"Sprague, Christopher M CIV NAVAIR, Code 4 dot 6 dot 2 dot 3" <[hidden] at navy dot mil>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToSprague, Christopher M CIV NAVAIR, Code 4 dot 6 dot 2 dot 3 [Jack-Devel] Windows: Problem running Jack Server and Clients with DLLs
Follow-UpSprague, Christopher M CIV NAVAIR, Code 4 dot 6 dot 2 dot 3 Re: [Jack-Devel] Windows: Problem running Jack Server and Clients with DLLs
Le 30 avr. 2012 à 19:24, Sprague, Christopher M CIV NAVAIR, Code 4.6.2.3 a écrit :

> I have two DLLs. 
> 
> 1) which uses the JACK Control API to setup and start the JACK server
> and make / break connections
> 
> 2) an implementation of a JACK Client that does some processing 
> 
> When I use the DLL's from a launcher application, everything seems to
> work fine until I make connections...(i.e. when I call jack_activate()
> from my Server DLL to activate a client I created to make connections)
> 
> JACK server DLL spawns a thread that sets up the server, creates, and
> starts it. Then spins on jackctl_wait_signals(signal)
> 
> The Client DLL registers itself with the server, registers the process
> callback, defines ports, activates etc...
> 
> At that point things work as expected.  The client callback is being
> called by the Jack Server and it all looks good. 
> 
> Now...In order to make connections, My Jack Server DLL creates a client
> called "jack_connnect" and when jack_activate(client) is called things
> start going wrong.  The DSP load jumps to 75% and the process callback
> in the client starts getting skipped. I discovered that if ANY other
> client calls jack_activate() this happens.

So you basically create a "in server" client right?

Described behaviour looks like a thread priority issue..

Do you have any test code that shows the problem that you could share?

Thanks.

Stéphane 
PrevNext  Index

1335811574.3569_0.ltw:2,a <BED14F78-8221-481D-AF44-7978FE81A923 at grame dot fr>