DOCSEARCHbyAlgolia
Submit Docs

MediaKind Developer Documentation

website·Indexed 35 days ago

https://docs.mediakind.com/

Developer documentation for MediaKind products and workflows, focusing on the MK.IO APIs. Includes guides for the Media API, Channels API for MK.IO Beam devices, Fleets API for device operations, Infrastructure API for network topology, and the Live API for managing live encoding and multiview composition.

Tokens
235.1K
Snippets
479
Records
1.7K
Agent score
64%

What's inside MediaKind

  1. Overview of the MK.IO Fleets API

    The Fleets API is the operational API for MK.IO Beam devices. It is used to register devices into a project, protect device configurations via backups, manage software versions, and collect diagnostic support packages. The API operates at the Project scope.

  2. Overview of MK.IO Platform Concepts

    MK.IO platform management and operational concepts include:

    • Organizations and Teams: Management of organizations, projects, team membership, and project-level access control.
    • API Resource Patterns: Standard patterns used for automating MK.IO workflows via API.
    • Resource States: Provisioning and operational states returned by MK.IO APIs.
    • Latency: Performance characteristics across live ingest, processing, packaging, and playback.
    • Edge Devices: Connectivity and integration of edge devices with MK.IO projects.
    • Pricing: The usage-based pricing model and the specific resources that contribute to costs.

  3. Overview of Static Multiview Channels

    A staticMultiviewChannels resource composes multiple live inputs into a single encoded multiview output. It is designed for continuous 24/7 production infrastructure (e.g., control room monitoring feeds, permanent studio outputs) and is billed at a monthly flat rate. For time-bounded workloads, use staticMultiviewEvents instead.

  5. Overview of MK.IO Beam capabilities

    MK.IO Beam is a network edge processing platform designed for high-quality broadcast and streaming headends, low-latency contribution encoding, and video/audio decoding. It integrates with the MK.IO cloud portal for automated control, monitoring, and life cycle management.

  6. Overview of MK.IO Beam Receiver capabilities

    The MK.IO Beam Receiver demodulates incoming signals and decodes video and audio, converting compressed transport streams into baseband output. It supports both satellite inputs (DVB-S, DVB-S2, and DVB-S2X via hardware demodulator cards) and IP transport stream inputs. A single satellite input can be routed to multiple Receiver services, or assigned independently.

  7. Overview of SCTE-35 Rewriting in MK.IO Beam

    SCTE-35 Rewriting is a stream conditioning service in MK.IO Beam used to manage, normalize, and distribute event signals that control content switching (such as advertising, blackouts, and content substitution). It ingests normalized event data via the SCTE-224 standard and maps media points (including policy, viewing policy, and audience attributes) to scheduled or signal-based SCTE-35 controls, which are then distributed to downstream encoders and TS processors.

  8. Overview of MediaKind API Domains

    MediaKind provides a suite of APIs to manage media workflows, infrastructure, and organizational settings:

    • Media API: Used for ingesting, transcoding, packaging, protecting, and publishing live and on-demand video assets.
    • Management API: Used for controlling organizations, users, teams, projects, webhook notifications, and usage reporting.
    • Fleets API: Used for registering and managing hardware/software device inventory for on-premises edge deployments.
    • Live API: Used for creating and managing live channels, events, and multiview compositions.
    • Templates API: Used for managing versioned configuration templates that live encoding and multiview resources depend on.
    • Infrastructure APIs: Used for configuring network settings and sites across the platform.

  9. Overview of JPEG-XS with Jumbo Frames

    Jumbo frames are Ethernet frames with a payload exceeding the standard 1500 bytes. They are recommended for JPEG-XS services with bitrates of 300 Mbps and higher to improve network performance by reducing packet header overhead. For jumbo frames to function, every device in the network path (including switches and routers) must be configured to support them.

  10. Overview of MK.IO Media Resource Model

    The MK.IO media resource model defines how media is organized, processed, protected, and delivered. Key components include:

    • Assets and Asset Filters: Reference cloud storage and modify manifests.
    • Transforms and Jobs: Reusable processing definitions and the specific job instances that execute them.
    • Live Events: The relationship between live inputs, processing modes, outputs, and archives.
    • Streaming Endpoints: Origin services used for packaging and delivering content.
    • Streaming Locators: Mechanisms to expose assets and apply streaming policies.
    • Content Protection: Configuration for content key policies, encryption, and Digital Rights Management (DRM).

  11. Overview of MK.IO streaming infrastructure

    To deliver content to viewers in MK.IO, two infrastructure components must be configured:

    1. Streaming Endpoint: The delivery server (origin) that handles viewer requests and serves content from storage. These are typically created per environment (e.g., production, staging) and reused across many assets.
    2. Streaming Locator: A configuration attached to a specific asset that generates playback URLs and controls streaming protocols, protections (DRM), and access windows.

  12. Overview of MK.IO Media Transformation Platform

    MK.IO is a cloud-native media transformation and delivery application used for building and operating modern video services. It is a scalable SaaS environment that allows users to manage end-to-end media processing workflows via both a User Interface (UI) and an API.