From owner-freebsd-current@FreeBSD.ORG Tue Apr 15 15:55:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E6B537B401 for ; Tue, 15 Apr 2003 15:55:32 -0700 (PDT) Received: from wabakimi.chat.carleton.ca (wabakimi.chat.carleton.ca [134.117.1.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68DA943FCB for ; Tue, 15 Apr 2003 15:55:31 -0700 (PDT) (envelope-from creyenga@connectmail.carleton.ca) Received: from fireball (terry.cavern.carleton.ca [134.117.93.187] (may be forged))h3FMtTWg011280; Tue, 15 Apr 2003 18:55:29 -0400 (EDT) Message-ID: <002a01c303a2$2661e140$0200000a@fireball> From: "Craig Reyenga" To: References: <200304152049.h3FKnenR064554@puma.icir.org> <3E9C72CF.7070708@ezri.org> <3E9C7472.7040500@ezri.org> Date: Tue, 15 Apr 2003 18:55:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: Re: Adjusting pcm buffersize? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2003 22:55:32 -0000 I see the problem when using ogg123 from the commandline, which writes directly to the card. My box in question is an AMD K6-2 450, SBLive. -Craig ----- Original Message ----- From: "Wade Majors" To: "Orion Hodson" Cc: Sent: Tuesday, April 15, 2003 5:06 PM Subject: Re: Adjusting pcm buffersize? > Ok, Orion Hodson is a genius. I don't know how he diagnoses this stuff > so easily. > > I have traced the problem to the esound daemon. Taking esd out of the > loop and using the OSS driver in XMMS works flawlessly under the same > situations that I was getting the underruns with esd. I switch the > output to Esound and the problems return. > > Huh. > > Since it seems not much stuff will work writing directly (or am I > mistaken?), what are my alternatives here? > > Do others seeing this problem have the same results writing directly to > the device? > > -Wade > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >