Back to corpus
technical noteexperiment writeup candidatescore 32

Insta360 + K11/LUME Custom Camera Runbook

This runbook turns the Insta360 from a passive stream into a programmable MotionMix/LUME source. The current production path uses MotionMixApp on iOS to connect to the Insta360 SDK, extract virtual camera crops from the 360 preview, run Vision pose detection, and publish LUME-compatible UDP JSON to K11 on `[ip]:9705`.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

This runbook turns the Insta360 from a passive stream into a programmable MotionMix/LUME source. The current production path uses MotionMixApp on iOS to connect to the Insta360 SDK, extract virtual camera crops from the 360 preview, run Vision pose detection, and publish LUME-compatible UDP JSON to K11 on `[ip]:9705`. Official Insta360 developer docs say the SDK supports secondary development for the X5, X4 Air, X4, X3, ONE RS 1-Inch, ONE RS, ONE X2, ONE R, and ONE X product lines. Supported platforms are Windows, Linux, iOS, and Android. Each platform SDK is split into Camera SDK and Media SDK. - SDK guide: `https://onlinemanual.insta360.com/developer/en-us/resource/sdk` - iOS SDK: `https://github.com/Insta360Develop/iOS-SDK` - Desktop CameraSDK C++: `https://github.com/Insta360Develop/Desktop-CameraSDK-Cpp` - Desktop MediaSDK C++: `https://github.com/Insta360Develop/Desktop-MediaSDK-Cpp` - OSC control surface: `https://github.com/Insta360Develop/Insta360_OSC` - iOS SDK path: best current path because MotionMixApp already has the SDK frameworks and the LUME UDP publisher. - Desktop CameraSDK path: strong K11-native future path because the C++ SDK can receive preview video/audio/gyro/exposure data over USB, but it requires a Windows/Linux decoding and stitching service. - MediaSDK path: useful for recorded `.insv` / `.insp` post-processing and preview stitching, not required for today's live pose bridge. - OSC path: useful for lightweight camera status/control experiments, but not the primary live image path. - `Frameworks/INSCameraSDK.xcframework` - `Frameworks/INSCameraServiceSDK.xcframework` - `Frameworks/INSCoreMedia.xcframework` - `Frameworks/SSZipArchive.xcframework`

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.