ScreenLiveStream-Windows

Project Overview

QuestCast VR for Windows is the Windows client of ScreenLiveStream, letting a Windows PC and an Android phone or Meta Quest headset cast to each other over the local network. It works as both sender and receiver: it can capture the desktop or a chosen window with system audio and push it to a mobile device, and it can receive Android streams in a standalone window. The whole pipeline uses D3D11 and Media Foundation hardware codecs and is fully compatible with the Android protocol.

Two-way casting between PC and headset, with hardware acceleration keeping latency low.

Key Features

• Two-way sender and receiver: switch between PC sender and receiver and cast either way with Android devices
• Window and fullscreen capture: built on Windows.Graphics.Capture to grab a single window or a whole monitor, with a cursor toggle
• System audio capture: grabs 48 kHz stereo system sound non-intrusively through WASAPI Loopback
• Hardware codecs: calls Media Foundation hardware codecs with NVIDIA, AMD, and Intel acceleration
• H.265 and H.264: defaults to H.265/HEVC and offers an ultra-low-latency preset without B frames
• Low-latency rendering: presents through a Direct3D 11 flip swap chain to reduce delay
• Protocol compatibility: works with the Android custom packet protocol, UDP 9998 discovery, UDP and TCP transport, and speed probing

Target Audience

• Users who cast from a PC
• Meta Quest headset users
• Users who receive phone screens on a PC
• Users running demos or streams on a LAN

Quick Start

1. Install Visual Studio and the Windows SDK, then configure and build with CMake
2. Run the built ScreenLiveStreamWindows.exe
3. Choose the PC sender or PC receiver at the top

PC sender

1. Pick the monitor or app window to cast from the capture target dropdown
2. Select an Android or Quest receiver from the LAN list, or enter its IP and port 8888
3. Choose the encoder, bitrate, frame rate, and protocol, then click start casting

PC receiver

1. Confirm the listen port (default 8888) and transport protocol (UDP or TCP)
2. Click start receiving
3. On the phone or Quest sender list, pick Windows-PC and start casting

The build commands are shown below:

cmake -B build -A x64
cmake --build build --config Release

Core Advantages

• Low-latency streaming: hardware codecs plus a flip swap chain cut visible delay
• Fully interoperable: cast directly with Android phones or Quest without extra adapters
• Zero-copy capture: GPU textures go straight into the encoder to cut copy overhead
• Dual purpose: one PC can act as sender or receiver for more flexible use

System Requirements

Notes

• Requires a GPU with hardware codec support; NVIDIA, AMD, or Intel integrated graphics all work
• The sender and receiver must be on the same LAN and use the same transport protocol
• Building requires Visual Studio and the Windows SDK, targeting x64
• Video travels directly over the LAN, so use it only on trusted networks