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

PrevNext  Index
DateTue, 01 May 2012 09:17:47 +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>
CcJack Developers <[hidden] at lists dot jackaudio dot org>
In-Reply-ToStéphane Letz Re: [Jack-Devel] Windows: Problem running Jack Server and Clients with DLLs
Le 1 mai 2012 à 08:45, Stéphane Letz a écrit :

> 
> Le 30 avr. 2012 à 23:08, Sprague, Christopher M CIV NAVAIR, Code 4.6.2.3 a écrit :
> 
>> I Don't think what I am doing is an "In Server" client.
> 
> Your are actually creating 2 "in server" clients, since you're linking the code with libjackserver.dll (and not libjack.dll). But this should not be a problem.
> 
>> 
>> Attached is a test program where I just threw all the parts of the process into a console app.
>> With this test program, the problem is still there.  
>> 
>> I create the server. Then I create a client and register its ports and process callback with the server. I sleep for 5 seconds so you can see the process callback happening.
>> 
>> Then I try to create another client by another name for the purpose of making connections.  After I call jack_client_open()...the problems arise  
>> 
>> Because my process callback is printing "." this is what I see:
>> 
>> .................................................JackWinSemaphore::TimedWait name = jack_pipe.default_freewheel time_out
>> JackFreewheelDriver::ProcessSync SuspendRefNum error
>> JackAudioDriver::ProcessGraphSync: ProcessWriteSlaves error, engine may now behave abnormally!!
>> 
>> And that repeats indefinitely but since the callback isn't being called anymore, no more periods.
>> 
>> Also, if I create the server and make connections this way, but run my client as a separate process, things work just fine.  
>> 
>> 
>> Thanks,
>> 
>> Chris
>> 
> 
> OK, so there is a real issue here. I'll try to reproduce the problem ASAP but not this week, and possibly even not the next one since we are moving to another place.....
> 
> Stéphane 
> 

Works normally here on OSX, so I guess this is a Windows specific issue. More next week.

Stéphane 
PrevNext  Index

1335856681.31019_0.ltw:2,a <00A23536-319A-41D9-A068-47B3A1E66268 at grame dot fr>