From: malc <av1474@comtv.ru>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [RFC] qemu-gui based on wxWidgets and libvncclient
Date: Wed, 18 Oct 2006 15:17:30 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0610181515090.678@home.oyster.ru> (raw)
In-Reply-To: <Pine.LNX.4.63.0610181218100.14200@wbgn013.biozentrum.uni-wuerzburg.de>
On Wed, 18 Oct 2006, Johannes Schindelin wrote:
> Hi,
>
> On Tue, 17 Oct 2006, Fabrice Bellard wrote:
>
>> Another point is that you should consider adding audio support. I can
>> help you on that (maybe malc would be interested too !). A simple format
>> could be 4 bit ADPCM at fixed frequency. Optionally A more advanced
>> codec such as Vorbis could be used.
I am certainly ready to give a helping hand to anyone who attempts
something to that effect.
>
> Please, please not _another_ vnc hack! The RFB protocol loses all of its
> appeal if everybody has proprietary, incompatible extensions! If you
> bother to search Google for prior art, here is a link:
>
> http://www.ks.uni-freiburg.de/php_arbeitdet.php?id=75
>
> Yes, it is in German, but it already works. No need to add yet another
> obscure extension.
Schade das mein Deutsch ...ehh... isn't basically up to scratch.
--
vale
next prev parent reply other threads:[~2006-10-18 11:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 16:35 [Qemu-devel] [RFC] qemu-gui based on wxWidgets and libvncclient Marc André Tanner
2006-10-12 21:25 ` Martin Bochnig
2006-10-16 3:56 ` [Qemu-devel] " Anthony Liguori
2006-10-17 19:32 ` Fabrice Bellard
2006-10-18 1:29 ` Anthony Liguori
2006-10-18 10:21 ` Johannes Schindelin
2006-10-18 11:17 ` malc [this message]
2006-10-18 14:06 ` Anthony Liguori
2006-10-19 8:52 ` Oliver Gerlich
2006-10-19 18:05 ` Fabrice Bellard
2006-10-19 19:01 ` Stefan Weil
2006-10-20 9:00 ` VNC audio extension, was " Johannes Schindelin
2006-10-19 16:08 ` Jorge Luis Zapata Muga
2006-10-17 21:10 ` Marc André Tanner
2006-10-17 21:23 ` Daniel P. Berrange
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=Pine.LNX.4.64.0610181515090.678@home.oyster.ru \
--to=av1474@comtv.ru \
--cc=Johannes.Schindelin@gmx.de \
--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).