Back to corpus
technical noteexperiment writeup candidatescore 44

Codex Handoff — MotionMix / ShootView / Still-Capture iOS Build

> Author: Claude (Mac1 session ff0dc14e), 2026-05-03 evening, US ET > Audience: Codex (next agent, fresh context) > Operator: Mohamed > Scope: finish the MotionMix multi-cam shoot stack so ShootView becomes the operator surface, iPhones produce max-resolution stills end-to-end, and Stage View is solid enough to ship.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> Author: Claude (Mac1 session ff0dc14e), 2026-05-03 evening, US ET > Audience: Codex (next agent, fresh context) > Operator: Mohamed > Scope: finish the MotionMix multi-cam shoot stack so ShootView becomes the operator surface, iPhones produce max-resolution stills end-to-end, and Stage View is solid enough to ship. The user explicitly decided **today, 2026-05-03**: **ShootView (iPad SwiftUI app) absorbs the Live Director role.** The native macOS `MotionMixDirector` Swift Package app is no longer the operator surface — it stays buildable as a fallback / debug tool, but ShootView is the canonical operator + photographer + gallery + reel + lookbook UI now. User quote: *"I, in fact, do not need the Live Director app itself, and I could actually direct my shoot through ShootView without any other external things."* Implication for you: do not pour effort into `Desktop/MotionMixDirector/` features. All operator-facing work goes into `Desktop/ShootView/`. | Host | Tailscale IP | LAN IP | Role | What's running right now | |---|---|---|---|---| | **Mac1** (MacBook Air M*) | varies | **[ip]** | Build host, multicam-server, mic capture | `multicam-server` :9404 (PID 72954+73358), `speakd` (PID 17419), `mic-pub` (PID 55971 → mac4:9540), `MotionMixDirector` native (built, may or may not be in the dock) | | **Mac4** (Mac mini M4) | **[ip]** | LAN | macOS-26 SpeechTranscriber relay + speakd remote-audio sink | `SpeechRelayApp` :9530 (PID 1313), `speakd` (PID 1339, mode = remote-udp:9540) | | **iPhone 16 Plus** | — | — | Primary capture node | UDID prefix `880B4058-F0B8-59EC-8693-7750C90BDB62` per `MotionMixApp/CLAUDE.md` | | **iPhone 16 Pro Max** | — | — | Secondary capture node | UDID prefix `84109044…` | | **iPhone 14 Pro Max** | — | — | Camera node (pose only) | UDID prefix `45896348…` | | **iPad A16 (Mohamed's)** | — | — | ShootView | UDID prefix `1DE6FABC…` | | **iPad A16** | — | — | ShootView (second) | UDID prefix `1938B9B3…` | | iPad (any) | — | — | Stage View (browser) | Safari → `http://[ip]:9404/program` (audience-facing live cut) |

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.