All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: Joachim Deguara <dga@idmt.fraunhofer.de>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: rme 9632 crackling when sound > 0db
Date: Tue, 13 Apr 2004 16:15:41 +0100	[thread overview]
Message-ID: <407C041D.6040503@wildgooses.com> (raw)
In-Reply-To: <407B8AB3.2030407@idmt.fraunhofer.de>

Joachim Deguara wrote:

> The good news: you don't have a driver problem!  But it sounds like 
> you have a Wordclock problem.  Namely, your rme 9632 has a different 
> clock than your playback device (D/A) and they are not in Sync.  Check 
> the setting for who is (and should be) Wordclock Master and take 
> adjust accordingly.  You can set the mode of synchronisation for you 
> card by editing /etc/asound.state and the running "alsactl restore".


Hi, Thanks for the thought, but I don't see how this could be the 
issue?  I am reading input from the HD, writing it to the card via 
either oss or alsa, and the output is analogue to a pre-amp and then on 
to an amplifier.  The crackle only occurs when I use +4db as the output 
level, and then either find a song which clips anyway, or crank up the 
mixer so that the output clips.  It could actually be some sort of 
electrical issue at the pre-amp to be fair, it's just that I don't 
remember it happening before?  It doens't seem to be a problem if I drop 
the output level to the -10bdv setting for example.

The main thing I would prefer to debug right now anyway is why mplayer 
doesn't work with this card.  A cursory glance at the mplayer output 
code suggests that everything looks fine...  Oh well, will need to break 
out that code and study it a bit more - most other apps are working now 
though

Thanks

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

      reply	other threads:[~2004-04-13 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-12  9:21 rme 9632 crackling when sound > 0db Ed Wildgoose
2004-04-12 10:07 ` Ed Wildgoose
2004-04-13  6:37   ` Joachim Deguara
2004-04-13 15:15     ` Ed Wildgoose [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=407C041D.6040503@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dga@idmt.fraunhofer.de \
    /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.