media-blocks-sdk-net-ios

Build and wire VisioForge Media Blocks SDK graph pipelines in .NET for iOS.

Updated May 29, 2025
One-click install
npx skills add https://github.com/visioforge/help --skill media-blocks-sdk-net-ios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: media-blocks-sdk-net-ios
Source: https://github.com/visioforge/help/tree/main/dotnet/agent-skills/media-blocks-sdk-net-ios
Command: npx skills add https://github.com/visioforge/help --skill media-blocks-sdk-net-ios

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of creating advanced, graph-based media capture, transcode, record, and streaming workflows in native .NET for iOS where the higher-level SDK does not provide enough control.

Core Features & Use Cases

  • Graph-based pipeline construction: Assemble pipelines by connecting Media Blocks (sources, encoders, tees, renderers, and sinks) rather than relying on a single “god-object” API.
  • Native iOS integration specifics: Correct iOS setup for net10.0-ios, VideoToolbox H.264 encoding, AudioToolbox-backed AAC, required Info.plist privacy keys, and mandatory SDK initialization order.
  • Production troubleshooting for common iOS failures: Avoid silent app termination, AOT/JIT ExecutionEngineException, missing-camera scenarios, trial/registration issues, and black preview due to renderer/clock configuration.
  • Use cases: iPhone/iPad capture (camera + microphone) to MP4, preview + record with a tee topology, dynamic graph wiring for different scenarios, and streaming/muxing setups driven by custom block graphs.

Quick Start

Use the media-blocks-sdk-net-ios skill to generate a native net10.0-ios pipeline that initializes VisioForgeX.InitSDK(), loads the required iOS privacy keys, builds a source → tee → renderer/encoder → MP4 sink graph, and starts preview with await pipeline.StartAsync().

Frequently Asked Questions about media-blocks-sdk-net-ios

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a custom .NET iOS media pipeline for camera capture and MP4 recording?

To build a .NET iOS media pipeline, connect source, encoder, tee, and sink blocks graph-style rather than relying on a single god-object API. You can assemble capture, encoding, rendering, and recording workflows specific to iOS environments.

Why does my .NET iOS camera preview show a black screen when the pipeline starts?

A black camera preview in .NET iOS pipelines often results from incorrect renderer clock configuration. Setting the VideoRendererBlock configuration with IsSync=false before starting the pipeline resolves this rendering issue.

How do I fix ExecutionEngineException AOT JIT errors in native .NET for iOS media applications?

To fix AOT JIT ExecutionEngineException errors in .NET iOS media apps, set the MtouchInterpreter property to all. This ensures AOT interpreter compatibility required by the underlying media SDK wrappers.

Do I need specific Info.plist privacy keys for microphone and camera capture in .NET iOS apps?

Yes, .NET iOS camera and microphone capture requires explicit privacy strings in Info.plist. Missing these privacy declarations causes silent app termination or missing-camera scenarios during pipeline execution.

Can I split a camera stream to show a live preview while simultaneously recording to an MP4 file?

Yes, you can split a camera stream for simultaneous preview and MP4 recording by using a tee topology. Connect the source block to a tee, then route outputs to both a renderer and an MP4 muxing sink.

What is the correct initialization order for VisioForge Media Blocks SDK in a native iOS application?

The correct initialization order requires calling VisioForgeX.InitSDK() at root setup before constructing any graph pipeline. Proper wrapper and iOS redist NuGet pinning must also be configured prior to pipeline execution.