Re: [LAU] qjackctl does not reflect state of jackd

From: Eric Steinberg <eric.steinberg@email-addr-hidden>
Date: Tue May 24 2011 - 02:12:33 EEST

Thanks, Paul. If jack had not crashed, shouldn't rotter have continued to
record? Is there any way to establish why recording was interrupted? This
happened about a week after I had started recording on this system.

On Mon, May 23, 2011 at 4:06 PM, Paul Davis <paul@email-addr-hiddenwrote:

> On Mon, May 23, 2011 at 6:56 PM, Eric Steinberg
> <eric.steinberg@email-addr-hidden> wrote:
> > Hi folks,
> > I'm trying to build an audio logger, that can record from six different
> > sources to separate files. I've been using the program rotter, and I
> > thought it was working but have discovered that jackd crashed and
> recording
> > was interrupted. Unfortunately this was not reflected by qjackctl, which
> is
> > what I use to launch jackd. The qjackctl display showed that jackd was
> > running, right down to the flashing "RT", but when I tried to launch
> > meterbridge it complained that the jack server was not running. The
> > instances of rotter that I launched were still running, but were making
> > files of just a few bytes, with no audio in them. Is this a bug in
> > qjackctl? I am using Arch, on a Pentium 4, and using a firewire
> interface
> > (Edirol FA-101).
>
> you should use:
>
> ps aux | grep jackd
>
> to establish whether jack has "crashed".
>
> my guess is that had not crashed, but was no longer accepting new
> clients and was otherwise hosed.
>

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Tue May 24 04:15:03 2011

This archive was generated by hypermail 2.1.8 : Tue May 24 2011 - 04:15:03 EEST