How do I stream a webcam to a browser using icey?

Use the PacketStream pipeline to attach a video capture source, encode with FFmpeg, and send via WebRTC with Symple signaling. The README provides a 150-line C++ example in the webcam-streamer sample.

icey vs GStreamer for WebRTC applications?

icey offers a more integrated C++-focused stack with built-in signaling and TURN, while GStreamer has a larger plugin ecosystem but requires more setup. Choose icey for cohesive C++ development; GStreamer for broader media format support.

Does icey support audio codecs like Opus?

Yes, via FFmpeg integration, icey supports any audio and video codec that FFmpeg can handle, including Opus for WebRTC and AAC for recording, as detailed in the AV module.

How to set up a self-hosted TURN server with icey?

Build the turn module and run the sample turnserver; icey includes a production-grade RFC 5766 TURN server with TCP support and channel binding for NAT traversal.

Can icey be used on mobile platforms like iOS?

The README mentions iOS build fixes, but mobile support is less emphasized; it's primarily targeted at Linux, macOS, and Windows servers, so cross-platform use may require extra effort.

Is icey production-ready for large-scale deployments?

With high-performance networking and modular design, icey can scale, but you'll need to handle infrastructure aspects like load balancing, as it's a toolkit, not a turnkey solution.

Open-Awesome

LibSourcey

LGPL-2.1C++2.5.0

A modular C++20 toolkit for real-time media, WebRTC, and networking, built as a lightweight alternative to libwebrtc.

Visit Website GitHub

1.4k stars352 forks0 contributors

What is LibSourcey?

icey is a modular C++20 toolkit that provides a complete real-time media stack, integrating WebRTC, FFmpeg, and async networking into a single, lightweight library. It solves the problem of fragmented media development by offering a cohesive alternative to Google's libWebRTC and GStreamer, with faster builds, smaller binaries, and no dependency conflicts.

Target Audience

C++ developers building real-time media applications, such as video conferencing systems, media servers, live streaming platforms, or server-side recording tools, who need fine-grained control over media pipelines and WebRTC signaling.

Value Proposition

Developers choose icey for its modular design, fast build times, and comprehensive feature set—including built-in signaling and TURN server—which eliminates the need to integrate multiple disparate libraries and reduces deployment complexity.

Overview

Real-time media stack and lightweight libwebrtc alternative, built in C++20

Use Cases

Best For

Building custom WebRTC media servers for video conferencing
Streaming live video from cameras or files to web browsers
Recording browser media streams server-side for telehealth or proctoring
Deploying self-hosted TURN relays for NAT traversal in production WebRTC applications
Developing high-performance HTTP/WebSocket servers in C++
Creating modular media pipelines with zero-copy processing and FFmpeg codec support

Not Ideal For

Projects requiring rapid prototyping in high-level languages like Python or JavaScript
Simple HTTP serving tasks without media components where lighter libraries suffice
Environments with legacy toolchains that lack C++20 and modern compiler support
Teams needing extensive third-party plugins or a large community ecosystem

Pros & Cons

Pros

Modular and Lightweight

With 16 independent modules, icey allows linking only what's needed, resulting in small binaries and build times in minutes, unlike monolithic alternatives like libWebRTC.

Integrated Media Stack

Combines WebRTC via libdatachannel, FFmpeg for any codec, and built-in Symple signaling and RFC 5766 TURN server, eliminating dependency hell and reducing integration work.

High-Performance Networking

The HTTP stack, built on libuv and llhttp, outperforms Go's net/http and Node.js in benchmarks, achieving 72,209 req/sec with lower latency.

Zero-Copy Pipeline

PacketStream enables efficient media processing with explicit backpressure and frame-dropping control, minimizing memory overhead for real-time flows.

Cons

Steep Toolchain Requirements

Requires C++20 and modern compilers (GCC 12+, Clang 15+), which can be a barrier in environments with fixed or older toolchains.

System Dependency Management

Auto-detection of OpenSSL, FFmpeg, and other system libraries can fail or require manual installation, adding deployment complexity compared to self-contained solutions.

Limited Ecosystem Maturity

As a newer project, icey has a smaller community and fewer third-party integrations than established frameworks like GStreamer, which may impact support and extensibility.

Open Source Alternative To

LibSourcey is an open-source alternative to the following products:

GStreamer

GStreamer is a pipeline-based multimedia framework that enables the creation of applications for handling audio and video streams, including playback, recording, editing, and streaming.

libwebrtc

libwebrtc is an open-source library that provides WebRTC (Web Real-Time Communication) functionality, enabling audio, video, and data communication between web browsers and applications.

Frequently Asked Questions

Related Projects

Folly

An open-source C++ library developed and used at Facebook.

Abseil Common Libraries (C++)

Stars18,088

Forks3,184