Ai-Launchpads
CAPTURE LIVE.
KEEP THE SOURCE.
Connect → Record → Stop & build.
Your original sensor observations stay local until you choose to upload them.
- 01
Connect & check
Run the local Kinect connector, approve your Studio tab, then check color, depth and infrared before recording.
Details & checks
Keep lighting bright and the sensor unobstructed. Kinect v2 requires its power adapter and USB 3. Confirm that the preview is fresh; missing sensor data is not a healthy connection.
- 02
Record measured views
Move slowly with overlapping views while tracking is valid. Watch coverage. If tracking is lost, return toward a previously observed view.
Details & checks
The continuous recorder saves original observations and measured camera poses on this computer. Reconstruction validates those observations and registration before fusion. Unseen surfaces stay incomplete. Full-resolution color processing can train appearance on measured geometry when its validation gates pass; the measured textured surface remains the fallback. Physical accuracy is not certified.
- 03
Stop & build
Stop recording to preserve the session and begin its build workflow. Processing requires an owner session and unlocked access.
Details & checks
A lost connection leaves saved observations recoverable. Reconnect, select the saved recording, then explicitly resume or build. Upload receipts preserve progress; resume with the exact original package. Gaussian training from other photographic sources requires a compatible calibrated capture package.
- 04
Review & share
Inspect alignment, missing surfaces and saved viewpoints. Export a portable project, or choose who can view a fixed scene revision.
Details & checks
Check reference scale before relying on a dimension. Preserve your original session and calibration evidence. Viewer links refer to a particular revision; you can unlist or revoke them later. A visually complete rendering is not evidence that an unobserved surface was measured.
Set up the local connector
Install and run the connector on the same device as this browser. 127.0.0.1:9773 always means this device, including when Studio is open on a Jetson. The website cannot install USB drivers. For a remote Orin, use Desktop’s Jetson workspace or the existing local-network session transfer.
Download connector source & setup instructions. Extract the entire ZIP into a permanent writable folder. Platform runtimes still require their own hardware qualification.
Linux / Jetson installation
Use Python 3.11 or newer alongside the system Python, plus venv support, git, a C++ compiler, pkg-config, libusb and libjpeg-turbo development headers. Follow README.md in the download. Setup builds the pinned libfreenect2 CPU adapter; it does not replace system drivers.
sh Setup.command
# Or select an installed interpreter:
GSPLAT_PYTHON=/path/to/python3.11 sh Setup.command
sh "Start Connector.command"Install the upstream Kinect udev rule as described in README.md, then reconnect the powered USB 3 adapter. Keep the connector running. Approve this Studio tab in the local pairing window; permission is never granted by downloading the files.
Connection troubleshooting
- Local window cannot load: the connector is not running on this device, or its port is unavailable. Start it and retry Connect Kinect.
- Pairing window opens, no sensor: check the powered Kinect v2 adapter, USB 3 connection, Linux USB permissions and driver installation. Close other programs using the sensor.
- Browser blocks the window: allow the local pairing popup, then retry. Do not disable browser security or expose the loopback service to the network.
Import an existing scene or recording
| Source | Browser support | Use this path |
|---|---|---|
| Gaussian PLY / SPZ | Import and explore | Choose the exported scene file |
| GLB / PLY mesh or points | Import and explore | Self-contained file; embed GLB textures |
| Kinect via USB | Live multi-view recording through the local connector | Open Studio → Capture → Connect Kinect |
| Handheld sessions | Import a stopped capture package | Transfer over your local network in Desktop compatibility, then export the session ZIP |
For a desktop project, export the folder containing studio-project.json and artifacts/, then ZIP that folder. For a raw capture, keep capture.json or manifest.json, all referenced frames and calibration together.
In browser Studio, choose Project settings → Export portable project to preserve scene assets, reference scale, camera and saved views. Import is local; uploading is a separate action.
Package validation and limits
The importer verifies paths, sizes and SHA-256 hashes. ZIP64, encrypted archives, links, missing files and modified artifacts are rejected. Capture ZIP limits: 128 MiB compressed, 256 MiB expanded and 12,000 entries. Keep original projects for workflows that require the Desktop compatibility workspace.
