Open bkapadia01 opened 2 years ago
Does anyone have any suggestions on how to fix this issue?
We spent a long time investigated what we are observing, thinking it was something we were doing wrong, but we realized what was causing the wrong cameras to be triggered we attributed to how the gphoto2 trigger commend works with the USB port parameter.
i added some more error code handling, especially for fully invalid ports.
however --port usb:xxx,yyy if the combi is invalid, will still fallback to the first valid port
ok, some more code added ..
--port usb:002,007 now fails if there is only usb:002,008
lets hope i did not break any usecases relying on this lax detection ;)
Understand. Thanks. I'll try this fix on our development Mac and let you know how it goes.
Describe the bug The trigger and capture command seems to accept any value for the
-port
portion of the script which is causing the camera to be triggered when an invalid port value is provided. This is causing an issue when we have more than one camera mounted to the system where the incorrect camera is being triggered when it should not be.Name the camera Camera name as shown by gphoto2 --auto-detect or USB IDs Canon EOS 5DS R
libgphoto2 and gphoto2 version output of: gphoto2 --version libgphoto2 2.5.27
To Reproduce Steps to reproduce the behavior: The usb port when running gphoto2 --auto-detect for a camera is:
Canon EOS 5DS R usb:020,013
Running command with invalid port
-port x
, note the camera should not be triggered.gphoto2 --port x --filename TOP_%H-%M-%S.%C --set-config eosremoterelease="Immediate" --set-config eosremoterelease="Release Full" --wait-event-and-download="FILEADDED"
When reproducing with the command line tool, attach debug out using --debug --debug-logfile=debug.log if considered useful