Bug 11143 – sound gets tinny...

Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours

Bug 11143 - sound gets tinny...

Summary:	sound gets tinny...

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	esound (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-05-01 09:49 EDT by kevin lyda
Modified:	2014-03-16 22:13 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-05-08 10:54:30 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description kevin lyda 2000-05-01 09:49:17 EDT

ok, first my setup:

a compaq presario 305 (laptop) using the maestro sound driver
(maestro-20000128) and a 2.2.14 kernel.

i can't figure out how to reproduce this, but it frequently happens when
starting and stopping something like xmms, or other sound apps.  after that
the sound is tinny to a point that's almost painful (and i'm not some
psycho audiophile).  i discovered to day that doing this will reset it:

esdctl off
***pause about 3 seconds***
esdctl on

don't know if you can fix this, and i honestly don't know what to do to
give you more info to fix it.  maybe it's the maestro driver, maybe it's
this laptop.  but the fact that starting and stopping esd seems like there
might be something esd is doing when the audio stream starts and stops?

Comment 1 Brown, Zach 2000-05-02 09:50:59 EDT

There are plenty of weird bug reports like this that are pointing at race
conditions in the hardware around updating the APUs in the maestro driver.
the APUS are a bank of logical voices that are mixed into the output.  They're
controlled by a bank of memory.. there appears to be a race between the hardware
accessing this memory and the driver altering it.

At least, thats my guess.  No docs on the maestro, remember.  This would explain
lots of completely odd sound artifacts people are getting that could be
explained by improper apu settings that seem to crop up under heavy apu
modification.  (lots of ioctls setting the speed, lots of start/stop traffic,
etc.)

but I don't have maestro hardware anymore.

sigh.

Note You need to log in before you can comment on or make changes to this bug.