.shock.LAB · camera
.camera.shock
In Development
Tethered shooting, straight into the pipeline.
The outcome .camera.shock delivers.
In the browser today, .camera.shock captures from a connected webcam and writes every frame to local storage — sequence number, timestamp, camera settings, keep/cut flag, 0–5 rating and colour label — so the review pass runs in the same window as the shoot, session by session. Nothing waits for a card to be pulled and ingested at the end of the day. Captures are not uploaded unless you switch on library sync in the app; with it on and signed in, they also go to your own asset library so cull and the modules after it can pick them up. Two requests leave the browser on their own: a thumbnail of each capture is posted to the .shock face-detection service to count faces, which is what raises the model-release flag on a frame, and the AI helpers — shot lists, session names, caption drafts — send their text prompts to the .shock server. Tethered capture from a camera body is specified but not yet available, so the app falls back to the webcam.
- No import step — each capture lands straight in the local session store, with no card pull or end-of-day ingest.
- Review while you shoot — keep/cut flags, 0–5 ratings and colour labels can be set mid-session.
- Named sessions from the first frame — captures stay grouped in the session structure the rest of the workflow reads.
- Exposure feedback while framing — live histogram and highlight zebras over the viewfinder.
- Exports carry their metadata — EXIF written on export, alongside a ZIP manifest for the session.
- Tethered capture is not yet available — the tether toggle stays disabled and capture falls back to the webcam; this runs in a browser tab, not a native desktop companion.
Built for the photographers who need it.
Studios that want the review pass to start during the shoot rather than after it. Today that means capturing from a webcam in the browser and setting keeps, cuts and ratings as the session runs, so the team reviewing on set is working from frames already in hand. The cabled-body workflow this module is designed around is not available yet.
Where .camera.shock fits.
Sits on the main line on shoot day, feeding captures straight into the cull. The tethered step it is designed around is not yet available. Built in the spirit of the Phase One SDK, with no affiliation implied.
What you get on each plan.
Tethered shooting, straight into the pipeline.
Part of the .shock.LAB — one workflow from brief to paid.