From: Avuton Olrich <avuton@gmail.com>
To: Patrick McFarland <diablod3@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Overruns are killing my recordings.
Date: Thu, 27 Oct 2005 12:57:50 -0700 [thread overview]
Message-ID: <3aa654a40510271257t62d2fd82n5f2bcbcae2bcba9d@mail.gmail.com> (raw)
In-Reply-To: <200510271528.28919.diablod3@gmail.com>
On 10/27/05, Patrick McFarland <diablod3@gmail.com> wrote:
> On Thursday 27 October 2005 03:12 pm, you wrote:
> > Hello,
> >
> > I've been plagued by overruns, I know it's probably linux device
> > driver issues, but wanted to see if anyone could possibly help me find
> > the heart of the issue:
> >
> > I have ecasound output (at bottom) to show that it's getting
> > interrupted for up to 6 seconds, and all I really need to know is how
> > I figure out what the problem device driver is, so I can file a more
> > specific bug.
>
> I don't know if ecasound uses jack or not, but jack should be set to use
> realtime mode. Without realtime, kiss sane low latency auto-input/output
> goodbye.
ecasound utilizes jack if it's on, which I don't really need so I
don't run it, but it is taking advantage of SCHED_FIFO. But truely
this is not what I'm trying to get to. I have something in this
computer that is interrupting everything +/- 6 seconds and I'd like to
find out what it is, I'm really just not sure the best way to find out
what the 'offender' is.
thanks,
avuton
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2005-10-27 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 19:12 Avuton Olrich
[not found] ` <200510271528.28919.diablod3@gmail.com>
2005-10-27 19:57 ` Avuton Olrich [this message]
2005-10-27 21:06 ` Lee Revell
2005-10-28 0:00 ` Avuton Olrich
2005-10-28 3:40 ` Lee Revell
2005-10-28 14:52 ` Mark Knecht
2005-10-28 18:43 ` Lee Revell
2005-10-28 18:55 ` Mark Knecht
2005-10-28 21:15 ` William Weston
2005-10-28 23:07 ` Mark Knecht
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=3aa654a40510271257t62d2fd82n5f2bcbcae2bcba9d@mail.gmail.com \
--to=avuton@gmail.com \
--cc=diablod3@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome