DeepLabCut / DeepLabCut/DeepLabCut-live-GUI

Add Hardware-trigger mode to gentl/basler backends

Open
#77 0 comments 0 reactions 1 assignee View on GitHub

@C-Achard is already working on this.

Since May 28, 2026.

  • #78 by @C-Achard — merged
camera config gui
Dominant language
Python
Stars
72
Forks
28
Avg merge
1d 10h
Merged PRs (30d)
2

Description

In certain scenarios its usefull to have the camera(s) run in a hardware - triggered mode instead of freerun.
That way one can exactly control when the cameras record the frames and at the same time enables a synchronization between cameras: all cameras receiving a trigger signal record their frames at the same time.

I would suggest different modes of hardware-trigger:

  1. fully external hardware-trigger - an external device will provide the TTL-like pulses to control the cameras. Simpler but requires external hardware.
  2. use one of the cameras as clock: this camera runs in freerun mode and outputs its ExposureActive signal via GPIO, other camera(s) are set in triggered mode and use the clock signal of the main camera.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.