On Friday 05 August 2011, Hans de Goede wrote: > > This sounds to be a good theme for the Workshop, or even to KS/2011. > > Agreed, although we don't need to talk about this for very long, the > solution is basically: > 1) Define a still image retrieval API for v4l2 devices (there is only 1 > interface for both functions on these devices, so only 1 driver, and to > me it makes sense to extend the existing drivers to also do still image > retrieval). > 2) Modify existing kernel v4l2 drivers to provide this API > 3) Write a new libgphoto driver which talks this interface (only need to > do one driver since all dual mode cams will export the same API). > > 1) is something to discuss at the workshop. > This approach sounds fine as long as you can come up with a definition for the API that covers the existing needs and is extensible when new cameras come along and doesn't create horrible inefficiencies by not matching the way some cameras work. I've only got one example of such a camera and it is a fairly basic one but things I can imagine the API needing to provide are 1) Report number of images on device 2) Select an image to read (for some cameras selecting next may be much more efficient than selecting at random although whether that inefficiency occurs when selecting, when reading image info or when reading image data may vary) 3) Read image information for selected image (resolution, compression type, FOURCC) 4) Read raw image data for selected image 5) Delete individual image (not supported by all cameras) 6) Delete all images (sometimes supported on cameras that don't support individual delete) I'm not sure if any of these cameras support tethered capture but if they do then add Take photo Set resolution I doubt if any of them support EXIF data, thumbnail images, the ability to upload images to the camera or any sound recording but if they do then those are additional things that gphoto2 would want to be able to do. Regards Adam -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
