DeepLabCut / DeepLabCut/DeepLabCut-live-GUI
Plugging in a new camera creates a duplicate ID
@C-Achard is already working on this.
Since Jun 26, 2026.
- Dominant language
- Python
- Stars
- 72
- Forks
- 28
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
Context
Originally reported by @arturoptophys
Plugging a new camera while the GUI is running (or maybe also viewing) gives the new camera a colliding id (so there are 2 cameras with id 1)
which still works with the display (all 4 cameras are displayed) but the recording is missing one video.
Overall minor issue which is solved by restarting the GUI.
Missing information
- Is this backend specific or Basler/GenTL only?
- Confirmed not to occur on OpenCV
- Does this persist at camera configuration time? And after device list refresh?
Potential fix
Device-specific machine IDs that disambiguate cam indices are already implemented. This may simply be a wiring issue in recording file naming, rather than a duplicate device indexing issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.