Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Bryan Scaringe <bscaring@slpmbo.ed.ray.com>
To: linux-sound@vger.kernel.org
Subject: Re: Reducing "noise" from output
Date: Wed, 23 Jun 1999 15:26:22 +0000	[thread overview]
Message-ID: <marc-linux-sound-93015477913292@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93007835614102@msgid-missing>

Yep. The hiss is gone using line-out.  I guess this next question may be
a bit off topic, but here goes:

speaker-out is considerably louder at a given volume level than
line-out.  speaker-out also seems to have better quality bass.
line-out however, seems to be much cleaner, lacking the hiss.
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?
Is this why line-out is less responsive to bass/treble changes
using "aumix" than speaker-out?

Thanks,
	Bryan
 


> 
> Hi, Bryan.
> 
> I wanted to ask you what kernel/distribution/drivers you are using.  I
> also have the AWE64 in my box, but I have no problems with hiss.  I *do*
> use the line-out instead of the speaker-out, so that may have something to
> do with it, but it seems unlikely.
> 
> -Paco
> 
> On Tue, 22 Jun 1999, Bryan Scaringe wrote:
> 
> > Hello all,
> > 	I have a SB-AWE64, and it works fine under Linux, but I was
> > wondering if there is any way to reduce the noise from the speaker-output.
> > It sounds like a tape hiss, only less so.
> > 
> > Thanks,
> > 	Bryan
> > 
> 
> 

  parent reply	other threads:[~1999-06-23 15:26 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 [this message]
1999-06-23 18:35 ` Paco
  -- 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-93015477913292@msgid-missing \
    --to=bscaring@slpmbo.ed.ray.com \
    --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