We’re working on streaming a multimedia remote desktop to the Raspberry Pi.
In the future we envision, you shall be able to use a webbrowser on the Pi at normal speeds – including YouTube videos, etc. – operate with CPU / GPU intensive applications – as all the processing is done on a server, and just the H.264 stream rendering on the Raspberry Pi.
Look at the WinSwitch homepage for installation instructions – it is really quite easy.
WinSwitch bundles several remote clients (VNC / xpra / RDP) with an easy-to-use interface, and broadcasts servers / clients (via Avahi / Bonjour).
A very first demonstration of the capabilities of this stack can be obtained installing WinSwitch on your “normal” desktop machine, and on a server.
As a server we currently use the “fastest available” Intel Atom processor currently on the market – Intel(R) Atom(TM) CPU C2750. We are looking into using AMD’s ARM 64 bit processor as server hardware in the future (power-efficiency!), and the performance should be roughly comparable.
As a client we use a Dell Inspiron notebook (with Windows 8.1), Core i7 processor, FullHD resolution.
There is a xpra package available for the Raspberry Pi, which is based on a quite old version of xpra, and will not connect to our server. This may be related to the huge version difference between the two packages, wrong setup, or special tweaking done by winswitch to xpra.
We can stream a webbrowser running YouTube fullscreen in FullHD, which will use about 50 % of the server’s total resources (decoding one or several videos in FullHD, encoding one FullHD stream). This is possible in low-latency, at about 30fps and high quality. Yes, this does include an audio stream, too.
The stream uses about 40 Mbp/s of bandwidth, and is much more reliable (less choppy) if streamed over LAN, instead of WLAN. In fast-moving scenes video will still be a bit choppy, but tolerably.
The encoding is done in software, using x264.
Streaming ONE browser window is possible with our server hardware in good quality (for video content) from either the host directly, or from a virtual Ubuntu machine (KVM-virtualized) inside it.
TWO browser windows will start to degrade the quality, even if trying to force best quality and lowest latency.
This screenshot shows the YouTube video in the browser being streamed on the client.
Winswitch allows you to stream single applications. Performance / latency is very good on a local network, keyboard / mouse delay is barely noticeable.
In general, applications will be quite useable and seem responsive.
Applications requiring precise mouse / screen cordination, like graphics software will not be usable (at least with our hardware setup).
This screenshot shows Firefox being streamed through xpra.
VLC media player being streamed – sound works
GIMP: barely usable (too much delays)
word processing with AbiWord: OK performance (could be better, but it’s usable)
Streaming a desktop with xnest / Xephyr / xpra from inside a virtualised Ubuntu container on the base hardware is NOT possible at low-latency (30 fps) with high-quality. (With our server hardware)
In order to test it, you have to install additional packages on the server:
aptitude install xnest xserver-xephyr
and set the desktop default to xpra, possibly after restarting the server / client:
Apparently frame-grabbing / mirroring the desktop / going through the X layer uses up much more processor resources.
Gameplay is quite smooth – but full screen video playback would be a problem.
- authentication with private/public key pairs may be problematic without additional configuration, for first tests I recommend to re-enable password login for SSH.
- audio for the browser may require alsa and pulseaudio
- This does not work on the Raspberry Pi yet, this is our next step (compiling a package for it).
- encoding performance and latency may be enhanced significantly using NVidia’s NVENC hardware encoding / framegrab API – which xpra supports.