qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5850] Add basic audio functionality to vnc.c
Date: Tue, 2 Dec 2008 20:13:06 +0200	[thread overview]
Message-ID: <f43fc5580812021013m14c0f69w27dd8fa3d6541514@mail.gmail.com> (raw)
In-Reply-To: <4934A98D.6070006@codemonkey.ws>

On 12/2/08, Anthony Liguori <anthony@codemonkey.ws> wrote:
> Blue Swirl wrote:
>
> > On 12/1/08, malc <av1474@comtv.ru> wrote:
> >
> >
> > > Revision: 5850
> > >
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5850
> > >  Author:   malc
> > >  Date:     2008-12-01 20:57:48 +0000 (Mon, 01 Dec 2008)
> > >
> > >  Log Message:
> > >  -----------
> > >  Add basic audio functionality to vnc.c
> > >
> > >  This allows among other things to capturing A/V of running
> > >  guests. Ad-hoc client that does this (via script that invokes ffmpeg)
> > >  can be found at:
> > >
> http://repo.or.cz/w/qemu/malc.git?a=tree;f=vcap;hb=capture3
> > >
> > >
> >
> > 244   and aliguori t =
> > 245     match r8 (pump#get 1) 0 with
> > 246     | 001 -> audio t
> > 247     | msg -> fail "unexpected aliguori message %x" msg
> >
> > What's an unexpected aliguori message?
> >
> >
>
>  heh, I made him remove "aliguori" from the vnc code but he insisted on
> keeping it in the client code :-)
>
>  I added an extended message type to the VNC protocol.  It has no official
> name.

What, subliminal messages in the audio stream of the VNC?

... UMEQ ... esu ... tsum ... uoy ...

;-)

      parent reply	other threads:[~2008-12-02 18:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 20:57 [Qemu-devel] [5850] Add basic audio functionality to vnc.c malc
2008-12-01 21:09 ` Blue Swirl
2008-12-02  3:20   ` Anthony Liguori
2008-12-02 16:51     ` malc
2008-12-02 18:13     ` Blue Swirl [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=f43fc5580812021013m14c0f69w27dd8fa3d6541514@mail.gmail.com \
    --to=blauwirbel@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).