From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4254] Let WM8750 users write to audio buffer directly.
Date: Mon, 28 Apr 2008 01:29:06 +0200 [thread overview]
Message-ID: <fb249edb0804271629r487fcccdi6e87b572bdf4f352@mail.gmail.com> (raw)
In-Reply-To: <4813BB52.1050300@web.de>
On 27/04/2008, Jan Kiszka <jan.kiszka@web.de> wrote:
> andrzej zaborowski wrote:
> > Yes, my doubt is if there is a use case in which this ever makes a
> > difference (and if it's valid for svn users), i.e. when you can't use
> > the host's mixer (using a mixer app outside qemu). With the
> > VirtualBox style mixer api the guest and host mixers can be the same
> > and that would be best to have.
>
>
> [ Digging through VBox's patch chaos... ] Just to ensure I got it right:
> You mean dropping vol from SWVoiceOut/In in favor of those global
> pcm_out/in_volume?
Well, my idea would be to retain volume in SWVoiceOut/In and use
always the volume of the voice that is active to set on host (wm8750.c
only has one active voice at all times). If more voices are active in
one or more QEMUSoundCard's then I don't know what should happen.
Maybe that's not so useful, and global volume like in your patches is
better.
VBox has this mixing engine which applies volume in software but is
still generic (i.e. sits in audio/). I don't know what malc thinks
qemu should adapt for mixer control (if anything).
Cheers
prev parent reply other threads:[~2008-04-27 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 12:00 [Qemu-devel] [4254] Let WM8750 users write to audio buffer directly Andrzej Zaborowski
2008-04-26 13:29 ` Jan Kiszka
2008-04-26 13:50 ` andrzej zaborowski
2008-04-26 14:11 ` Jan Kiszka
2008-04-26 20:10 ` andrzej zaborowski
2008-04-26 23:31 ` Jan Kiszka
2008-04-27 23:29 ` andrzej zaborowski [this message]
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=fb249edb0804271629r487fcccdi6e87b572bdf4f352@mail.gmail.com \
--to=balrogg@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).