gPhoto

Libgphoto2 is the core library designed to allow access to digital cameras by external (front-end) programs, such as digiKam and gPhoto2. List of officially supported cameras is available on the official website (though more may work).

This article documents the configuration of libgphoto2 to access digital cameras. Some digital cameras will mount as normal USB storage devices and may not require the use of libgphoto2.

Installation

Install the libgphoto2 package, and optionally gphoto2 to have a command line interface.

Frontend applications
  • Darktable — Utility to organize and develop raw images.
https://darktable.org/ || darktable
  • digiKam — Digital photo management application for KDE.
https://www.digikam.org/ || digikam
  • Entangle — Provides a graphical interface for “tethered shooting”, aka taking photographs with a digital camera completely controlled from the computer.
https://entangle-photo.org/ || entangleAUR
  • gphotofs — Fuse module to mount camera as a filesystem.
http://www.gphoto.org/proj/gphotofs/ || gphotofsAUR
https://wiki.gnome.org/action/show/Apps/Gthumb || gthumb
https://wiki.gnome.org/Apps/Shotwell || shotwell

GPhoto2 usage

GPhoto2 is a command line client for libgphoto2. GPhoto2 allows access to the libgphoto2 library from a terminal or from a script shell to perform any camera operation that can be done. This is the main user interface.

GPhoto2 also provides convenient debugging features for camera driver developers.

Quick Commands

  • gphoto2 --set-config datetime=now - sets the camera to the current time

For advanced file manipulation, use

    Example usage with GVfs

    Auto detect the connected camera and list the required port:

    Now open your favorite file manager and enter the address with the found port detail . File manager functionality#Mounting will use gvfs to get the camera mounted and manageable with the file manager.

    Permission issues

    Users with a local session have permissions granted for cameras using ACLs. See General troubleshooting#Session permissions if it does not work.

    gollark: https://www.archmission.org/spaceil ← interesting real-life implementation of pretty long-term storage
    gollark: No, Intel stuff is affected by both, basically every modern one including ARM by spectre.
    gollark: I'm pretty worried about the effects of Spectre/Meltdown. Apparently Spectre, at least, affects basically all modern/high-performance CPUs, and can't be patched without large performance drops. It probably wouldn't have been an awful vulnerability to have around probably a few decades ago, but now basically everything executes some untrusted code (JS in browsers, cloud providers running people's workloads, etc.) Which probably means a significant security/speed tradeoff, and there's not really any right way for that to go...
    gollark: https://xkcd.com/2115/
    gollark: If you want to know, it's a picture of lemons.
    This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.