From: Paco <paco@OhKeePa.Net>
To: linux-sound@vger.kernel.org
Subject: Re: Reducing "noise" from output
Date: Wed, 23 Jun 1999 18:35:10 +0000 [thread overview]
Message-ID: <marc-linux-sound-93016573325640@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93007835614102@msgid-missing>
On Wed, 23 Jun 1999, Bryan Scaringe wrote:
> So: What is the difference between line-out and speaker-out,
> specificly from a functional standpoint. Is line-out expected to
> be sent to an amplifier that will control bass/treble/vol?
Exactly. For line-out, you have minimal control over the amplitude of the
signal. "Line-level" voltage is (I believe) 2.2V, peak-to-peak. Volume
control of line-out allows you to change this peak-to-peak value, but not
significantly.
Line-out signals are meant to go to another device which will control the
bass/treble/volume. (ie, your stereo)
Speaker-out signals are amplified *on-the-card* and provide enough juice
to power speakers themselves. This on-card amplification may be the cause
of your hiss. (I'm not too sure if the on-card amplifiers are very
high-quality on an AWE64.)
> Is this why line-out is less responsive to bass/treble changes
> using "aumix" than speaker-out?
BINGO! Bass and treble controls function just like the volume control for
line-out; they *do* cause changes in the signal, but not significant ones.
You can think of bass and treble controls as "turning up the volume" of
the low or high EQ bands.
regards,
Chad "Paco" Walker
next prev parent reply other threads:[~1999-06-23 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 18:54 Reducing "noise" from output Paco
1999-06-22 20:25 ` ljp
1999-06-23 15:26 ` Bryan Scaringe
1999-06-23 18:35 ` Paco [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-06-22 15:11 Bryan Scaringe
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-93016573325640@msgid-missing \
--to=paco@ohkeepa.net \
--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