From: Ed Wildgoose <lists@wildgooses.com>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: rme 9632 crackling when sound > 0db
Date: Mon, 12 Apr 2004 10:21:29 +0100 [thread overview]
Message-ID: <407A5F99.4040201@wildgooses.com> (raw)
Hi, I'm running kernel 2.6.5-mm1 with built-in alsa drivers. Also, v
1.04 of the various alsa utils, etc.
I'm playing (for example) Dido - No Angel, track "Isobel", and according
to the hdspmixer tool, at the end of the track the drums have transients
that go greater than 0db, and this causes nasty metallic crackles on my
RME 9632 (tested with both Alsa and OSS interfaces). Without looking at
the code, I'm wondering if there is an overflow occuring, ie something
unsigned going into a signed value and causing this... However, it
doesn't seem that likely, for example if you turn up the middle layer of
mixer controls and then turn down the last layer of output mixer
controls then as long as the red clip light isn't on then everything is
still ok, ie the crackle isn't occuring as a result of the first layer
of software mixing, it purely seems to be something happening *after*
the last mixer control
You can also simulate this simply by turning up the mixer controls so
that normal music starts to clip. Same effect.
Two points to note, first I don't remember getting this on an alsa
snapshot from about 1-2 months ago, so I'm thinking it's a driver issue,
rather than a feature of this card? Secondly, before now I couldn't use
the card at all with many apps, I would just get constant over-runs and
other problems. So thankyou for fixing those problems!
Just a heads up, this card still doesn't work with mplayer 1.0 pre3.
The sound appears to be playing too slowly, and several times a second
there are "xruns" reported (which makes sense). I will try and rip out
the mplayer audio code and make up a test app so that I can experiment
further with this.
Thanks to everyone who has made Alsa what it is today!
Ed W
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-04-12 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 9:21 Ed Wildgoose [this message]
2004-04-12 10:07 ` rme 9632 crackling when sound > 0db Ed Wildgoose
2004-04-13 6:37 ` Joachim Deguara
2004-04-13 15:15 ` Ed Wildgoose
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=407A5F99.4040201@wildgooses.com \
--to=lists@wildgooses.com \
--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 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.