What problem does it solve?
Integrating VisioForge Media Blocks SDK into a single .NET MAUI codebase is hard because you must correctly wire a graph-based media pipeline while also handling per-OS native dependencies, permissions, and licensing order.
Core Features & Use Cases
- Cross-platform pipeline integration (MAUI): Set up
MediaBlocksPipeline with camera and microphone sources and connect them to renderers/encoders/sinks that work across Windows, Android, iOS, and Mac Catalyst.
- Preview + capture graphs with tees: Keep real-time preview running while recording by splitting media streams using
TeeBlock into renderer and MP4 sink branches.
- Production-ready setup essentials: Register MAUI handlers (
AddVisioForgeHandlers()), include the correct conditional native runtime packages per target framework, request platform permissions, and load the trial/purchased .vflicense before StartAsync.
Use when you need custom media processing (capture, transcode, stream, record) that requires low-level control over the pipeline graph rather than a high-level capture/edit/player API.
Quick Start
Use the media-blocks-sdk-net-maui skill to generate a MAUI project setup that targets net10.0-android plus net10.0-ios and net10.0-maccatalyst on macOS, registers AddVisioForgeHandlers(), requests camera/mic permissions, and wires a preview-only and preview+MP4 capture pipeline with the correct per-platform filename and licensing flow.