Hi Nick,
I'm forwarding this to you in the hopes that you can shed some light on a
problem I've been having with Rotter. I am trying to build a system that is
stable for long-term use, i.e. I want to leave it running. I've observed
that after some time (a few days or so), Rotter will continue to run but
will not record audio, instead creating files of about 1K in size. Can you
tell me how I might troubleshoot this? Thanks!
---------- Forwarded message ----------
From: Eric Steinberg <eric.steinberg(a)gmail.com>
Date: Mon, May 23, 2011 at 4:12 PM
Subject: Re: [LAU] qjackctl does not reflect state of jackd
To: Paul Davis <paul(a)linuxaudiosystems.com>
Cc: linux-audio-user(a)lists.linuxaudio.org
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(a)linuxaudiosystems.com>wrote;wrote:
On Mon, May 23, 2011 at 6:56 PM, Eric Steinberg
<eric.steinberg(a)gmail.com> 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.