Photogrammetry

Photogrammetry capture features

Available controls depend on the camera model, connection, platform and selected license. Check the supported-camera guide and test the complete array before a production session.

Multi-camera control

• Adjust ISO, aperture, shutter speed, white balance and image quality from one interface where supported.
• Auto-focus compatible lenses together, then inspect framing and focus camera by camera.
• Use live view and optical or digital zoom where the camera and adapter support them.
• Number cameras in capture order and check their identities before shooting.
• Capture JPG or RAW+JPG when you need image previews and processing. RAW-only capture is available when you only need source files; JPG previews are no longer extracted from RAW files.

Current capture and RAW guidance

Synchronized triggering and capture sequences

• Trigger supported cameras over USB without separate camera trigger cables.
• Warm up the rig before capture, including half-press and mirror lockup on supported bodies.
• Use Timeline scripts for repeatable camera, light and timing steps.
• Use buffered multiple-shot or burst capture where supported for ROM (range of motion) and OLAT (one light at a time) sessions.
• Measure synchronization with the complete rig. Camera latency, shutter behavior, exposure duration, warmup and the trigger path all affect the captured result; there is no universal sub-millisecond guarantee for every setup.

Capture sequences - Measuring trigger synchronization

Networked multi-camera capture

• Plan systems of up to 1,000 cameras according to the license, supported adapters and validated hardware capacity.
• Connect compatible cameras directly to a Windows computer over USB, or distribute connections across supported Raspberry Pi and Windows camera nodes.
• On Mac, direct USB supports one Canon camera; use Raspberry Pi camera nodes for additional Canon cameras. Other camera families have their own platform and adapter limits.
• Choose node count from measured power, USB bandwidth and transfer requirements. Twenty-four cameras per computer and four per Pi are rig-layout examples, not universal limits.
• Avoid assuming that different camera models have matching settings, exposure timing or color. Test mixed arrays before relying on them.

Camera compatibility - Raspberry Pi and network setup

Automatic photo download and transfer performance

• Transfer captured images automatically and prepare datasets for review.
• Use a suitable wired network for distributed capture. Gigabit Ethernet means 1 Gbps; a 10 Gbps uplink can carry more concurrent node traffic when the switch, computer and storage can keep up.
• Test with the intended camera count, resolution and JPG or RAW+JPG settings. Larger files increase transfer, preparation and storage time.
• Keep the working folder on a fast local SSD and use performance monitoring to identify the slowest stage.
• Treat published studio benchmarks as configuration-specific examples, not guaranteed turnaround times for another rig or software version. Older RAW benchmarks included JPG extraction, which is not part of the current RAW capture path.

Studio benchmarks - Finding transfer and processing bottlenecks

Browser-based review and control stations

• Use supported browser stations on devices that can reach the Camera Server computer over the local network.
• Configure stations through Devices rather than relying on legacy fixed-port URLs.
• Separate browser stations on phones, tablets or computers require Pro or Pulse. Basic and higher can show replay or sharing tiles on a monitor connected to the server computer.

Device and station setup

Dataset and individual-camera review

• Review capture sets in Library, with ratings and comments.
• Compare camera views in Frames to check focus, exposure, framing and missing images before the subject leaves.
• Use a preview grid for a quick overview, then inspect original images for fine detail.
• Review individual iterations of burst captures and choose the intended main view.
• Configure selected camera views or separate review screens where the license supports them.

Frames previews and image review

Monitoring and troubleshooting

• Check disconnected cameras and the connection status of Raspberry Pi and Windows camera nodes.
• Use node-management controls to inspect versions and perform supported updates or restarts.
• Monitor disk space, transfer and processing performance, and reported errors before continuing a session.
• Test a complete capture, transfer and review cycle after changing the rig.

Setup and troubleshooting support

File naming, datasets and automatic backups

• Configure original-file, processed-file and dataset-folder names using templates and capture values.
• Use custom fields and preset values for actor names, scan identifiers or FACS (Facial Action Coding System) expression labels.
• Configure automatic dataset copies to folders accessible from the server computer, including suitable external drives or mounted network storage.
• Choose the files and camera numbers to include in each backup entry, and use multiple destinations when required.
• Check backup logs and the copied files before deleting working data. Naming and backup capabilities depend on the selected license.

Current Camera Server documentation

Strobes, flashes and cross-polarized scanning

• Coordinate supported flash-control hardware with the capture sequence and test flash timing against the camera exposure.
• Prepare the lighting and optical equipment required for cross-polarized photogrammetry. Polarization is a lighting-and-filter setup, not a software-only reflection-removal feature.
• Test the complete camera and lighting system for consistent exposure, timing and image quality.

Video capture

• Capture video on supported cameras and adapters; availability is not limited to Canon.
• Check each model's video modes, storage requirements and transfer behavior instead of assuming that photo support implies video support.
• Test the intended recording and download cycle across the full array.

Supported models, platforms and capture modes

LED control

• Use supported lighting controllers and presets to coordinate LED states with the countdown and capture.
• Prepare focusing light, exposure light and post-capture states appropriate to the rig.
• Use Event scripts for countdown and capture cues, and Timeline scripts for repeatable steps. Test reset and cancellation behavior before a session.

Event scripts and capture cues

API access and capture automation

• Use the Camera Server API for supported remote operations such as triggering, changing camera settings and retrieving camera information.
• Use Timeline and Event scripts to coordinate repeated capture steps and external cues.
• Check the installed version's API documentation and license requirements before connecting an external system.

Explore the full feature list

Equipment and system requirements

• Computer: Camera Server is available for Windows and macOS. Choose a fast local SSD and enough CPU, memory and network capacity for the intended capture and output tasks. Check each local processing engine's separate operating-system and GPU requirements.
• Cameras: choose exact models from the supported-camera list. Canon, Sony, GoPro, iPhone, Android and Raspberry Pi camera paths have different capture modes, host requirements and limitations.
• Connections: a smaller Windows rig can use suitable USB controllers or powered hubs. For larger arrays, distribute supported cameras across network nodes. Direct USB on Mac supports one Canon camera; additional Canon cameras need Raspberry Pi nodes.
• Nodes and network: size the camera groups, switches, uplink and storage from measured load. Follow the current Pi image and node-package instructions. A cardless boot-server network must be isolated from other DHCP servers; it is not a plug-in-any-router setup.
• License: camera count, network nodes, browser stations, scripting, naming and backup access depend on the selected license. Confirm the required tier and camera count before a production session.

Required gear - Network setup guide

Getting started with a photogrammetry rig

1. Request a trial for evaluation, or choose a production license.
2. Download Camera Server for your platform and check camera compatibility.
3. Connect supported cameras directly or through prepared network nodes, then number them in capture order.
4. Configure subject and capture-set naming, storage and any required backup destinations.
5. Aim the cameras, set exposure and white balance, and check focus across every view.
6. Rehearse the intended camera and lighting sequence, then trigger a test capture.
7. Confirm image transfer, inspect the dataset in Library and Frames, and test the intended reconstruction or output stage.

Trials are for evaluation, not production events. Review the current trial and licensing FAQ before planning a session.

Watch a full capture session from our Montreal studio: