Dominic Szablewski

It's just a guess to provide some default. Higher resolutions require higher bitrates and 1500 bits per pixel worked reasonably well for a few resolutions I tested this with. Of...

No. The [grabber.c](https://github.com/phoboslab/jsmpeg-vnc/blob/master/source/grabber.c) code to get pixel data from a window is quite Windows specific. You'd need to rewrite this for other OSes. The [app_on_message()](https://github.com/phoboslab/jsmpeg-vnc/blob/master/source/app.c#L135) that "fakes" keyboard and mouse...

@jaredly good idea. The summary now reads: _A low latency, high framerate screen sharing server for Windows and client for browsers_

Yep, thanks for the notice! This seems to be a new requirement in Windows 8: http://stackoverflow.com/questions/22259936/c-move-mouse-in-windows-using-setcursorpos Do you know if we can force the App to run with elevated rights?...

Try starting the jsmpeg-vnc.exe with Administrator privileges. Some versions of Windows (not sure exactly which) don't allow manipulation of mouse/keyboard input for non-elevated apps.

Capturing, encoding and transmitting sound is not that difficult, however, decoding and playing Sound in the browser is. Afaik there's currently no native Browser API that can deal with streaming...

Sounds like a bandwidth problem on the server. You could check with tools like `iftop`, but this is really outside the scope of this project.

The video canvas is always stretched to 100% width. You can change this by removing [these two lines of CSS](https://github.com/phoboslab/jsmpeg-vnc/blob/master/client/index.html#L21-L22) in the `index.html`.

The server sometimes has problems capturing hardware accelerated windows. Try disabling Aero, i.e. chose a Windows "Classic Theme".

Be more specific. I haven't tested it on Android, but it should work just fine with Chrome (which is the default browser on newer devices).