LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: noreply@tsc.uc3m.es
To: linux-kernel@vger.kernel.org
Subject: Re: Sound artifacts in Gravis Ultrasound
Date: Fri, 05 Oct 2001 17:05:48 +0200	[thread overview]
Message-ID: <3BBDCC4C.EF9F7C49@tsc.uc3m.es> (raw)

> I have a Gravis Ultrasound sound card. I suspect kernel from
> non-continuous feed of audio
> data into the device.
> 
> When I feed directly a sine-wave data into /dev/dsp, 100Hz, 1KHz, 10kHz,
> there is
> a distortion that can be heard on 1kHz, is not heard on 100Hz and is
> very strong at 10kHz.
> It sounds like every several-per-second to several-ten-per-second, the
> data in the sound
> card are repeated (for several samples). The distortion occurs
> permanently and generates
> a regular sound, something like a car ignition system makes in board
> radio.
> 
> When I play mp3 (mpg123) or Ogg Vorbis (ogg123), it can be heard also,
> when suitable
> pattern is present in the music to make the distortion audible.
> 
> It is not caused by my amplifier (audible also in earphones), not caused
> by too
> much volume (when playing on low volume, it is also there, it's a linear
> phenomenon).
> The sound of distortion is also not added to the signal, because can not
> be heard
> when certain sound patterns appear in the music.
> 
> Is there any kernel setting that improves continuity of data feed? The
> card is
> Gravis Ultrasound Plug'n'play, on ISA.

I have the exact same problems using a Sound Blaster 128 PCI with the
es1371.

It's a linux problem because it works with Windows 98.

             reply	other threads:[~2001-10-05 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 15:05 noreply [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-05  7:03 Karel Kulhavy

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=3BBDCC4C.EF9F7C49@tsc.uc3m.es \
    --to=noreply@tsc.uc3m.es \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Sound artifacts in Gravis Ultrasound' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).