menu
Nested Media Panels — Technology Spec
A composable system for packaging heterogeneous media (video, audio, images, vectors) into hierarchical containers and presenting them as adaptive panels across screens, AR, or spatial contexts.
Nested Media Container (NMC)Nested Media Panel (NMP)Scheduling & CompositionMultisensory I/O
Concepts
Core concepts
Two primitives — a storage container and a visual panel — enable deep nesting, time/space aware delivery, and multi‑modal presentation.
Nested Media Container (NMC)
Holds mixed media types and metadata; supports child containers to arbitrary depth for hierarchical organization and reuse.
Nested Media Panel (NMP)
The renderable layout that places media tracks (video, audio, images, polygons/overlays) into regions; panels can include sub‑panels to form grids, belts, or stacks.
Composition & Schedules
Composition rules map NMC assets to NMP regions; schedules drive time‑based rotation, live vs on‑demand, and ad inventory.
Primitives
Container vs Panel vs Organizer
Three roles work together: containers store and nest media, panels render layouts from containers, and the organizer coordinates scheduling and distribution across panels.
Nested Media Container (NMC)
- Purpose: Storage + hierarchy. Holds tracks (video, audio, images, polygons) and child containers.
- Scope: Reusable across many panels and schedules.
- Analogy: A folder of assets with metadata + children.
Nested Media Panel (NMP)
- Purpose: Presentation. A layout with regions that render tracks from an NMC; panels can include sub‑panels.
- Scope: Device/view dependent (screen, wall, AR plane, spatial zone).
- Analogy: A dashboard/canvas that places media into slots.
Organizer
- Purpose: Orchestration. Owns schedules, resolves conflicts, and routes containers to panels in time/space.
- Scope: Fleet‑level (many panels, venues, roles, SoI zones).
- Analogy: A broadcast control room + CMS.
| Aspect | Container (NMC) | Panel (NMP) | Organizer |
|---|---|---|---|
| Primary role | Store & nest media + metadata | Lay out & render media regions | Schedule & route NMC→NMP |
| Key objects | tracks[], children[] | regions[], children[] | schedules[], assignments[], policies[] |
| Inputs | Encoders, asset pipelines | Container refs, layout templates | Catalog of NMC/NMP, time/geo/context |
| Outputs | Addressable media bundles | Composed frames/audio/overlays | Resolved playlists, per‑panel timelines |
| Conflict handling | N/A (asset level) | Layout reflow & fallbacks | Priority rules, trims, re‑slots |
| Security | Entitlements on assets/children | Variant exposure per device/role | SoI/zone gating, audit, approvals |
Coordinator
Organizer API (preview)
Schedule containers into panels, resolve conflicts, and stream per‑panel playlists with audit.
Key types
type Assignment = { id: string; panelId: string; containerId: string; slot: { start: string; end: string }; priority?: number; soi?: 'Private'|'Social'|'Public' }
type Schedule = { id: string; name: string; assignments: Assignment[] }
type PlaylistItem = { at: string; panelId: string; render: { panel: string; container: string } }REST (sample)
POST /v1/organizer/schedules { name, assignments:[...] }
POST /v1/organizer/resolve { scheduleId }
→ { playlist: PlaylistItem[], conflicts: [] }
GET /v1/organizer/playlist?panelId=...&at=...Architecture
High‑level architecture
Server array and encoders feed NMCs; clients render NMPs with validation, policy, and context gating.
Pipeline
- Ingest: encoders and asset pipelines populate NMCs.
- Linking: NMCs reference live events, VOD, images, audio, polygons.
- Validation: client verifies policies/constraints before render.
- Render: NMP layouts compose regions from linked assets.
Panel Regions
Panels place tracks into regions (e.g., video viewport, audio rack, image slots, overlay polygons). Regions can contain nested panels for tiered UI or channel stacks.
Scheduling
Scheduling & composition patterns
Drag‑and‑drop timelines, nested channels, conflict resolution, and live/on‑demand switching.
Timeline scheduler
Operators place assets onto a time grid; NMPs rotate content per slot and resolve overlaps; supports channel nesting and program breaks.
Live vs On‑Demand
Panels shift from scheduled programs to live events; ad interstitials and overlays compose into panel regions alongside primary content.
Conflict handling
When assets collide, the system resolves by priority rules, duration trimming, or reflow to child panels.
I/O
Multisensory output & context gating
Visual, aural, and tactile channels can be orchestrated; location and identity cues tailor which panel variant is shown.
Visual • Aural • Tactile
NMPs coordinate multi‑channel delivery (screen, speakers, haptics) so a single panel can drive synchronized outputs.
Location & identity
Panels adapt to where/when a user is (geo‑fence, venue, room) and who they are (role, entitlement), selecting the correct container/panel variant.
Interface
Data model & API (preview)
A minimal shape for containers, panels, schedules, and policy checks.
Types
type MediaTrack = { id: string; kind: 'video'|'audio'|'image'|'polygon'; src: string; meta?: Record<string, any> }
type Container = { id: string; name: string; tracks: MediaTrack[]; children?: Container[]; meta?: Record<string, any> }
type PanelRegion = { id: string; role: 'video'|'audio'|'image'|'overlay'|'subpanel'; layout: { x: number; y: number; w: number; h: number }; childPanelId?: string }
type Panel = { id: string; name: string; regions: PanelRegion[]; children?: Panel[]; policy?: string[] }
type ScheduleSlot = { start: string; end: string; containerId: string; panelId: string; priority?: number }REST (sample)
POST /v1/nmc { name, tracks:[...], children:[...] }
POST /v1/nmp { name, regions:[...], children:[...] }
POST /v1/schedules { slots:[...] }
POST /v1/compose { containerId, panelId, at: ISO8601 }
→ { layout, resolvedAssets, conflicts:[], outputs:['visual','aural','tactile'] }Governance
Security & logging
Least‑privilege access to assets; every composition decision is auditable.
Access control
Role‑ and context‑aware gating of containers/panels; panel variant exposure is scoped to user, device, and place.
Audit
Schedules, overrides, and conflict resolutions are traced for replay.
Provenance
Every rendered region references its source track and transform chain.
Build with Nested Media Panels
Request a demo & tech brief
See authoring, scheduling, and multi‑modal delivery in action.
XRDNA, MoE, Map of Everything, eVa, Sphere of Influence, and Neural Voyager are all registered trademarks for XRDNA Inc
2025 XRDNA, Inc. All Rights Reserved.
2025 XRDNA, Inc. All Rights Reserved.