Bug 23293

Summary: newpcm/emu10k: mono playback is distorted
Product: Base System Reporter: Keith Jones <keith>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.2-STABLE   
Hardware: Any   
OS: Any   

Description Keith Jones 2000-12-05 07:20:00 UTC
When playing back any mono audio, there is a lot of "noise" (usually
crackles and pops!) No such distortion is noticed when playing stereo
sound.

Judging by feedback on the mailing lists, this problem is not limited to
the Soundblaster Live! Value card but a range of SBLive! cards, all of
which use the newpcm/emu10k1 driver.

The card functions normally in other operating systems that support it.

Fix: 

No (yet), sorry!
How-To-Repeat: 
I tested this with a considerable number of stereo and mono WAV files and
MP3 files, using 'play' and 'amp' respectively. The sound quality of the
stereo files was as expected, but the mono audio output was distorted. 

The same files have been tested under other operating systems that support
it, and this problem did not occur, which leads me to believe that it's a
driver problem.
Comment 1 iedowse freebsd_committer freebsd_triage 2001-11-18 12:31:23 UTC
State Changed
From-To: open->feedback


Does this problem still occur?
Comment 2 iedowse freebsd_committer freebsd_triage 2001-11-18 13:15:47 UTC
State Changed
From-To: feedback->closed


Mail to submitter bounces.
Comment 3 Keith Jones 2002-10-14 00:36:12 UTC
Hi,

With reference to this PR (now closed), I was the original submitter of 
this PR but it was closed because my e-mail address had changed.

It turns out that I'm still getting the odd pop and crackle with the 
current (4.7-RC) version of the newpcm/emu10k1 driver, but nowhere near 
the kind of distortion that I used to get (i.e. it's merely slightly 
irritating, as opposed to painful). I don't use this card in anger 
anymore, so it's probably safe to leave this closed unless someone else 
raises it.

Keith
Comment 4 freebsd-pr 2002-10-22 17:19:48 UTC
i still have this problem (4.7 stable/live), and find it very annoying.

i would like for it to be reopened/fixed (fix preferred).