Burst

Capture a short native continuous sequence from the camera

Burst captures a fast sequence of still images from the connected camera body. Use it when you want the camera to run its own continuous shooting behavior. Use Pulse instead when you need app-controlled timing between individual captures.

Page controls

  • Images is the requested number of images in the burst. The maximum follows the connected body's current continuous-shooting limit when the body reports one.
  • Speed is currently Camera default. The camera body and release-mode settings decide the actual drive speed.
  • Start begins the Burst run.
  • Cancel appears only when the active camera path reports that Burst can be cancelled.

The Images value is saved with the current profile. The app also synchronizes the Images value with the body's continuous-shooting number when the connected body supports that setting.

Before you start

Burst can start when the camera is connected, the connection is not changing, the body supports capture, and no other workflow is running. If the normal Shoot command is not ready, Burst is not ready either.

Check the Body controls before starting a run. Burst uses the current camera settings, including exposure, image quality, body destination, and storage path.

Some bodies require release mode or drive mode to be set to a continuous option on the physical body or body menu before pressing Start. Some providers can set the continuous-shooting count remotely when the body supports it. Others rely on the camera body's current release-mode setting.

Running Burst

  1. Connect the camera.
  2. Set the camera exposure, image quality, destination, and release-mode options.
  3. Open Workflows/Burst.
  4. Set Images.
  5. Select Start.

The app shoot/status area reports Burst progress. When the body and provider finish the continuous capture, the status changes to Burst complete.

If the camera is set to save more than one file per exposure, each requested image can produce multiple final files for the same capture.

Cancelling

Continuous shooting cancellation depends on the camera body, provider, and timing. Once a continuous Burst has started firing, some bodies or providers cannot reliably interrupt the active run.

When cancellation is supported, Cancel requests that the active Burst run stop. When cancellation is not supported, the page may hide Cancel or wait for the body to report that the continuous capture has completed.

Saving Burst runs with Path

Burst works well with Path templates that use the group timestamp token. Use @GRP when all files from one Burst run should land in the same generated folder.

For example:

c:\images\burst\@GRP\@GCT4

Each Burst run receives a fresh group timestamp when it starts. Single-file Burst saves advance counter tokens once per image. Multi-file Burst saves advance counter tokens once per complete image group, so paired or grouped files share the same final base name.

Use @UGRP instead when the run folder should use Coordinated Universal Time. Open the Path help page for the full token reference and more destination examples.

Capture safety

When Burst saves to the computer, the app treats each expected save as part of the capture workflow. The app does not treat the Burst run as complete until the expected final Path output is saved and verified.

Some providers use a staging area before files are copied to the final Path destination. Others stream files directly to the app for final save. If a required save check or final Path copy fails, the app shows a capture failure, withholds successful workflow completion, preserves any recovery files that are available, and cancels pending Burst workflow commands.