qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [Qemu-devel] [PATCH 00/10] apply volume on client side v5
Date: Thu, 22 Mar 2012 16:21:28 +0100	[thread overview]
Message-ID: <1332429698-10395-1-git-send-email-marcandre.lureau@redhat.com> (raw)

Hi,

This patch series implements client-side audio volume support. This reduces confusion of guest users when volume control is not effective (because mixemu is disabled or because client-side is muted and can't be unmuted by the guest..)

Instead, the backend is responsible for applying volume giving the guest control over the full range of the client, and avoiding multiple level of volume/mute effects.

Although I was mainly interested in having the Spice audio backend support, I also added PulseAudio backend support (which unfortunately requires full-blown API, even after quick discussion with upstream).

v5:
- code style fixes (spaces)
- left out from patch series the RFC "remove PLIVE and PERIOD options"


Marc-André Lureau (10):
  audio: add VOICE_VOLUME ctl
  audio: don't apply volume effect if backend has VOICE_VOLUME_CAP
  hw/ac97: remove USE_MIXER code
  hw/ac97: the volume mask is not only 0x1f
  hw/ac97: add support for volume control
  audio/spice: add support for volume control
  Do not use pa_simple PulseAudio API
  configure: pa_simple is not needed anymore
  Allow controlling volume with PulseAudio backend
  Enable mixemu by default, add runtime option

 audio/audio.c          |   29 +++-
 audio/audio_int.h      |    6 +
 audio/audio_template.h |    2 +
 audio/mixeng.c         |    6 -
 audio/paaudio.c        |  476 +++++++++++++++++++++++++++++++++++++++++++-----
 audio/spiceaudio.c     |   41 ++++
 configure              |   14 +-
 hw/ac97.c              |  139 +++++---------
 hw/hda-audio.c         |    4 -
 9 files changed, 561 insertions(+), 156 deletions(-)

-- 
1.7.7.6

             reply	other threads:[~2012-03-22 15:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 15:21 Marc-André Lureau [this message]
2012-03-22 15:21 ` [Qemu-devel] [PATCH 01/10] audio: add VOICE_VOLUME ctl Marc-André Lureau
2012-03-22 15:21 ` [Qemu-devel] [PATCH 02/10] audio: don't apply volume effect if backend has VOICE_VOLUME_CAP Marc-André Lureau
2012-03-22 15:21 ` [Qemu-devel] [PATCH 03/10] hw/ac97: remove USE_MIXER code Marc-André Lureau
2012-03-22 15:21 ` [Qemu-devel] [PATCH 04/10] hw/ac97: the volume mask is not only 0x1f Marc-André Lureau
2012-03-22 15:21 ` [Qemu-devel] [PATCH 05/10] hw/ac97: add support for volume control Marc-André Lureau
2012-03-22 15:21 ` [Qemu-devel] [PATCH 06/10] audio/spice: " Marc-André Lureau
2012-03-22 15:21 ` [Qemu-devel] [PATCH 07/10] Do not use pa_simple PulseAudio API Marc-André Lureau
2012-03-22 15:21 ` [Qemu-devel] [PATCH 08/10] configure: pa_simple is not needed anymore Marc-André Lureau
2012-03-22 15:21 ` [Qemu-devel] [PATCH 09/10] Allow controlling volume with PulseAudio backend Marc-André Lureau
2012-03-22 15:21 ` [Qemu-devel] [PATCH 10/10] Enable mixemu by default, add runtime option Marc-André Lureau

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=1332429698-10395-1-git-send-email-marcandre.lureau@redhat.com \
    --to=marcandre.lureau@gmail.com \
    --cc=marcandre.lureau@redhat.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).