The problem is that I sometimes get static instead of normal sound when I play sound files with one of the following applications compiled from the ports tree: - mpg123 - amp - pcmplay (comes with tosha) - waveplay If I control-C out of the sound file once the static starts, and then start it again, usually I don't get any static. I think in general, this happens 1 in 10 or 20 times I try to play a sound file. For what it's worth, both Voxware (after Amancio hacked on it for a while) and Luigi's pcm code didn't behave like this, This has been a problem since the newpcm introduction. Sometimes, after I've gotten static while playing a sound file, I hear a hissing sound in either the left or right channel from subsequent sound files. There are only two ways I know of to "fix" that behavior: - reboot the box - keep cranking up sound player programs and ^C out of them until I get another round of static. Usually this will take care of the problem. Recompiling the applications and/or updating to newer versions doesn't help. Also, this can happen with any sound file I've tried. Most of the sound files I'm using are 16bit, 44KHz stereo. Let me know if more information is needed. Fix: If I knew, this wouldn't be a problem. :) How-To-Repeat: See above.
Responsible Changed From-To: freebsd-bugs->cg Over to the maintainer.
State Changed From-To: open->feedback Is this still a problem with more recent sources?
Responsible Changed From-To: cg->greid I'll handle feedback
State Changed From-To: feedback->closed Feedback timeout
State Changed From-To: closed->feedback Re-opening this, putting this in feedback. I actually sent feedback to greid and cg, but never got a response. I just didn't CC it to freebsd-gnats-submit.
[ Re-sending the original message I sent on this back in July ] On Thu, Jul 12, 2001 at 18:25:48 -0700, greid@FreeBSD.org wrote: > Synopsis: random static with GUS PnP > > State-Changed-From-To: open->feedback > State-Changed-By: greid > State-Changed-When: Thu Jul 12 18:25:20 PDT 2001 > State-Changed-Why: > Is this still a problem with more recent sources? > > > Responsible-Changed-From-To: cg->greid > Responsible-Changed-By: greid > Responsible-Changed-When: Thu Jul 12 18:25:20 PDT 2001 > Responsible-Changed-Why: > I'll handle feedback > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17542 It was still a problem as of August, 2000. I haven't upgraded the version of -current on that machine since. (It's an SMP box, and my main mail gateway. :) To try it out with a more recent -current I'd have to move it to a different machine. If you really want more feedback, I may be able to move it this weekend. Before I spend time doing that, it might be good to get some idea from Cameron whether he thinks this might have been fixed. The last significant change to the GUS driver was in July 2000. It has been broken since newpcm was introduced in 1999. Ken -- Kenneth Merry ken@kdm.org
On Wed, Sep 12, 2001 at 09:21:12 -0700, ken@FreeBSD.org wrote: > Synopsis: random static with GUS PnP > > State-Changed-From-To: closed->feedback > State-Changed-By: ken > State-Changed-When: Wed Sep 12 09:20:28 PDT 2001 > State-Changed-Why: > Re-opening this, putting this in feedback. I actually sent feedback to > greid and cg, but never got a response. I just didn't CC it to > freebsd-gnats-submit. FYI, this is still a problem in -stable as of September 21st. Ken -- Kenneth Merry ken@kdm.org
State Changed From-To: feedback->open
State Changed From-To: open->feedback Is this still a problem with modern versions of FreeBSD?
On Wed, Apr 05, 2006 at 04:31:18 +0000, Mark Linimon wrote: > Synopsis: [sound] random static with GUS PnP > > State-Changed-From-To: open->feedback > State-Changed-By: linimon > State-Changed-When: Wed Apr 5 04:31:11 UTC 2006 > State-Changed-Why: > Is this still a problem with modern versions of FreeBSD? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=17542 I haven't tried it in years, probably since the last feedback I sent in September 2001. :) Ken -- Kenneth Merry ken@kdm.org
State Changed From-To: feedback->closed It's been so long since this PR came in (and since the submitter tried it) that this PR is just stale and should be closed.