linuxaudio.org

--000325558cee0c52ce04a85ffdfe

Content-Type: text/plain; charset=ISO-8859-1
Hi all,
I'm trying to build an audio logger- a machine to record audio that can stay

running all the time.  I've been attempting to use Rotter and Jack for this,

but I'm getting the same problems across a variety of distros (Arch, Ubuntu,

Ubuntu Studio, CentOs &c.).  I'm using an Edirol FA-101, attached to a P4

3ghz machine with a second SATA drive as an audio recording volume.  I

launch jack, with a big period so as to avoid xruns:
jackd -v -d firewire -r 44100 -n 3 -p 4096 2> jack_stderr.log >

jack_stdout.log &
Then I launch multiple instances of Rotter, one per channel, six total:
rotter -f flac -c 1 -n channelone -d 500 -L flat -v

/secondsatadrive/channelone

.

.

.

rotter -f flac -c 1 -n channelsix -d 500 -L flat -v

/secondsatadrive/channelsix
Then I launch esjit and patch physical input one to rotter instance

channelone, etc.
This works, for a while.  Jackd still gets xruns, but the recording happens

and files are written properly.  However, after several hours and a whole

lot of xruns, it stops working.  Files are still written and named properly,

but they are only a few hundred k in size and contain no audio.  The error

logs show the xruns, but nothing else (no error messages, except for xruns).

 The output of Rotter also does not show anything wrong.  Clearly, jackd is

breaking somehow; anyone have clues?  Any way to get more info from jackd?

 What am I doing wrong?  This problem is the same across several distros

(see above), and occurs whether or not I use the -R realtime flag.
--000325558cee0c52ce04a85ffdfe

Content-Type: text/html; charset=ISO-8859-1

Content-Transfer-Encoding: quoted-printable
Hi all,I'm trying to build an audio logger- a machi=

ne to record audio that can stay running all the time. =A0I've been att=

empting to use Rotter and Jack for this, but I'm getting the same probl=

ems across a variety of distros (Arch, Ubuntu, Ubuntu Studio, CentOs &c=

.). =A0I'm using an Edirol FA-101, attached to a P4 3ghz machine with a=

 second SATA drive as an audio recording volume. =A0I launch jack, with a b=

ig period so as to avoid xruns:
jackd -v -d firewire -r 44100 -n 3 -p 4096 2> jack_stderr.log > =

jack_stdout.log &Then I launch multiple insta=

nces of Rotter, one per channel, six total:rotter=

 -f flac -c 1 -n channelone -d 500 -L flat -v /secondsatadrive/channelone

...rotter -f flac -c 1 -n channelsix =

-d 500 -L flat -v /secondsatadrive/channelsixThen=

 I launch esjit and patch physical input one to rotter instance channelone,=

 etc.

This works, for a while. =A0Jackd still gets xruns, but=

 the recording happens and files are written properly. =A0However, after se=

veral hours and a whole lot of xruns, it stops working. =A0Files are still =

written and named properly, but they are only a few hundred k in size and c=

ontain no audio. =A0The error logs show the xruns, but nothing else (no err=

or messages, except for xruns). =A0The output of Rotter also does not show =

anything wrong. =A0Clearly, jackd is breaking somehow; anyone have clues? =

=A0Any way to get more info from jackd? =A0What am I doing wrong? =A0This p=

roblem is the same across several distros (see above), and occurs whether o=

r not I use the -R realtime flag. =A0
--000325558cee0c52ce04a85ffdfe--