immersive-spatial-video-production

Plan, finish, and validate immersive video deliverables across VR180, 360, and spatial workflows.

123|21|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/calesthio/generative-media-skills --skill immersive-spatial-video-production
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: immersive-spatial-video-production
Source: https://github.com/calesthio/generative-media-skills/tree/main/skills/production/content-formats/immersive-spatial-video-production
Command: npx skills add https://github.com/calesthio/generative-media-skills --skill immersive-spatial-video-production

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps media teams plan and deliver immersive video without causing avoidable viewer discomfort, metadata failures, accessibility gaps, or rights issues. It turns complex decisions about 180-degree, 360-degree, spatial, stereoscopic, and wide-FOV video into practical production and QA workflows.

Core Features & Use Cases

  • Format and Capture Planning: Select the appropriate mono 360, stereo 360, VR180, spatial, dome, or flat companion format based on viewer presence, staging, platform, and production constraints.
  • Production and Finishing Guidance: Plan camera placement, stereo comfort, stitching, seams, nadir treatment, stabilization, attention direction, spatial audio, captions, color, VFX, and immersive editing.
  • Delivery and Quality Assurance: Validate projection, stereo, pose, audio, caption, container, and platform metadata across YouTube, Vision Pro, headsets, and local playback.
  • Rights and Safety Review: Identify privacy, likeness, location, music, performance, trademark, sensitive-site, and accessibility requirements for immersive capture.
  • Use Case: Create a stereo VR180 capture brief for a front-row concert performance, including camera geometry, ambisonic audio, captions, comfort safeguards, rights clearances, and headset delivery tests.

Quick Start

Use the immersive spatial video production skill to create a capture, finishing, rights, accessibility, and device QA plan for a four-minute stereo VR180 performance video intended for YouTube and Vision Pro.

Frequently Asked Questions about immersive-spatial-video-production

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

FAQPage Schema
How do I plan spatial video capture to prevent viewer discomfort on headsets?

To plan spatial video for comfortable headset viewing, you must carefully select capture formats, manage stereo camera geometry, and validate spatial audio and comfort safeguards during production and finishing.

What is the best way to validate VR180 metadata for YouTube and Vision Pro delivery?

Validating VR180 metadata for YouTube and Vision Pro requires checking projection, stereo pose, audio, caption, and container metadata against target-device specifications to prevent playback failures during quality assurance.

How do I choose between mono 360 and stereo VR180 for an immersive performance video?

Choosing between mono 360 and stereo VR180 depends on viewer presence needs, staging constraints, and platform delivery targets, balancing stereoscopic depth requirements against capture complexity and stitching limits.

What privacy and rights clearances do I need for 360-degree immersive video capture?

For 360-degree immersive video capture, you must review and clear privacy, likeness, location, music, performance, trademark, and sensitive-site requirements to ensure compliant delivery and avoid rights failures.

Does immersive video production require special accessibility and fallback planning?

Immersive video production requires accessibility and fallback planning to ensure captions, spatial audio alternatives, and flat companion formats are validated for viewers across various headset and platform delivery environments.

Why does my stereoscopic 360 video fail quality assurance on local playback devices?

Stereoscopic 360 video fails local playback QA when projection, stereo alignment, or container metadata are incorrect, requiring thorough stitching review and target-device validation to resolve playback errors.