FFmpeg is a comprehensive, production-grade multimedia framework providing libraries and command-line tools for encoding, decoding, transcoding, muxing, demuxing, filtering, streaming, and playing audio, video, subtitles, and related metadata. The codebase is organized into several core libraries: libavcodec (codec implementations), libavformat (container formats), libavfilter (audio/video filters), libavutil (utilities), libavdevice (device I/O), libswresample (audio resampling), and libswscale (image scaling/colorspace conversion). The primary user-facing tools are ffmpeg (conversion/streaming), ffplay (media player), and ffprobe (media analysis). The architecture is modular, with each library exposing a public API and internally using a plugin-like registration system for codecs, demuxers, muxers, filters, and bitstream filters. Hardware acceleration is supported via Vulkan, CUDA, VA-API, D3D11VA, D3D12VA, VideoToolbox, MediaCodec, and others, with architecture-specific SIMD optimizations for x86, ARM, RISC-V, MIPS, LoongArch, and PowerPC. The project is actively maintained with extensive testing infrastructure including fuzzers, unit tests, and a checkasm framework for verifying assembly optimizations.
Frigate is a production-grade, full-stack Network Video Recorder (NVR) with real-time AI object detection. It ingests IP camera streams, performs motion detection, object detection (via TFLite/ONNX/OpenVINO/TensorRT on CPU/GPU/NPU), tracking, and recording. The backend is Python with FastAPI, Peewee ORM, and ZMQ-based inter-process communication. The frontend is a React/TypeScript single-page application with live views, timeline review, config editing, and GenAI enrichments (face recognition, license plates, semantic search, chat). It supports hardware acceleration across a wide range of devices (Coral, Intel iGPU, NVIDIA Jetson, Hailo, Rockchip NPU, etc.) and integrates deeply with Home Assistant. While primarily an application, it contains substantial data/research components including ML model runners, embedding pipelines, and post-processing logic for classification and transcription.
This repository is a Java library for industrial communication protocols, providing implementations for Siemens S7 PLC, Modbus, Mitsubishi Melsec, RTSP/RTP/RTCP media streaming, and MP4 file format handling. The library features a modular architecture with clear separation by protocol, annotation-based serialization frameworks, and low-level utilities for binary data handling. It serves as an SDK for developers to integrate industrial device communication and media streaming capabilities into their applications. The code demonstrates consistent use of design patterns (builder, template method, annotation-based processing) and includes comprehensive test suites showing usage patterns.
Monibuca/engine is a media streaming server engine written in Go, designed for extensibility through a plugin system. It handles the ingestion (publishing) and distribution (subscribing) of media streams, supporting protocols like RTSP, WebRTC, HTTP-FLV, and RTMP via plugins. The engine manages stream lifecycle through a state machine (waiting for publisher, track availability, publishing, waiting to close, closed), processes audio/video/data tracks with efficient buffering, and provides an HTTP API for stream control and monitoring. Key internals include a custom ring buffer for low-latency frame queuing, a memory pool to reduce GC pressure, and an event bus for inter-component communication. The configuration system supports layered overrides (command line > plugin config > global config > defaults). The architecture emphasizes separation of concerns: core stream management resides in stream.go, track handling in track/, publisher/subscriber logic in publisher/ and subscriber/, and plugins extend functionality without modifying the core. Data flows involve publishers sending media to the engine, which demuxes into tracks stored in ring buffers; subscribers then consume these tracks for retransmission. External dependencies include pion/webrtc for WebRTC, bluenviron/gortsplib for RTSP, and zap for logging. The engine exhibits strong performance optimizations but contains some complexity in state handling and occasional use of unsafe pointers for efficiency.
SysDVR is a Nintendo Switch homebrew streaming tool that captures the console's video and audio output and streams it to external clients via USB, TCP, or RTSP. The system comprises three main components: a sysmodule (C code) running on the Switch that interfaces with the grc:d service to capture frames and audio, a cross-platform client (C# .NET 9) that receives the stream, decodes it with FFmpeg, and renders/records using SDL2 and ImGui, and a configuration app (C++ ImGui) that runs on the Switch to manage streaming modes and patches. The architecture is modular with clear separation between capture, transport, and playback layers. The client uses a custom binary protocol with handshake, packet headers, and NAL replay for efficient streaming. External dependencies include libnx (Switch), FFmpeg, SDL2, libusb, ImGui, and .NET 9. The codebase demonstrates solid engineering with reusable patterns like buffer pools, pipeline chains, and platform abstraction, though it carries some technical debt from outdated third-party bindings and platform-specific workarounds.