qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Gerlich <olig9@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [RFC] qemu-gui based on wxWidgets and libvncclient
Date: Thu, 19 Oct 2006 10:52:12 +0200	[thread overview]
Message-ID: <45373CBC.7060809@gmx.de> (raw)
In-Reply-To: <453634E4.20109@cs.utexas.edu>

Here's a partial translation/explanation of the link that Johannes sent 
some days ago, concerning remote sound in VNC. The final documentation 
(in german) can be found at 
http://www.ks.uni-freiburg.de/download/studienarbeit/SS05/08-05-TonSpur-DRichter/Dokumentation/Dokumentation.pdf

According to that PDF, sound is transmitted by capturing it with a Java 
application, then converting it using JMF (Java Media Framework) and 
sending it out as RTP stream. A Java client receives the RTP stream and 
plays it. As far as I understand, handshaking is done with an own TCP 
connection, while actual RTP packets are sent via UDP. During 
handshaking, connection speed is measured (see 6.1.2) to decide on the 
encoding (see 6.2.2).

There's also an older document at 
http://www.ks.uni-freiburg.de/download/studienarbeit/WS03/Ton-Spur-VNC.pdf 
which indeed describes a way to use ESD for remote sound.


Regards,
Oliver


Anthony Liguori wrote:
> 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.
>>
>> 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.
> 
> My German is not very good, but from what I was able to read, it seems 
> like they are just using VNC to transmit the port information for doing 
> esd forwarding.  Presumably this saved a lot of work because no server 
> side code was needed.
> 
> Regards,
> 
> Anthony Liguori
> 
>> Ciao,
>> Dscho
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 
> 

  reply	other threads:[~2006-10-20  6:39 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
2006-10-18 14:06       ` Anthony Liguori
2006-10-19  8:52         ` Oliver Gerlich [this message]
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=45373CBC.7060809@gmx.de \
    --to=olig9@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).