All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] dsound: warning: Voice is already playing
Date: Wed, 18 Feb 2009 21:18:31 +0100	[thread overview]
Message-ID: <499C6D17.1050701@web.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0902180119550.2613@linmac.oyster.ru>

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

malc wrote:
> On Tue, 17 Feb 2009, Robert Riebisch wrote:
> 
>> malc wrote:
>>
>>>>> What is the exact sequence of events that leads to it?
>>>> What do you mean by "sequence"?
>>> Step by step actions after which the following message is seen, including
>>> all command line parameters.
> 
> [..snip..]
> 
>> I narrowed it down to GUS emulation, because this warning also appears,
>> when I just use "-soundhw gus" (not "all").
>>
> 
> It's actually fallout from r6402:
> "Rework vm_state_change notifiers (Jan Kiszka)"
> 
> GUS, unlike all other cards emulated by QEMU, is mixing sound at all times
> and as such it calls AUD_set_active_out during intialization stage which
> happens before vm_start is called and when it does audio vm change state 
> notification callback is invoked which tries to enable underlying audio
> subsystem's voice, but it is already enabled and in case of dsound will,
> rightfully, complain.
> 
> Jan, can you please check that this doesn't break Musicpal or the other
> ARM stuff you have written and i have no means to test:

Sounds good, at least on the MusicPal (I haven't written the "other
stuff" nor do I have test setups at hand).

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-02-18 20:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 21:49 [Qemu-devel] dsound: warning: Voice is already playing Robert Riebisch
2009-02-16 21:59 ` malc
2009-02-16 22:02   ` Robert Riebisch
2009-02-16 23:16     ` malc
2009-02-17 19:54       ` Robert Riebisch
2009-02-17 22:27         ` malc
2009-02-18 20:18           ` Jan Kiszka [this message]
2009-02-18 20:44             ` 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=499C6D17.1050701@web.de \
    --to=jan.kiszka@web.de \
    --cc=av1474@comtv.ru \
    --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.