darktable-org / darktable-org/darktable
Teathered capture with Canon R6 MK II locks camera controls
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.1k
- Forks
- 1.4k
- Avg merge
- 22h 14m
- Merged PRs (30d)
- 198
Description
Is there an existing issue for this?
- I checked and did not find my issue in the already reported ones
Describe the bug
Opening a tethered capture session locks the camera controls limiting the usefulness of this feature. I dug around a bit and figured it was likely a problem with libgphoto2 and found an issue that seems to be the cause.
This issue for gphoto2 seems to indicate an additional flag on the start of the session may be needed for this model and a couple others. Setting disablemodedial to 0 looks like an option to try.
Steps to reproduce
- Connect camera via USB-C camera
- Open a teather capture
- Live view and controls work as expected on darktable but the local camera controls remain locked
Expected behavior
Open a session without locking the local camera controls
Logfile | Screenshot | Screencast
No response
Commit
No response
Where did you obtain darktable from?
darktable.org / GitHub release
darktable version
5.4.1
What OS are you using?
Linux
What is the version of your OS?
Arch rolling
Describe your system
No response
Are you using OpenCL GPU in darktable?
Yes
If yes, what is the GPU card and driver?
AMD Radeon via OpenCL with ROCM
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
No response
Contributor guide
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.
Research direction
Start by reproducing the tethered-capture session with a Canon R6 Mark II on Linux and review libgphoto2 issue 1210, especially the suggested disablemodedial setting. Trace the tethered-capture startup path in darktable to determine how the camera session is opened. Done means the session opens without locking the camera's local controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100