A high-performance .NET library for fetching and aggregating social media metrics across multiple platforms. SocialCounter provides a unified interface to retrieve follower counts and other social metrics while handling rate limiting, retries, and failures gracefully. Key Features: - Unified API for fetching social metrics across different platforms - Built-in resilience with automatic retry policies and exponential backoff - Parallel processing of requests to multiple social media platforms - Extensible design for adding new platform implementations - Configurable timeouts and comprehensive error handling
A high-performance .NET library for fetching and aggregating social media metrics across multiple platforms. SocialCounter provides a unified interface to retrieve follower counts and other social metrics while handling rate limiting, retries, and failures gracefully. Key Features: - Unified API for fetching social metrics across different platforms - Built-in resilience with automatic retry policies and exponential backoff - Parallel processing of requests to multiple social media platforms - Extensible design for adding new platform implementations - Configurable timeouts and comprehensive error handling
VST 3® plug-in hosting for NAudio. Discover, load, and host VST 3 audio effects and instruments. VST is a registered trademark of Steinberg Media Technologies GmbH.
A fully managed, cross-platform FFmpeg/FFprobe wrapper for .NET that makes media analysis and conversion easy. Exposes video and audio transcoding, muxing, probing, snapshots and animated GIFs, raw frame piping, a fluent argument builder covering codecs, filters, colour management, metadata and stream dispositions, a built-in process wrapper, and an in-memory image bridge (snapshots as CodeBrix.Imaging images) under the CodeBrix.VideoProcessing namespace.
Using Windows Media Foundation for webcams
Fluent media processing pipeline for .NET MAUI on Android, iOS, Mac Catalyst, and Windows: camera or gallery capture, resize, compress, EXIF removal, orientation correction, watermark, blur, redact, AES-256-GCM encryption, and upload. Designed for insurance, inspections, healthcare, and field capture.
YoloDotNet.ExecutionProvider.DirectML enables hardware-accelerated inference on Windows using Microsoft’s DirectML framework. This execution provider integrates ONNX Runtime’s DirectML backend and runs on top of DirectX 12, allowing inference to be accelerated on a wide range of GPUs using the Windows graphics driver stack. DirectML is a Windows-only technology and is supported on Windows 10 and Windows 11 with a DirectX 12–capable GPU. No vendor-specific SDKs or external runtimes are required beyond the standard Windows graphics drivers. This makes the DirectML execution provider a low-friction option for GPU acceleration on Windows systems. Designed for YoloDotNet’s modular, execution-provider-agnostic architecture, the DirectML provider integrates cleanly with the core library and exposes explicit, predictable inference behavior. It is well-suited for Windows applications that require GPU acceleration without locking into a specific hardware vendor or proprietary ML stack.
Stops Umbraco sites being OOM-killed in memory-limited containers while browsing the media section. Caps the unmanaged buffer pool ImageSharp retains and bounds how many images are processed concurrently, both derived from the memory available to the process. Backport of the fix proposed for the CMS in umbraco/Umbraco-CMS#23557, for Umbraco 13, 17 and 18 sites that need it now.
The Lyntai backends that need nothing beyond Lyntai.Core, the BCL and Microsoft.Extensions.Http: the authenticated `claude` and `codex` CLIs (completions and self-driving agent sessions), any OpenAI-shaped HTTP endpoint (OpenAI, Azure OpenAI, OpenRouter, llama-server, LM Studio, vLLM) for chat, embeddings or reranking, Ollama's native API for chat and embeddings, and an in-process model2vec embedder — bundled because none of them ships a native payload. Media backends live in Lyntai.Generation; local GGUF inference is Lyntai.Providers.LlamaSharp; in-process transformers are Lyntai.Providers.Onnx.
C# .NET library for creating CLI arguments for various media processing tools using fluent builders
.NET 9 Web Development Library with Core, Security, Data Processing, Database Operations, Logging & Monitoring, File & Media Processing, CAPTCHA & Anti-Bot, and Testing & Mocking Framework
Shared native libraries for the VisioForge .NET SDKs on Windows ARM64: the VisioForge native media and video processing libraries used by the Windows engines and their DirectShow filters, and the MediaInfo library the classic engines read media files with.
A high-performance .NET library for fetching and aggregating social media metrics across multiple platforms. SocialCounter provides a unified interface to retrieve follower counts and other social metrics while handling rate limiting, retries, and failures gracefully. Key Features: - Unified API for fetching social metrics across different platforms - Built-in resilience with automatic retry policies and exponential backoff - Parallel processing of requests to multiple social media platforms - Extensible design for adding new platform implementations - Configurable timeouts and comprehensive error handling
The engine-neutral contract for video processing in .NET: analyse media files, read decoded video frames and audio samples, write standard MP4 (H.264 or HEVC with AAC) video from your own frames and sound, and transcode, trim and join files - through one interface that a separate engine package implements for each platform - plus a registry through which separate video encoder packages (such as AV1) plug in. Dependency-free; carries its own frame, plane, frame-rate and media-description types and needs no image library.
Media player control and server for dotnet. Winforms, avalonia, uno desktop controls for playback via mplayer or mpv. Server side process video files using ffmpeg.
Media player control and server for dotnet. Winforms, avalonia, uno desktop controls for playback via mplayer or mpv. Server side process video files using ffmpeg.
Image processing with System.Drawing.Bitmap using ONNX Runtime.
Media player control and server for dotnet. Winforms, avalonia, uno desktop controls for playback via mplayer or mpv. Server side process video files using ffmpeg.
Official .NET SDK for the Sirv REST API. Provides a simple, type-safe way to interact with Sirv's image hosting and processing platform. Features include automatic token management, retry logic, async/await support, and comprehensive coverage of all 40+ API endpoints.
A small QUIC abstraction with two interchangeable backends: the real System.Net.Quic over native msquic, and an in-process loopback wired with System.IO.Pipelines that needs no msquic or IPv6. It lets a QUIC-based protocol (such as MOQT) be built and tested where msquic is unavailable, and leaves room for msquic features System.Net.Quic does not surface. Knows nothing about MoQ, so any QUIC protocol can target it.
The Android engine for CodeBrix.VideoProcessing.Core: analyse media files, decode video frames (I420, NV12, RGBA or Gray, at 8 bits or - where the device decoder outputs 10-bit P010 - 10 bits) and audio samples, write standard MP4 video (H.264, or HEVC where the device has an encoder, with AAC audio and a fast-start index) from your own frames and sound, take snapshots, and transcode, trim and join files - all on Android's own MediaExtractor, MediaCodec and MediaMuxer, with no native code and no ffmpeg. For .NET 10 Android applications on API level 33 and newer; register it once with CodeBrixVideoProcessingAndroid.Register() and code written against CodeBrix.VideoProcessing.Core works unchanged.
Alibaba Cloud ApsaraVideo for Media Processing (20180528) SDK Library for .NET
YoloDotNet is a modular, lightweight C# library for high-performance, real-time computer vision and YOLO-based inference in .NET. Built on .NET 8 and powered by ONNX Runtime, YoloDotNet provides explicit, production-ready inference for modern YOLO model families, including YOLOv5u through YOLOv26, YOLO-World, YOLO-E, RT-DETR and D-Fine. Support AOT. The library features a fully modular execution architecture with pluggable execution providers for CPU, CUDA / TensorRT, Intel OpenVINO, Apple CoreML, and DirectML, enabling predictable deployment across Windows, Linux, and macOS. YoloDotNet intentionally avoids heavy computer vision frameworks such as OpenCV. Image handling and preprocessing are performed using SkiaSharp, with no Python runtime, no hidden preprocessing, and no implicit behavior. Designed for low-latency inference and long-running workloads, YoloDotNet gives developers full control over execution, memory usage, and preprocessing — allowing you to choose the hardware, platform, and execution backend without unnecessary abstraction or overhead.
.NET process wrapper for invoking an independently installed FFmpeg executable from C# applications. The package builds command-line arguments and starts FFmpeg as a separate operating-system process; it does not include, distribute, install, or link against FFmpeg or libav* libraries.
Media file storage, processing, and metadata management core abstractions, interfaces, and types used by Carcass.Media.* libraries.
Payments for TeleForge — invoices, pre-checkout validation, payment processing, refunds, subscriptions, Telegram Stars, gifts, paid media, an anti-fraud pipeline and payouts.
Stops Umbraco sites being OOM-killed in memory-limited containers while browsing the media section. This is the ImageSharp 2.x variant, for sites using Umbraco.Cms.Imaging.ImageSharp2; use Umbraco.Community.Imaging.ImageSharp for the default ImageSharp 3.x setup. Caps the unmanaged buffer pool ImageSharp retains and bounds how many images are processed concurrently, both derived from the memory available to the process.
Media file storage, processing, and metadata management built with Azure Blob Storage.
YoloDotNet.ExecutionProvider.DirectML enables hardware-accelerated inference on Windows using Microsoft’s DirectML framework. This execution provider integrates ONNX Runtime’s DirectML backend and runs on top of DirectX 12, allowing inference to be accelerated on a wide range of GPUs using the Windows graphics driver stack. DirectML is a Windows-only technology and is supported on Windows 10 and Windows 11 with a DirectX 12–capable GPU. No vendor-specific SDKs or external runtimes are required beyond the standard Windows graphics drivers. This makes the DirectML execution provider a low-friction option for GPU acceleration on Windows systems. Designed for YoloDotNet’s modular, execution-provider-agnostic architecture, the DirectML provider integrates cleanly with the core library and exposes explicit, predictable inference behavior. It is well-suited for Windows applications that require GPU acceleration without locking into a specific hardware vendor or proprietary ML stack.
DRIT.Presentation is a pure-managed, cross-platform .NET library for creating, reading, and manipulating PowerPoint presentations (PPTX, PPTM, PPSX, PPSM, and ODP). It offers presentation processing capabilities including slides, charts, SmartArt, shapes, animations, transitions, media, digital signatures, AES-256 encryption, VBA macros, and PDF, image, SVG, and HTML export.
Multi-tenant WhatsApp Cloud API (Meta Graph API v24) toolkit for .NET 8. Send text, media, interactive, template, carousel and Flow messages; sync and create message templates; run broadcast campaigns with a queue worker; process webhooks (messages, statuses, account updates); keyword and AI (OpenAI/Flowise) chatbot replies; WhatsApp Flows; catalog orders with Razorpay/PhonePe payments; Embedded Signup. Ships an EF Core SQL Server schema and stores every tenant secret (access token, WABA id, app secret, payment keys) encrypted in the database.
Hosts one STANAG 5066 Edition 4 node in real time: the SIS server on TCP 5066 (Annex S), the real-time driver for the sans-IO core, a modem port with an M0LTE.Ms110d adapter, and in-process loopback media for tests. Licensed AGPL-3.0-or-later; commercial licences are available from the copyright holder (see the repository README).