Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Dominik Stadler <Dominik.Stadler@apertum.de>
To: linux-sound@vger.kernel.org
Subject: AW: record overrun
Date: Wed, 09 Sep 1998 09:03:43 +0000	[thread overview]
Message-ID: <marc-linux-sound-90534379411786@msgid-missing> (raw)


Hi!

I'm not an insider in sound-driver-stuff, but as far as I know, you can
specify a certain amount of memory as DMA-Buffer (in sound-config during
kernel-configuration).

This amount of memory is used to store incoming sound until it is
written to disk.

Obviously if your hard-disk is too slow or your machine is too much
stressed, the buffer will be too small and will overrun, causing it to
be emptied and leave a crack in the sound. 

You should check if your DMA-Buffer is set to the maximum amount (I
think for 2.0.xx no more than 65536 Bytes), and try to decrease the load
of your machine during recording. If this doesn't help, your machine is
too slow for the desired sampling parameters (sampling rate, number of
channels, ..) and therefore you could decrease the quality of your
recording to avoid overruns.

Dschau.. Dominik


	-----Ursprüngliche Nachricht-----
	Von:	Karsten Patzwaldt [SMTP:kpa@gmx.net]
	Gesendet am:	Dienstag, 8. September 1998 17:16
	An:	linux-sound@vger.rutgers.edu
	Betreff:	record overrun

	hi!

	when i try to record something with my sb16, the kernel gives me
'Sound:
	Recording overrun' messages. this happens with the 'normal'
sb-driver as
	well as with the oss/free. i use linux 2.0.33, oss/free 3.8 and
a normal
	sb16. please tell me what this means, it sounds terrible when
this
	occurs...

	thanks in advance,

	--- 
	Karsten Patzwaldt             http://kpa.notrix.de
kpa@gmx.net
	                        "Wisdom is earned... not given."

                 reply	other threads:[~1998-09-09  9:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-sound-90534379411786@msgid-missing \
    --to=dominik.stadler@apertum.de \
    --cc=linux-sound@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