You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Canon M50 Mark II and R100 sporadically take >6 seconds to capture the image and issue a "file added" event. It happens every couple of hours on cameras that are being actively used to take photos throughout the day. After the issue occurs, cameras just go back to normal until malfunctioning again.
Name the camera
--auto-detect shows it as "USB PTP Class Camera"
libgphoto2 and gphoto2 version
gphoto2 2.5.28 gcc, popt(m), exif, no cdk, no aa, jpeg, no readline
libgphoto2 2.5.31 standard camlibs (SKIPPING docupen lumix), gcc, no ltdl, EXIF
libgphoto2_port 0.12.2 iolibs: disk ptpip serial usb1 usbdiskdirect usbscsi, gcc, no ltdl, EXIF, USB, serial without locking
To Reproduce
I trigger the capture with --set-config eosremoterelease=5, then I issue a --wait-event for "file added". I am using the Python bindings.
The camera operates in Servo AI / Continuous AF mode with remote release to avoid autofocus errors. Captures are supposed to be instant, and they are on my unit. However, cameras I have in the field consistently experience it. I am attaching a few log files from the same camera with timestamps which you could use to understand this behavior. Is this an edge case or a bug? Is there a solution for it?
Describe the bug
Canon M50 Mark II and R100 sporadically take >6 seconds to capture the image and issue a "file added" event. It happens every couple of hours on cameras that are being actively used to take photos throughout the day. After the issue occurs, cameras just go back to normal until malfunctioning again.
Name the camera
--auto-detect shows it as "USB PTP Class Camera"
libgphoto2 and gphoto2 version
gphoto2 2.5.28 gcc, popt(m), exif, no cdk, no aa, jpeg, no readline
libgphoto2 2.5.31 standard camlibs (SKIPPING docupen lumix), gcc, no ltdl, EXIF
libgphoto2_port 0.12.2 iolibs: disk ptpip serial usb1 usbdiskdirect usbscsi, gcc, no ltdl, EXIF, USB, serial without locking
To Reproduce
I trigger the capture with --set-config eosremoterelease=5, then I issue a --wait-event for "file added". I am using the Python bindings.
The camera operates in Servo AI / Continuous AF mode with remote release to avoid autofocus errors. Captures are supposed to be instant, and they are on my unit. However, cameras I have in the field consistently experience it. I am attaching a few log files from the same camera with timestamps which you could use to understand this behavior. Is this an edge case or a bug? Is there a solution for it?
cap_err_13_36_26_03_11_2024.log
cap_err_14_40_35_04_11_2024.log
cap_err_18_39_10_02_11_2024.log
cap_err_19_39_14_04_11_2024.log
cap_err_21_07_01_02_11_2024.log
cap_err_23_06_11_03_11_2024.log
cap_err_09_39_05_04_11_2024.log
The text was updated successfully, but these errors were encountered: