Closed spiderkeys closed 1 year ago
The path is returned by the libgphoto2 library from gp_camera_capture, it is not an input parameter.
This path is a path into the virtual libgphoto2 filesystem. After downloading it from the virtual filesystem you can select your own folder and filename where to save the image to disk.
(e.g. this is what gphoto2 --filename "..." option is doing)
Understood for capturetarget==sdram
. When capturetarget
is set to "card", is there any way to influence the filename written to the SD card (i.e. Pathname on the camera: /store_00020001/DCIM/100FOCUS/021A6916.JPG
), or is that purely camera vendor controlled?
the on camera path is entirely controlled by the cameras, have not seen any camera that allows configuration of it.
Thanks, will close this issue then!
Is there a limitation with the PTP capture interface for most cameras that requires libgphoto2 to ignore the path provided by the user to
gp_camera_capture()
and instead generate the/captXXXX.Y
folder/filename pattern?I would like to be able to explicitly set this filename (folder too, if possible), specifically for the purpose of being able to include a timestamp and other metadata in the filename, such that it can be later correlated to some sensor data in post-processing (with millisecond resolution, as opposed to the 1 second resolution possible through using the time sync APIs).
If there is no strict limitation or requirement for the files to match this format, that would be helpful to know. I can imagine scenarios where the camera itself might have some expectation/requirement for the directory and filenames to match these specific patterns, but I thought I'd check before making any modifications.
Thanks