A fortieth of a second. Then the hard part.
Anyone can take the photograph. SnaptureX runs everything after the shutter — the cameras on the ride, the pipeline that renders what they catch, the till, the printer, the hand it ends up in — across every venue you operate, from one console.
- Capture
- LIVE
- Capture setting
- CAM-07
- Capture setting
- GATE 3
- Capture setting
- f/2.0
- Capture setting
- 1/2000 s
- Capture setting
- ISO 3200
- Capture time
- 21:47:06.412
The face is lit for one frame.
Attraction photography is not a photography problem. It is a timing problem wearing a camera, and the three constraints below are all true at the same moment.
- One frame
- A dark ride at sixty kilometres an hour gives you a single usable exposure per guest. There is no retake — the train has already gone.
- Four minutes
- The walk from ride exit to shop door. The render has to be finished, priced and on a screen before they reach it, or it sells to nobody.
- Sixteen hours
- Gates open to gates closed, every day of the season, at every venue at once. The pipeline never gets a maintenance window.
Matched to a rider, priced against the venue’s catalogue and queued to the shop’s printer before the train finished braking.
Five stages. Everyone else sells you three.
A device manager stops at capture. A render farm starts and ends in the middle. A point-of-sale system joins at the till and has never heard of a camera. The seams between them are where a park’s media revenue leaks, and nobody owns the seam.
- 01
Capture
Cameras and photographers are owned by a venue and deployed to the leaf location that actually uses them. Capture settings are configured per location, versioned, and pushed to the box in the park.
- 02
Render
Frames go into the pipeline and come out as products — profiles, composition layers, generated video. The queue is visible while it runs and the failures are addressable, not silent.
- 03
Sell
Products, packages, availability and prices, set per venue. Point of sale with its own staff, payment methods and tills, because the commercial layer is part of the system rather than a bolt-on beside it.
- 04
Deliver
Printer pools resolve down to the leaf that uses them. Fulfilment endpoints route a job to a machine. A print knows which counter it is going to before anyone walks to it.
- 05
Reconcile
Takings, closing, media mix, order value, upload health. What was captured, what sold, and what never arrived — which is the number nobody else can give you, because they never held the capture end.
One console. Every venue. No crossed wires.
Multi-tenant is easy to claim and expensive to get wrong. These three are enforced in the data layer, not in a review checklist — which is the only version of the promise that survives a busy Saturday.
Scope is explicit, every time
Every read carries the operator and the venues they may see. There is no ambient current tenant and no module-level default, so a screen cannot quietly serve one operator another operator’s data.
Assets cannot cross a venue
A camera is owned by a venue and deployed to a leaf beneath it. A deployment that would put one venue’s hardware in another’s location is refused at the write, not caught in a report later.
Yesterday stays yesterday
A transaction freezes its site, business date and configuration version at the moment of capture, and they are never recomputed. Last season’s numbers do not move when this season’s settings change.
Bring us your estate.
Every park runs its media differently — different rides, different tills, different rules about what a print costs on a wet Tuesday. An evaluation starts with your hierarchy loaded and your prices in it, not with a generic sandbox that proves nothing about your operation.