Pulse captures a sequence of images from the connected camera body. Use it when you want a simple repeated-capture run with a fixed count and interval. You can cancel an active run, and the app shoot/status area shows progress as each capture is requested.

Page controls

  • Images is the number of captures to make. It accepts 1 through 999 images.
  • Interval is the target number of milliseconds between capture starts. If the camera is late, the next capture starts when the camera is ready.
  • Start begins the Pulse run.
  • Cancel requests cancellation of the active Pulse run.

The Images and Interval fields are disabled while Pulse is running. They are saved with the current profile, so a profile can keep its own Pulse count and interval.

Before you start

Pulse 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, Pulse is not ready either.

Check the Body controls before starting a run. Pulse uses the current camera settings, including exposure, image quality, body destination, and any other capture settings already active on the body.

Running Pulse

  1. Connect the camera.
  2. Set the camera exposure and destination options.
  3. Open Workflows/Pulse.
  4. Set Images.
  5. Set Interval.
  6. Select Start.

The app shoot/status area reports the current step, such as waiting for the next capture or capturing a specific image in the run. When the final capture has finished, the status changes to Pulse complete.

Cancelling

Select Cancel when you want to stop an active run. Cancellation stops the remaining Pulse captures and interrupts interval waits. If a capture has already started, the camera may still need to finish the active capture or transfer before the app is ready for the next command.

After cancellation, you can adjust Images or Interval and start a new Pulse run when the camera is ready again.

Saving Pulse runs with Path

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

For example:

c:\images\pulse\@GRP\@GCT4

Each Pulse run receives a fresh group timestamp when it starts. If you cancel a run and immediately start another, the next run still receives its own group timestamp, so its files do not mix with the previous run.

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.