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

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.

-- 
mailto:av1474@comtv.ru

  reply	other threads:[~2012-07-14 10:44 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 [this message]
2012-07-14 12:55     ` agraham
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=alpine.LNX.2.00.1207141443570.1428@linmac \
    --to=av1474@comtv.ru \
    --cc=agraham@g-b.net \
    --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.