Skip to main content

Kyber 0.8.0

· 2 min read

Version 0.8.0 is a significant milestone that introduces QUIC-based streaming as the default transport protocol, replacing the older RTP-based approach. The new transport layer delivers improved performance and reliability, and is now the recommended way to connect a client to a host. Alongside this, a new streaming pipeline component is now used on the host side to handle video encoding and delivery, replacing the previous implementation with one that is more flexible and maintainable.

GPU support on Windows has been extended considerably: AMD and Intel GPUs are now supported for hardware-accelerated video encoding when using the QUIC transport. A new --video_codec option lets you choose between H.264, HEVC, and AV1, giving you control over compression and compatibility depending on your hardware. For users who prefer or need RTP, it remains available via a new --protocol option, though some newer features are exclusive to the QUIC path.

The server now handles spawning and coordinating the input and streaming services directly, improving process management and stability. Communication between client and server has been moved to HTTPS for better security. A new --port option has been added so you can configure the server port from the command line.

Changelog​

  • controller/libkynput: windows_sys is now used and replaces winapi
  • Rust dependencies updated
  • Rust toolchain updated to 1.65.0
  • Add avserver that now uses libtxproto
  • controller: Use libkypc to spawn and communicate inputserver and avserver
  • controller: Switch to HTTPS
  • client: Kymux (QUIC) replaces RTP as the default protocol
  • client: Add --protocol option to choose between Kymux/RTP
  • avserver: Add support of AMD and Intel GPUs on Windows. Not supported when using RTP
  • client: Add --video_codec option to choose between H264/HEVC/AV1. Not supported when using RTP
  • client: Add --port to choose the port to use to connect to a controller