Skip to content

IMMERSE Documentation

Documentation for the IMMERSE platform: Studio (authoring), Runtime (playback), and Node (hardware service).

Pick your role

  • For Designers


    You author shows in IMMERSE Studio — rooms, devices, looks, cues, logic graphs.

    Start designing

  • For Venue Installers


    You set up Runtime and Nodes at a physical venue, push media, and prep for opening night.

    Install at a venue

  • For Operators


    You press GO during the show. One page. Read it, tape it next to the dashboard.

    Run the show

  • For Developers


    Schema, APIs, build instructions, and architectural decisions.

    Build with IMMERSE

Quick map of the platform

┌─ Designer's laptop ─┐         ┌─ Venue mini-PC ─┐         ┌─ Nodes ─┐
│  IMMERSE Studio     │ .ishow  │  IMMERSE        │ HTTP    │  IMMERSE   │ → speakers
│  (author shows)     │ ──────► │  Runtime        │ ──────► │  Node      │ → screens
└─────────────────────┘         │  (play shows)   │         └────────────┘ → relays
                                └────┬────────────┘
                                     │ sACN multicast
                                     ▼
                                ┌────────────┐
                                │ DMX lights │
                                └────────────┘

Three pieces, one platform. Studio produces .ishow files. Runtime loads them and drives playback. Nodes carry out audio/video/GPIO commands on Runtime's behalf. Lighting goes direct to fixtures via the industry-standard sACN protocol.

Versions

This documentation matches:

  • IMMERSE Studio v0.1.0
  • IMMERSE Runtime v0.1.0
  • IMMERSE Node v0.1.0
  • Show file schema 0.5.0

When you upgrade, check the changelog for breaking changes.

I just want to get something running

  1. Author a show: see Getting Started for Designers
  2. Set up the venue: see Site Preparation
  3. Run the show: see the operator one-pager

Reporting bugs

Email support@immersecontrol.com with:

  • What you were doing
  • What you expected
  • What happened instead
  • The relevant log file (locations in the operator and developer docs)