* Jacob Meuser <[email protected]> [081223 15:30]:
Date: Tue, 23 Dec 2008 21:50:51 +0000
From: Jacob Meuser <[email protected]>
To: OpenBSD Misc <[email protected]>
Subject: Re: no sound with aucat -l
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: [email protected]
On Tue, Dec 23, 2008 at 11:12:14AM -0700, Steven wrote:
* Steven <[email protected]> [081223 10:30]:
It seems that if you have an audio/video/multimedia application
running when you start up aucat in server mode you get a "stopped
input" message and then you have to use "kill -9 <pid>" to kill the
aucat server. Not surpisingly, the application is accessing
/dev/audio and aucat cannot.
eh?
$ cat > /dev/audio < /dev/zero &
[1] 24358
$ aucat -l
safile_new: can't open device
$ fg
cat > /dev/audio < /dev/zero
^C
$
where exactly do you see the "stopped input" message?
Interesting, I've got multiple instance of aucat running again. I'm
not too sure why, but they weren't killed off like pkill said they
were.
So, when an already running instance of aucat is running I see:
$ sudo aucat -l &
[1] 30719
$
[1] + Stopped (tty output) sudo aucat -l
So it's not "stopped input", sorry about the misleading error
message.
I didn't have vlc running this time. Pidgin is running so maybe
there was a conflict over /dev/audio there? I'm a little concerned
about pkill reporting that programs have been killed when they're
still running.
Could that be contributing?
--
W. Steven Schneider <[email protected]>
