Date: Thu, 15 Jun 2000 12:51:57 -0700 From: David Bushong <david@bushong.net> To: freebsd-stable@FreeBSD.ORG Subject: esound borken (was: crunchy sound with newpcm) Message-ID: <20000615125157.U79778@bushong.net> In-Reply-To: <Pine.BSF.4.21.0006151526070.9492-100000@epsilon.lucida.qc.ca>; from matt@ARPA.MAIL.NET on Thu, Jun 15, 2000 at 03:26:36PM -0400 References: <20000615122227.T79778@bushong.net> <Pine.BSF.4.21.0006151526070.9492-100000@epsilon.lucida.qc.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Ah hah. It seems to be just esd (esound). What tricked me was that mpg123 crunches even when I'm not running esd, so it must be secretly using its routines or something (not sure how that works). xmms works fine when you use its OSS driver instead of the esound one, and auplay and the other NAS utils work fine. esdplay on anything is crunch. So now the question is, what's wrong with esound? I really liked the functionality. On Thu, Jun 15, 2000 at 03:26:36PM -0400, Matt Heckaman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > If you're using something like XMMS or anything that uses a mixer - turn > it off. I had this exact same problem with winamp until I turned off the > mixer feature which does not like to work over here. > > Matt > > On Thu, 15 Jun 2000, David Bushong wrote: > > : Date: Thu, 15 Jun 2000 15:22:27 -0400 > : From: David Bushong <david@bushong.net> > : To: freebsd-stable@freebsd.org > : Subject: crunchy sound with newpcm > : > : My coworker had this problem about a month before I did, and now the same > : thing's happened to me: > : > : At some indeterminate point (for both of us, it was after a crash or a reboot > : or some other event, NOT immediately after a new -STABLE build), sound > : coming out (mp3s, regular wavs, anything going to /dev/dsp) comes out sounding > : crunchy and garbled. I just have > : > : device pcm > : > : in my config file, /dev/sndstat says: > : > : FreeBSD Audio Driver (newpcm) Jun 9 2000 12:35:40 > : Installed devices: > : pcm0: <Yamaha OPL-SAx> at io 0x530 irq 5 drq 0:1 (1p/1r channels duplex) > : > : and the dmesg says: > : > : pcm0: <Yamaha OPL-SAx> at port 0x220-0x22f,0x530-0x537,0x388-0x38f,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 > : unknown0: <OPL3-SA3 Snd System> at port 0x201 on isa0 > : > : (and all of those ranges, irq, and drqs check out in windows). It's actually > : an onboard sound chip on a Dell Dimension XPS D266, and (as always), it > : "used to work just fine". > : > : Anyone else seen this? Any thoughts? I've loved the newpcm driver for its > : simple one line, no options configuration, but now I feel helpless without > : settings to fiddle with ;) > : > : --David Bushong > : > : > : To Unsubscribe: send mail to majordomo@FreeBSD.org > : with "unsubscribe freebsd-stable" in the body of the message > : > > Matt Heckaman > matt@arpa.mail.net > http://www.lucida.qc.ca > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.1 (FreeBSD) > Comment: http://www.lucida.qc.ca/pgp > > iD8DBQE5SS3vdMMtMcA1U5ARAqFJAJ4orc8e/06i3z0DTNgVOcroy5rKcwCfeAqh > aslqAcWGuJTP3mcnyxAQSAg= > =9Y4f > -----END PGP SIGNATURE----- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000615125157.U79778>