From owner-freebsd-current Sun Jun 20 10:41:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id E2BEF14F05 for ; Sun, 20 Jun 1999 10:41:46 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id TAA28690 for freebsd-current@freebsd.org; Sun, 20 Jun 1999 19:41:45 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m10vlFF-000WyXC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Sun, 20 Jun 1999 19:19:01 +0200 (CEST) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: audio-Device gone mute Date: 20 Jun 1999 19:18:58 +0200 Message-ID: <7kj7q2$qoo$1@mips.rhein-neckar.de> References: <199906201457.QAA29227@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: > Did you check (with fstat or lsof) if there's still > another process which has the audio device open? Yes I did, and no there isn't. > (Maybe some pcmplay process gone wild... Although > in that case it shouldn't block, but rather print > "device busy" or something like that.) Well, the blocking thing is peculiar. "buffer -S1024 /dev/audio" writes 120kB into /dev/audio, then it blocks. (buffer was the first thing that came to mind that can output how much data it has copied.) When I call it again, it blocks immediately. Now, if I start mpg123 and subsequently call buffer again, I can again write 120kB to /dev/audio before it blocks. So mpg123 seems to perform some kind of partial reset. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de >H Deutsche Transhumanismus-Mailingliste echo 'subscribe trans-de' | mail majordomo@lists.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message