26 Sep
2010
26 Sep
'10
9:01 p.m.
On Fri, Sep 24, 2010 at 10:39:20PM -1000, Joel Roth wrote:
Hello all,
I recently upgraded my Debian 'unstable' system (I know -- a terrible
thing to do to a functioning system), including a recent
version of the "jackd" package.
jackd --version
jackdmp 1.9.6
The package contains the utility program, jack_lsp,
which I rely on and need to be able to parse.
I find the STDOUT stream is peppered with what appear to be
debugging messages from the JACK server.
Is that purposeful or a bug?
According to Adrian Knoth, under jackd2 with the -v option,
jack clients print debugging messages onto STDOUT.
$ jack_lsp
Jack: JackClient::SetupDriverSync driver sem in flush mode
Jack: JackPosixSemaphore::Connect jack_sem.1000_default_lsp
Jack: Already connected name = lsp
Jack: Clock source : system clock via clock_gettime
Jack: JackLibClient::Open name = lsp refnum = 2
system:capture_1
system:capture_2
system:playback_1
system:playback_2
[...]
--
Joel Roth