[Fluxus] Getting sound

[troels knak-nielsen]

On Wed, Jun 4, 2008 at 12:34 AM, krgn <k.gebbert at gmail.com> wrote:
> hm its difficult to tell. the way jackd is invoked here is:
>
> /usr/bin/jackd -R -P80 -dalsa -dhw:0 -r44100 -p128 -n3 -S -Xseq

This yields a slightly better result. Still some clicking noises, but
much better.

> often the reason can be the kernel is used. an rt-based kernel usually
> performs best although I recently found the stock ones already quite good
> (they are merging a lot of the rt-patches into the main linux source tree).

I'd rather not have to change my kernel for this to work. Is that
really nescesary?

> other than that I'd try *not* using full duplex (i.e. switch off hw inputs)
> and larger period sizes, although that will increase latencies.

How would I go about that? I see some options in the settings menu of
qjackctl, but those seems to be the same options that are sent to
jackd as commandline options. Wouldn't those take precedence?

> to connect audio applications with each other click the 'Connect' button in
> qjackctl (I never really used the pachbay) and drag sources from the left
> panel to the right-hand panel, the destinations (where the fluxus client
> will show up)

hm ... I tried the following:

start jackd (With the options from above)

start qjackctl. Open connect menu.

I can now see the following, in the "output ports" panel:
system
  capture_1
  capture_2

Start audacious. Play a tune.

The "output ports" panel now contains:
audacious-jack_19568_000
  out_0
  out_1
system
  capture_1
  capture_2

I select capture_1 and press "connect", and lines appear, going from
out_0/out_1 to the right hand side "input ports":
system
  playback_1
  playback_2

... and back to capture_1

I suppose that is fine?

Then I start fluxus, and punch in:
(start-audio "alsa_pcm:capture_1" 128 44100)

... which gives the following output in the shell:

$ fluxus
SSE2 detected
Welcome to fluxus.
Type (help) for info.
cannot complete execution of the processing graph (Resource
temporarily unavailable)
zombified - calling shutdown handler
Shutdown

Finally, when I close fluxus, jackd dies, with:

**** alsa_pcm: xrun of at least 0.038 msecs

subgraph starting at audacious-jack_20228_000 timed out
(subgraph_wait_fd=12, status = 0, state = Running)
jack main caught signal 15
cannot read event response from client [qjackctl] (Connection reset by peer)
cannot send event to client [qjackctl] (Broken pipe)
cannot send event to client [qjackctl] (Broken pipe)
no message buffer overruns


--
troels