All of lore.kernel.org
 help / color / mirror / Atom feed
From: agraham <agraham@g-b.net>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU VNC Audio - All audio data null
Date: Sat, 14 Jul 2012 13:55:14 +0100	[thread overview]
Message-ID: <50016C32.6000906@g-b.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1207141443570.1428@linmac>

On 07/14/2012 11:44 AM, malc wrote:
> On Sat, 14 Jul 2012, agraham wrote:
>
>> On 07/14/2012 03:17 AM, agraham wrote:
>>> Hi Guys,
>>>
>>> I've written a VNC client that implements the VNC QEMU Audio extensions.
>>> Using QEMU 0.13 it works very very for remote sound, however after
>>> upgrading to QEMU 1.1.0 the audio stream contains only bytes of zeros,
>>> so this results in no sound on the client.
>>>
>>> It is almost like the stream is muted by sending 0 bytes instead of the
>>> actual data.
>>>
>>> 0: VNC: :SOUND: AudioOn
>>> 1: VNC: :SOUND: Received _QEMU_Audio_Server_Message: Operation: 1
>>> 2: VNC: :SOUND: Received _QEMU_Audio_Start
>>> 3: VNC: :SOUND: Received _QEMU_Audio_Server_Message: Operation: 2
>>> 4: VNC: :SOUND: Received _QEMU_Audio_Data 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>>> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>>>
>>> Is there something new that needs to be done in order for the sound to
>>> be pushed out, like some unmute mechanism?
>>>
>>> I rebuilt QEMU 0.15.1 and sound worked but was very choppy, I think due
>>> to some timer injection changes - but that's another issue.
>>>
>>> Thanks in advance.
>>>
>>> Albert
>>
>> I've just rebuilt QEMU 1.0 (and all of its dependencies) and it has the same
>> problem (zero bytes), so some incompatibility was introduced between 0.15.1
>> and 1.1.0.
>>
>> Anyone got any clues ?
>
> Please try to bisect the issue.
>

My previous comment had a typo, it should have said: between 0.15.1 and 
1.0. (not 1.1.0)

bi-section so far:

I suspect that one of the following patches is causing the issue, these 
are all added to QEMU 1.0 (by Fedora at least) and are included in 1.1.0 
upstream.

# Spice volume control backports, all are upstream for 1.1
Patch501: 0501-audio-add-VOICE_VOLUME-ctl.patch
Patch502: 0502-audio-don-t-apply-volume-effect-if-backend-has-VOICE.patch
Patch503: 0503-hw-ac97-remove-USE_MIXER-code.patch
Patch504: 0504-hw-ac97-the-volume-mask-is-not-only-0x1f.patch
Patch505: 0505-hw-ac97-add-support-for-volume-control.patch
Patch506: 0506-audio-spice-add-support-for-volume-control.patch
Patch507: 0507-Do-not-use-pa_simple-PulseAudio-API.patch
Patch508: 0508-configure-pa_simple-is-not-needed-anymore.patch
Patch509: 0509-Allow-controlling-volume-with-PulseAudio-backend.patch

In order to use the QEMU VNC Audio for remote sound, you must
export QEMU_AUDIO_DRV=none, this indicates that you are not using a 
back-end.

QEMU_AUDIO_DRV=none is deceptive, but accurate, it tells QEMU not to 
connect to the QEMU host sound system. It does _not_ mean there is no sound.

Volume/mute control for VNC QEMU remote sound should _always_ be managed 
from the client side and should be on by default, but it looks like 
something is interfering with the stream from QEMU >0.15.1 on the server 
side and thus breaking the QEMU VNC extension.

Albert

  reply	other threads:[~2012-07-14 12:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-14  2:17 [Qemu-devel] QEMU VNC Audio - All audio data null agraham
2012-07-14  5:37 ` agraham
2012-07-14 10:44   ` malc
2012-07-14 12:55     ` agraham [this message]
2012-07-14 17:10       ` agraham
2012-07-14 17:20         ` malc
2012-07-14 19:30           ` agraham
2012-07-14 20:09             ` malc
2012-07-14 22:16               ` agraham
2012-07-14 22:23                 ` malc
2012-07-14 22:42                   ` agraham
2012-07-14 22:52                     ` agraham
2012-07-14 23:23                       ` malc
2012-07-14 23:01                     ` malc
2012-07-14 23:13                       ` agraham
2012-07-14 23:21                         ` malc
2012-07-15 19:22                           ` agraham
2012-07-15 19:48                             ` malc
2012-07-16  0:03                             ` malc
2012-07-16  2:10                               ` agraham
2012-07-16  8:12                                 ` Daniel P. Berrange
2012-07-16 10:56                                   ` agraham
2012-07-16 19:58                                   ` agraham

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=50016C32.6000906@g-b.net \
    --to=agraham@g-b.net \
    --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.