From owner-freebsd-current Sun Jan 9 4:15:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 2B7D214E9C for ; Sun, 9 Jan 2000 04:15:27 -0800 (PST) (envelope-from ian@niw.com.au) Received: by rose.niw.com.au (Postfix, from userid 1000) id B94DB62E4E; Sun, 9 Jan 2000 22:45:01 +1030 (CST) Date: Sun, 9 Jan 2000 22:45:01 +1030 From: Ian West To: current@freebsd.org Subject: Re: ESS 1868 and DSP_BUFFSIZE Message-ID: <20000109224500.B94641@rose.niw.com.au> References: <38786E0E.D0216628@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <38786E0E.D0216628@cvzoom.net>; from Donn Miller on Sun, Jan 09, 2000 at 06:16:30AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 09, 2000 at 06:16:30AM -0500, Donn Miller wrote: > It looks like the ESS 1868 is working OK now with the DSP_BUFFSIZE set > to 8192. Before, it wouldn't work unless I set this value to (65536 - > 256), which was the original value, I believe. So, why does the ESS > work OK now with a buffer size of 8192? And how is this buffersize an > advantage over (65536 - 256)? > > Everything seems to be working great for the ESS 1868 now, but I was > just wondering... > While it is much better than it was (sound happens, and the machine doesn't reboot :-), I am still seeing a repeat of the last few seconds of some audio with the ESS 1869 chipset. This seems to occur using waveplay (.wav files) and au files (cat *.au > /dev/dsp). I can't pick any pattern to it, although it is consistent on a per file basis. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message