From: Pete <peterpion@yahoo.com>
To: John Rigg <aldev@sound-man.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: Xrun stack trace for 1010LT
Date: Fri, 5 Dec 2008 07:20:27 -0800 (PST) [thread overview]
Message-ID: <227999.32830.qm@web65402.mail.ac4.yahoo.com> (raw)
In-Reply-To: <20081205151709.GA3160@localhost>
John thanks,
I spoke to you about 2 weeks ago about this and have been trying the various tweaks you suggested. But so far I have found no configs which have worked flawlessly, although one config had it down to about one xrun every 20 mins or so average.
Thing is I am after capturing live gigs, which you dont get a second chance with. Although I suspect a small xrun would be easy to disguise but its not ideal. So I am trying to hunt down the elusive 'perfection' config.
Its interesting that when I comment out the actual write call in arecord, there are no xruns. Tonight I will try the exact config you mention below. I suspect that the problem I am getting might be related to the hardware I am on though, which does not have much in the way of configurable bios. Perhaps something should be turned off which I can not access through this basic bios.
Anyway on discovering the stack trace system it was obvious that I must get it working so if it works under a non RT kernel thats where I will go next. Although it would be nice if someone could tell me a tool which would work with the RT kernel as it does interest me what could be screwing up this supposedly real time system, just from a technical interest point of view.
John Rigg <aldev@sound-man.co.uk> wrote: On Fri, Dec 05, 2008 at 06:48:43AM -0800, Pete cat wrote:
> I understand. Im only a fairly basic C coder and such, so could you
> recommend a tool which is fairly easy to use? Or would it be better
> to revert to a non RT kernel (there did not seem to be much improvement
> when I moved to the RT kernel)?
FWIW I've never been able to run an RT-patched kernel with pcm_multi.
I've been using a non-rt preempt SMP kernel with three Delta 1010s for
about three years now without too many problems, currently with
alsa-lib-1.0.16 and 2.6.25.x kernel.
John
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2008-12-05 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 14:18 Xrun stack trace for 1010LT Pete cat
2008-12-05 14:26 ` Takashi Iwai
2008-12-05 14:48 ` Pete cat
2008-12-05 15:17 ` John Rigg
2008-12-05 15:20 ` Pete [this message]
2008-12-05 15:23 ` Pete
2008-12-05 16:02 ` John Rigg
2008-12-05 16:11 ` Pete
2008-12-05 19:41 ` John Rigg
2008-12-05 21:39 ` Pete
2008-12-06 14:46 ` John Rigg
2008-12-15 15:23 ` Pete
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=227999.32830.qm@web65402.mail.ac4.yahoo.com \
--to=peterpion@yahoo.com \
--cc=aldev@sound-man.co.uk \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox