Re: [LAU] jack weirdness, and -verbose doesn't help

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Gabriel Beddingfield <gabrbedd@...>
Cc: <linux-audio-user@...>
Date: Tuesday, July 19, 2011 - 1:06 am

--0015174a0a8421537604a861b978
Content-Type: text/plain; charset=ISO-8859-1

Interesting, but it's more like 48-72 hours, and sometimes as much as 100
hours before recordings start to break. Others (Roberto, Lieven) on this
list have mentioned integer overflow as a possible culprit, but I've been
pretty consistent in the way I've set up recording, and the time-to-break is
not consistent, i.e. it will sometimes go 4 or 5 days before breaking. What
is consistent is that there will be many xruns and then things will break.
I have not done hdparm on the disk used for recording, and I am not
currently using an RT kernel (although I have used the Ubuntu Studio distro,
with the same results as above).

On Mon, Jul 18, 2011 at 5:49 PM, Gabriel Beddingfield wrote:

> On 07/18/2011 06:02 PM, Eric Steinberg wrote:

--0015174a0a8421537604a861b978
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Interesting, but it's more like 48-72 hours, and sometimes as much as 1=
00 hours before recordings start to break. =A0Others (Roberto, Lieven) on t=
his list have mentioned integer overflow as a possible culprit, but I'v=
e been pretty consistent in the way I've set up recording, and the time=
-to-break is not consistent, i.e. it will sometimes go 4 or 5 days before b=
reaking. =A0What is consistent is that there will be many xruns and then th=
ings will break. =A0I have not done hdparm on the disk used for recording, =
and I am not currently using an RT kernel (although I have used the Ubuntu =
Studio distro, with the same results as above). =A0
On Mon, Jul 18, 2011 at 5:49 PM, Gabriel Bed=
dingfield <gabrbedd@gmail.com> wrote:

On 07/18/2011 06:02 PM, Eric Steinberg =
wrote:

jackd -v -d firewire -r 44100 -n 3 -p 4096 2> jack_stderr.log >
jack_stdout.log &

Snip...

This works, for a while. =A0Jackd still gets xruns, but the recording
happens and files are written properly. =A0However, after several hours
and a whole lot of xruns, it stops working. =A0Files are still written and<=
br>
named properly, but they are only a few hundred k in size and contain no
audio. =A0The error logs show the xruns, but nothing else (no error

How many hours? =A0Is it a regular number?

What happens when jack_frame_time() overflows? (jack_nframes_t, 32-bit unsi=
gned) =A0At 44.1k this would be about 27 hours.

-gabriel
_______________________________________________
Linux-audio-user mailing list
=
Linux-audio-user@lists.linuxaudio.org

http://lists.linuxaudio.org/listinfo/linux-audio-user

--0015174a0a8421537604a861b978--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] jack weirdness, and -verbose doesn't help, Eric Steinberg, (Mon Jul 18, 11:02 pm)
Re: [LAU] jack weirdness, and -verbose doesn't help, Gabriel Beddingfield, (Tue Jul 19, 12:49 am)
Re: [LAU] jack weirdness, and -verbose doesn't help, Eric Steinberg, (Tue Jul 19, 1:06 am)
Re: [LAU] jack weirdness, and -verbose doesn't help, Paul Davis, (Tue Jul 19, 2:48 am)
Re: [LAU] jack weirdness, and -verbose doesn't help, Erik de Castro Lopo, (Tue Jul 19, 3:22 am)
Re: [LAU] jack weirdness, and -verbose doesn't help, Eric Steinberg, (Tue Jul 19, 3:01 am)
Re: [LAU] jack weirdness, and -verbose doesn't help, Bob van der Poel, (Mon Jul 18, 11:27 pm)
Re: [LAU] jack weirdness, and -verbose doesn't help, Eric Steinberg, (Tue Jul 19, 2:48 am)
Re: [LAU] jack weirdness, and -verbose doesn't help, Eric Steinberg, (Mon Jul 18, 11:44 pm)