Re: [Jack-Devel] Installers for Jack 1.9.8 (SVN 4376) for Windows 64 and 32 bits

PrevNext  Index
DateSat, 07 May 2011 09:29:28 +0100
From Peter L Jones <[hidden] at drealm dot info>
To[hidden] at jackaudio dot org
In-Reply-ToStéphane Letz Re: [Jack-Devel] Installers for Jack 1.9.8 (SVN 4376) for Windows 64 and 32 bits
Follow-UpStéphane Letz Re: [Jack-Devel] Installers for Jack 1.9.8 (SVN 4376) for Windows 64 and 32 bits
Stéphane,

It's the subsequent repeat-until-server-killed spew of
> JackWinSemaphore::TimedWait name = jack_pipe.default_freewheel time_out
> JackFreewheelDriver::ProcessSync SuspendRefNum error
> JackAudioDriver::ProcessGraphSync: ProcessWriteSlaves error, engine may now behave abnormally!!
> JackAudioDriver::ProcessSync: process error, skip cycle...
> JackWinSemaphore::Signal name = jack_pipe.default_jack_midi_latency_test err = 6
> JackFreewheelDriver::ProcessReadSync: ResumeRefNum error
> JackAudioDriver::ProcessGraphSync: ProcessReadSlaves error, engine may now behave abnormally!!
> JackWinSemaphore::TimedWait name = jack_pipe.default_freewheel time_out
> JackFreewheelDriver::ProcessSync SuspendRefNum error
> JackAudioDriver::ProcessGraphSync: ProcessWriteSlaves error, engine may now behave abnormally!!
> JackAudioDriver::ProcessSync: process error, skip cycle...
> JackWinSemaphore::Signal name = jack_pipe.default_jack_midi_latency_test err = 6
that worries me.  Why would a simple command line error in a client cause that
in the server?

Thanks,

-- Peter


On 07/05/2011 08:20, Stéphane Letz wrote:
> 
> Le 7 mai 2011 à 00:03, Devin Anderson a écrit :
> 
>> On Fri, May 6, 2011 at 2:29 PM, Peter L Jones <[hidden]> wrote:
>>
>>> http://dino.drealm.info/peter/media/Jack1.9.8(SVN4376).7z
>>> A selection of log files:
>>> jackd-\d+-{,latency}.log - the jackd and jack_midi_latency output for varying
>>> numbers of periods: 64, 128, 512.
>>
>> Could you run the tests again with the '-v' flag?  I added a bunch of
>> debug messages to the WinMME driver regarding MIDI timing that are
>> only output when the verbose flag is set.
>>
>>> jackd-err-{,latency}.log - something odd happens to make jackd unhappy when I
>>> get the port names around the wrong way...
>>
>> Hmmm ... I'm not sure what's going on.  Stéphane may know more.
>>
>> -
> The error message is pretty clear: "Destination port in attempted (dis)connection..."
> 
> Connection in the wrong order of between port with wrong type.
> 
> Stéphane  
PrevNext  Index

1304757017.30712_0.ltw:2,a <iq2vti$pqq$1 at dough dot gmane dot org>