Real-Time Pipeline SDK vs Broadcast Frame-Based SDK
Media Blocks SDK .NET vs Medialooks MFormats SDK
Which C# Video SDK to Choose in 2026
Last updated: January 2026
Looking for an MFormats alternative for your .NET broadcast or video processing project? This comparison evaluates Media Blocks SDK .NET and Medialooks MFormats SDK across architecture, SDI hardware support, cross-platform deployment, live streaming, pricing, and code examples — helping you choose the right C# video SDK for broadcast, capture, or custom media pipelines.
Executive Summary
Media Blocks SDK .NET and Medialooks MFormats SDK both target professional video processing and streaming, but with fundamentally different architectures. Media Blocks uses a modular pipeline model — developers connect source, transform, and sink blocks like building a processing graph. MFormats uses a frame-based grab-process-output model — developers manage a loop where each frame is an object with attached audio. Both support broadcast hardware and streaming, but Media Blocks is cross-platform with 400+ blocks while MFormats is Windows-only with deeper multi-vendor SDI support.
| Aspect | Media Blocks SDK .NET | MFormats SDK |
|---|---|---|
| Architecture | Modular pipeline (blocks + pads) | Frame-based (grab → process → output) |
| Platform | Windows, macOS, Linux, iOS, Android | Windows only |
| Pricing | €500/year or €500–€1,500 team/lifetime | ~$4,508/developer/year (subscription) |
| Block Count | 400+ blocks | N/A (monolithic API) |
| Best For | Custom pipelines, cross-platform, complex workflows | Broadcast playout, multi-vendor SDI |
Architecture: Modular Pipeline vs Frame Loop
Media Blocks SDK .NET — Modular Pipeline
- ✓Build custom pipelines by connecting reusable blocks (source, transform, sink)
- ✓Pipeline manages threading and data flow automatically
- ✓400+ blocks available for video, audio, encoding, effects, and output
- ✓Dynamic pipeline modification — add/remove blocks at runtime
- ✓Create your own custom blocks for specialized processing
- ✓Cross-platform: Windows, macOS, Linux, iOS, Android
MFormats SDK — Frame-Based Loop
- •Developer controls the frame loop explicitly (grab → process → output)
- •Each frame is a COM object with attached audio channels
- •Simpler mental model for single-input/single-output workflows
- •More manual work required for complex multi-output pipelines
- •Deep multi-vendor SDI hardware integration (AJA, BlueFish444, DELTACAST)
- •Windows-only deployment
Feature Comparison Matrix
| Feature | Media Blocks SDK | MFormats SDK | Winner |
|---|---|---|---|
| Modular pipeline (connect blocks) | ✅ 400+ blocks | ❌ Monolithic | Media Blocks SDK |
| Dynamic pipeline modification | ✅ Add/remove blocks at runtime | ❌ | Media Blocks SDK |
| Custom block development | ✅ Create your own blocks | ❌ | Media Blocks SDK |
| Frame-based processing | ✅ Via callback blocks | ✅ Primary model | Tie |
| USB webcams | ✅ SystemVideoSourceBlock | ✅ | Tie |
| IP cameras (RTSP/RTMP/HLS) | ✅ UniversalSourceBlock | ✅ | Tie |
| Screen capture | ✅ ScreenSourceBlock | ✅ | Tie |
| Blackmagic DeckLink | ✅ DeckLinkSourceBlock | ✅ | Tie |
| AJA Video Systems | ❌ | ✅ Native | MFormats |
| NDI source | ✅ NDISourceBlock | ✅ | Tie |
| Virtual source (push frames) | ✅ VirtualVideoSourceBlock | ✅ Bitmaps | Tie |
| Industrial cameras (Basler, FLIR) | ✅ Native blocks | ❌ | Media Blocks SDK |
| Video effects (GPU) | ✅ Multiple GPU effect blocks | ⚠️ Basic (scale, convert) | Media Blocks SDK |
| Audio effects (40+) | ✅ Audio effect blocks | ❌ Normalization only | Media Blocks SDK |
| Text/image overlays | ✅ OverlayBlock | ✅ Text + graphic | Tie |
| HTML5 CG overlay | ❌ | ✅ Character Generator | MFormats |
| Chroma key | ✅ ChromaKeyBlock | ❌ | Media Blocks SDK |
| Video mixing / composition | ✅ VideoMixerBlock | ✅ GPU mixer | Tie |
| Color correction | ✅ ColorEffectsBlock | ✅ | Tie |
| Resize / scale | ✅ VideoResizeBlock | ✅ GPU scaling | Tie |
| Deinterlace | ✅ DeinterlaceBlock | ✅ | Tie |
| Audio effects pipeline | ✅ EQ, reverb, chorus, 3D | ❌ | Media Blocks SDK |
| Audio mixing | ✅ AudioMixerBlock | ✅ | Tie |
| RTMP output | ✅ RTMPSinkBlock | ✅ | Tie |
| RTSP server | ✅ | ✅ | Tie |
| HLS output | ✅ HLSSinkBlock | ✅ | Tie |
| SRT output | ✅ SRTSinkBlock | ✅ | Tie |
| NDI output | ✅ NDISinkBlock | ✅ | Tie |
| WebRTC | ✅ | ✅ VTConnect | Tie |
| MP4, MKV, AVI, MOV | ✅ Typed sink blocks | ✅ | Tie |
| MXF | ✅ | ✅ | Tie |
| Hardware encoding (NVENC, QSV, AMF) | ✅ Typed encoder blocks | ✅ NVENC, QSV | Tie |
| Apple VideoToolbox / MediaCodec | ✅ | ❌ | Media Blocks SDK |
| H.264 | ✅ Multiple encoder blocks | ✅ | Tie |
| H.265/HEVC | ✅ | ✅ | Tie |
| AV1 | ✅ | ❌ | Media Blocks SDK |
| VP8/VP9 | ✅ | ❌ | Media Blocks SDK |
| Pre-event recording (circular buffer) | ✅ PreEventRecordingBlock | ❌ | Media Blocks SDK |
| Motion detection | ✅ CVMotionCellsBlock | ❌ | Media Blocks SDK |
| Face detection | ✅ CVFaceDetectBlock | ❌ | Media Blocks SDK |
| Barcode/QR scanning | ✅ BarcodeDetectorBlock | ❌ | Media Blocks SDK |
| Video transitions | ✅ TransitionBlock | ✅ | Tie |
| Frame-accurate operations | ✅ Pipeline-based | ✅ Frame-level control | Tie |
| 24/7 ingest | ✅ | ✅ Proven stability | Tie |
| Docker deployment | ✅ Linux containers | ✅ Windows containers | Media Blocks SDK |
| DeckLink output | ✅ DeckLinkSinkBlock | ✅ | Tie |
| AJA output | ❌ | ✅ | MFormats |
When to Choose Each Solution
Choose Media Blocks SDK .NET When You Need
Cross-platform deployment
Your application must run on Windows, macOS, Linux, Android, or iOS — MFormats is Windows-only.
Custom modular pipelines
You need to build complex workflows by connecting source, processing, and output blocks with dynamic modification at runtime.
Advanced audio and video effects
Your project requires GPU video effects, 40+ audio effects, chroma key, or color grading — areas where MFormats has minimal support.
Computer vision features
You need built-in motion detection, face detection, or barcode/QR scanning without third-party libraries.
Modern codec support
Your workflow requires AV1, VP9, or Apple VideoToolbox / MediaCodec hardware encoding that MFormats does not support.
Budget-conscious teams
Your budget is under €2,000 — Media Blocks SDK is 9–27x cheaper than MFormats for a 5-developer team over 3 years.
Choose MFormats SDK When You Need
Multi-vendor SDI hardware
Your broadcast facility uses AJA, BlueFish444, DELTACAST, or Magewell hardware that requires native SDK integration.
HTML5 character generator overlays
You need a built-in HTML5 CG overlay engine for broadcast graphics and lower thirds.
Frame-based processing model
You prefer explicit frame loop control where each frame is a COM object you grab, process, and output in sequence.
Code Examples
Capture + Overlay + Record Pipeline
Media Blocks SDK .NET
C#// Build custom pipeline by connecting blocks
var pipeline = new MediaBlocksPipeline();
var source = new SystemVideoSourceBlock(
new VideoCaptureDeviceSourceSettings(deviceInfo));
var overlay = new TextOverlayBlock(
new TextOverlaySettings("LIVE"));
var tee = new TeeBlock(2, MediaBlockPadMediaType.Video);
var preview = new VideoRendererBlock(pipeline, videoView);
var h264Encoder = new H264EncoderBlock();
var fileOutput = new MP4SinkBlock(
new MP4SinkSettings("output.mp4"));
// Connect: source -> overlay -> tee -> [preview + encoder -> file]
pipeline.Connect(source.Output, overlay.Input);
pipeline.Connect(overlay.Output, tee.Input);
pipeline.Connect(tee.Outputs[0], preview.Input);
pipeline.Connect(tee.Outputs[1], h264Encoder.Input);
pipeline.Connect(h264Encoder.Output,
fileOutput.CreateNewInput(MediaBlockPadMediaType.Video));
await pipeline.StartAsync();MFormats SDK
C#var source = new MFLiveClass();
source.DeviceSet("video", 0, "");
var writer = new MFWriterClass();
writer.WriterSet("output.mp4", 0, "");
MFFrame frame;
while (running)
{
source.SourceFrameGet(-1, out frame, "");
frame.MFOverlayAdd(null, "text=\"LIVE\"", 0);
writer.WriterPut(frame, -1, "");
Marshal.ReleaseComObject(frame);
}Live RTSP Camera to HLS Stream
Media Blocks SDK .NET
C#var pipeline = new MediaBlocksPipeline();
var rtspSource = new RTSPSourceBlock(
new RTSPSourceSettings(
new Uri("rtsp://camera.local:554/stream")));
var videoView = new VideoRendererBlock(
pipeline, VideoView1);
var h264Encoder = new H264EncoderBlock(
new OpenH264EncoderSettings { Bitrate = 4000000 });
var aacEncoder = new AACEncoderBlock(
new AACEncoderSettings());
var hlsSink = new HLSSinkBlock(
new HLSSinkSettings("/var/www/stream/") {
SegmentDuration = TimeSpan.FromSeconds(4),
PlaylistLength = 5
});
pipeline.Connect(rtspSource.VideoOutput, videoView.Input);
pipeline.Connect(rtspSource.VideoOutput, h264Encoder.Input);
pipeline.Connect(rtspSource.AudioOutput, aacEncoder.Input);
pipeline.Connect(h264Encoder.Output,
hlsSink.CreateNewInput(MediaBlockPadMediaType.Video));
pipeline.Connect(aacEncoder.Output,
hlsSink.CreateNewInput(MediaBlockPadMediaType.Audio));
await pipeline.StartAsync();MFormats SDK
C#// MFormats requires manual frame loop
// and Windows-only deployment
var source = new MFLiveClass();
source.DeviceSet("video", 0, "");
var writer = new MFWriterClass();
writer.WriterSet(
"rtmp://server/live/stream", 0, "");
MFFrame frame;
while (running)
{
source.SourceFrameGet(-1, out frame, "");
// Process frame...
writer.WriterPut(frame, -1, "");
Marshal.ReleaseComObject(frame);
}
// Note: No cross-platform support.
// No Linux Docker deployment.Pricing and Total Cost Comparison
MFormats SDK uses an annual subscription model at approximately $4,508/developer/year. Media Blocks SDK offers both annual and perpetual licensing at a fraction of the cost.
| Scenario | Media Blocks SDK | MFormats SDK |
|---|---|---|
| 1 developer, 1 year | €500/year (annual) | ~$4,508 |
| 1 developer, lifetime | €500–€1,500 (one-time) | ~$13,524 (3 years) |
| 5 developers, 3 years | €1,500 (Team/Lifetime) | ~$67,620 |
| License type | Perpetual (lifetime) | Annual subscription |
| Subscription lapse | Still works | ⚠️ Watermark on output |
| Runtime fees | None | None |
Platform Support Comparison
| Platform | Media Blocks SDK | MFormats SDK |
|---|---|---|
| Windows | ✅ | ✅ |
| macOS | ✅ | ❌ |
| Linux | ✅ | ❌ |
| Android | ✅ | ❌ |
| iOS | ✅ | ❌ |
| Docker (Linux) | ✅ | ❌ |
| Docker (Windows) | ✅ | ✅ |
Media Blocks SDK is 9–27x cheaper over 3 years for a 5-developer team. MFormats adds watermarks if the subscription lapses, while Media Blocks perpetual licenses keep working indefinitely.
Limitations and Trade-offs
Media Blocks SDK Limitations
- ⚠No AJA Video Systems hardware support — MFormats has native AJA integration
- ⚠No built-in HTML5 character generator overlay engine
- ⚠Commercial license required — not suitable for open-source projects needing a free dependency
- ⚠Closed-source binary SDK — cannot inspect or modify native pipeline internals
MFormats SDK Limitations
- ⚠Windows-only — no macOS, Linux, Android, or iOS support
- ⚠No modular pipeline architecture — manual frame loop management required
- ⚠Limited video effects — basic scaling and conversion only, no GPU effects pipeline
- ⚠No audio effects pipeline — normalization only, no EQ/reverb/chorus
- ⚠No computer vision — no motion detection, face detection, or barcode scanning
- ⚠No AV1 or VP9 codec support
- ⚠Subscription lapses result in watermarked output
- ⚠Significantly higher cost (~$4,508/developer/year vs €500/year)
Decision Matrix
Use this matrix to match your requirements against each SDK. Scores are 1–5 (5 = fully meets requirement).
| Requirement | Media Blocks SDK | MFormats SDK | Recommended |
|---|---|---|---|
| Cross-platform deployment | Media Blocks SDK | ||
| Custom modular pipelines | Media Blocks SDK | ||
| Audio effects (40+) | Media Blocks SDK | ||
| GPU video effects | Media Blocks SDK | ||
| Motion/face/barcode detection | Media Blocks SDK | ||
| AV1 / VP9 encoding | Media Blocks SDK | ||
| Industrial cameras (Basler, FLIR) | Media Blocks SDK | ||
| Budget under €2,000 | Media Blocks SDK | ||
| Linux Docker containers | Media Blocks SDK | ||
| Multi-vendor SDI (AJA, BlueFish) | MFormats | ||
| HTML5 CG overlays | MFormats | ||
| Frame-based processing model | MFormats |
Hybrid Approach: Using Both Together
In some broadcast environments, combining both SDKs can leverage each product's strengths:
Media Blocks for processing + MFormats for SDI output
Use Media Blocks SDK for video effects, encoding, and cross-platform capture. Use MFormats for final SDI output to AJA or BlueFish444 hardware in a broadcast facility.
Media Blocks for cloud + MFormats for on-premise broadcast
Deploy Media Blocks SDK in Linux Docker containers for cloud-based processing and streaming. Use MFormats on Windows machines for on-premise broadcast playout with multi-vendor SDI hardware.
Gradual migration from MFormats to Media Blocks
Start new cross-platform features with Media Blocks SDK while maintaining existing MFormats-based Windows broadcast workflows. Migrate incrementally as Media Blocks SDK expands SDI support.
Conclusion
Media Blocks SDK .NET and Medialooks MFormats SDK both serve professional video processing, but their architectures and capabilities diverge significantly.
Media Blocks SDK .NET
Media Blocks SDK .NET is the right choice for cross-platform deployment (Windows, macOS, Linux, Android, iOS), modular pipeline workflows with 400+ blocks, advanced GPU video effects, 40+ audio effects, computer vision (motion/face/barcode detection), modern codecs (AV1, VP9, HEVC), and budget-conscious teams — at 9–27x lower cost than MFormats over 3 years with perpetual licensing and royalty-free distribution.
MFormats SDK
MFormats SDK is the right choice if you need multi-vendor SDI hardware support (AJA, BlueFish444, DELTACAST, Magewell), frame-based architecture with explicit frame loop control, or HTML5 character generator overlays in a Windows-only broadcast environment.
For 90% of cross-platform video applications, Media Blocks SDK delivers significantly more capability at a fraction of the cost. Broadcast facilities with multi-vendor SDI infrastructure may find MFormats worth its premium. For everything else — custom pipelines, effects, detection, streaming, encoding — Media Blocks SDK is the stronger choice.
