From: Richard Neill <rn214@hermes.cam.ac.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Soundwrapper and artsd (fails to share)
Date: Mon, 06 Dec 2004 01:01:04 +0000 [thread overview]
Message-ID: <41B3AF50.9000603@hermes.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0412060338420.2323@home.oyster.ru>
malc wrote:
> On Mon, 6 Dec 2004, Richard Neill wrote:
>
>> Dear All,
>>
>> I wonder why the following doesn't seem to work? Qemu still takes an
>> exclusive lock on the soundcard, even when invoked with soundwrapper.
>> I'm using this invocation:
>
>
> There is no such thing as excluse soundcard lock, /dev/dsp is being opened
> and if sound hardware does not support multiple hardware channels then
> this is where the story ends.
Sorry - please excuse my poor terminology. What I mean is that when qemu
is running, no other application may play sounds.
>
>>
>> soundwrapper /usr/local/bin/qemu -cdrom servicepacks.iso -hda
>> winxp_pro_hd.img -boot c -localtime -enable-audio -m 256 -monitor stdio
>
>
> I'm not quite sure what soundwrapper is, but if it is just a script that
> calls artsdsp under the hood, then it's a no go:
As I understand it, soundwrapper intercepts the open() call to /dev/dsp,
and redirects it to a socket, talking to artsd.
>
> <quote>
> # artsdsp i386-softmmu/qemu
> artsdsp works only for binaries
> </quote>
Sorry, I'm afraid I don't understand this. qemu is a binary, isn't it?
I did the following tests. In all cases, commands (i) and (ii) are run
simultaneously in different terminals:
1)
(i) play file1.wav
(ii) play file2.wav
Result:
file1.wav plays. When it is finished, file2.wav plays.
2)
(i) soundwrapper play file1.wav
(ii) soundwrapper play file2.wav
Result:
file1.wav and file2.wav play simultaneously.
3) (i) soundwrapper qemu [qemu options]
(ii) soundwrapper play file2.wav
Result: qemu's audio is played. file2.wav does not start playing until
qemu has shut down. In my view, this behaviour is undesirable; it's also
rather puzzling. After all, to the O.S., qemu is just another
application, isn't it? So, if soundwrapper can redirect the output of
play (i.e. the sox binary), why can't it do the same with qemu.
[Info: Host = Linux/KDE/ARTS; guest = WinXP ]
>
>>
>> No other audio can be played on the host while qemu is running. Does
>> anyone have any ideas? Thanks for your help,
>>
>
> Perhaps some dmix(ALSA's) magic can work, but you'll have to RTFM about it
> yourself.
Thanks for the idea - I shall try it.
Regards
Richard
next prev parent reply other threads:[~2004-12-06 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 0:02 [Qemu-devel] Soundwrapper and artsd (fails to share) Richard Neill
2004-12-06 0:42 ` malc
2004-12-06 1:01 ` Richard Neill [this message]
2004-12-06 1:21 ` Jim C. Brown
2004-12-06 1:32 ` malc
2004-12-06 1:43 ` Jim C. Brown
2004-12-06 1:13 ` Jim C. Brown
2004-12-06 1:27 ` malc
2004-12-06 1:55 ` Jim C. Brown
2004-12-06 10:34 ` malc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41B3AF50.9000603@hermes.cam.ac.uk \
--to=rn214@hermes.cam.ac.uk \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.