media-blocks-sdk-net-wpf

What problem does it solve?

Integrating VisioForge Media Blocks SDK into a Windows WPF app is difficult because you must correctly assemble and wire a graph of media blocks (sources, transforms, sinks), initialize the SDK, register licensing, and avoid common deployment pitfalls that cause runtime failures.

Core Features & Use Cases

• Graph-based pipeline construction: Build GStreamer-style directed graphs using MediaBlocksPipeline and connect block pads to create custom topologies for capture, transcode, mix, stream, and record.
• WPF rendering and device-driven capture: Use VideoRendererBlock with a WPF VideoView for preview, plus DeviceEnumerator-based selection for video/audio sources and sinks.
• Encoding, muxing, and dynamic inputs: Configure tee + encoders + file/network muxers (MP4, MPEG-TS, WebM) using dynamic sink inputs via IMediaBlockDynamicInputs.
• Production readiness: Pin wrapper and redist versions, match PlatformTarget architecture, initialize and tear down the SDK correctly, and handle licensing via SetLicenseCertificateAsync(byte[]).

Quick Start

Use the media-blocks-sdk-net-wpf skill to create a WPF project that previews webcam video in a VideoView and records to MP4 with an H264 video encoder and AAC audio encoder, following the pipeline wiring shown in the bundled sample.