All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fergus Reid <fergusr@solid-state-logic.com>
To: Paul Davis <pbd@Op.Net>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Request for advice on stopping xruns
Date: Thu, 07 Mar 2002 08:20:34 +0000	[thread overview]
Message-ID: <3C8722D2.4DFE5FE4@solid-state-logic.com> (raw)
In-Reply-To: 200203061305.IAA15354@renoir.op.net


Paul Davis wrote:

> >Hi, I'm developing an 8 channel recorder based on alsa0.9.0beta10 and a
> >Terratec EWS88mt sound card.
> >I'm now using a 2.4.18 kernel with the Andrew Morton patches applied. I
> >really want to be able to record/playback at the full 96k 24bits on all
> >8 channels simultaneously, but I need absolutely no under/overruns.
> >Currently, as I try to up the bandwidth requirements I get xruns
> >occurring more and more frequently; I'm not even sure if I can guarantee
> >a maximum, before the onset of xruns, although 16bit 44.1 may well be
> >okay.
> >
> >I don't care about other system processes, so I've set the record and
> >playback threads to SCHED_FIFO prio 99 (although I don't really know if
> >this is the right thing to do!)
> >
> >Is there anything I can do/change/not do to eliminate xruns altogether?
>
> You cannot eliminate xruns altogether. xruns are caused either by OS
> scheduling delay, or by processor load. I trust that you are not
> trying to read/write from/to disk from the same thread as you are
> handling audio in ...
>
> Ardour (http://ardour.sf.net) records 24 channels with 32 bit samples
> with no xruns. Perhaps you are not familiar with this project. It uses
> JACK (http://jackit.sf.net) as its underlying audio engine, which in
> turn uses ALSA.
>
> --p

Er, actually I am doing it all in a single thread, I guess this is not a
good idea. I will
modify things and see how I go!

I looked at Ardour at the beginning of last year, and thought it looked very
good,
although I must confess I never got it to record. The JACK part doesn't ring
any
bells, I will take a look.

The reason I'm writing my own, far simpler, 8 track recorder, is because I
wanted
to do it for myself, being an ex Sound Engineer turned Computer programmer.
I did
look at the code for Ardour, but it was quite involved, and I didn't have
the time then
to get to grips with it. I actually ended up looking at how aplay works,
which is how
I've ended up with a single thread!!

Thanks,
Fergus






**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

      reply	other threads:[~2002-03-07  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06  8:50 Request for advice on stopping xruns Fergus Reid
2002-03-06  8:06 ` Paul Davis
2002-03-07  8:20   ` Fergus Reid [this message]

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=3C8722D2.4DFE5FE4@solid-state-logic.com \
    --to=fergusr@solid-state-logic.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pbd@Op.Net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.