[linux-audio-user] jackd acts weird

[Martin Wohlleben]

Hello,

I tried kluppe on current realtime-audio setups and it didn't work fine 
anymore (one year ago on SuSE 9.1 it was running on the same 
computer/souncard config at smallest available buffersizes without any 
problems) 
Now, the only possibility to get it working with jack is to increase the 
buffer size to 1024 samples or more. 
You should check if kluppe is still conncted to jack after starting  (e.g. 
with qjackctl - if it's still connected after start-up you should see 
kluppe's channels).
I tried kluppe under Agnula-Demudi and Gentoo with rt-patched kernels and 
rt-privileges, so it seems to be a problem of kluppe or some other new 
libraries used by it. 
Jackd seems to run ok, because other apps like ardour, sooperlooper, jamin or 
Rosegarden are still running fine at small buffers (64-128 samples).
I didn't use terminatorX yet, so I can't say if it is the same for me.

regards
Martin 

Am Freitag 25 August 2006 17:08 schrieb eun.sung:
> hi list
>
> on a new system, i can't understand what happens with jack
>
> i can launch jackd - seems to work normally - create some connections
> with terminatorX for example
>
> but when i "power" on terminatorX - the same thing happens with kluppe
> (haven't tried yet with other apps) - the audio file doesn't get read at
> all although it gets read when i use the app with a direct ALSA output
>
> i tried both stable and svn versions of jack and run that all on a
> 2.6.17.11-molnar's patched kernel
>
> do you have an idea about what happens here?
>
> thanks
> greetings