SonyShell – An effort to “SSH into my Sony DSLR”

Original Article ↗ Hacker News Discussion ↗

Project behavior & capabilities

  • Tool mimics an SSH-like session to Sony mirrorless cameras over Wi‑Fi using Sony’s official Camera Remote SDK.
  • It currently watches for new photos or events and runs user scripts; shutter/focus/aperture control via CLI is not yet fully implemented but is considered easy to add and early patches exist.
  • Main motivation: a6700 lacks built‑in FTP, and this approach offers more flexible automation than just file transfer.

Use of ChatGPT & C++ implementation quality

  • Some praise the project as a fun one‑day hack and a good excuse to revisit C++.
  • Others criticize the AI-assisted code: path handling mixing Windows/Linux, questionable signal safety, weak unique filename generation, unnecessary copies, and non‑compliance with XDG directory conventions.
  • Suggestions include using modern C++ features (e.g., std::filesystem::exists) and generally cleaning up for robustness.

DSLR vs mirrorless terminology debate

  • Large subthread disputes calling the a6700 a “DSLR”.
  • One side: mislabeling basic hardware undermines trust in the project; DSLR has a precise technical meaning (digital + single‑lens + reflex mirror).
  • Other side: for non‑specialists, “DSLR” is colloquial shorthand for “big interchangeable‑lens camera”; for this software, the key characteristic is API access, not the viewfinder mechanism.
  • Discussion expands into camera taxonomy (rangefinder, mirrorless, medium format) and whether any type is “inherently better”; consensus is that comparisons often conflate unrelated attributes (viewfinder mechanism, sensor size, lens design).

Brand naming & legal worries

  • Several commenters warn against using “Sony” in the project name for trademark reasons; the repository is renamed accordingly while maintaining redirect.

APIs, Wi‑Fi, and tethering across brands

  • Survey of vendor APIs: Canon and Sony have official APIs; Fujifilm’s exists but may be warranty‑sensitive; Blackmagic has REST for higher‑end models; some Pentax and Olympus/OM cameras also support remote control or tethering.
  • Many complain that Wi‑Fi features across brands are slow, unreliable, or awkward (AP mode vs STA mode, flaky phone apps).
  • Some still prefer SD‑card workflows; others lean on FTP, USB PTP, or tools like darktable/gphoto when they work.

Security & access model

  • Current implementation effectively exposes camera photos to anyone on the same network; authentication is planned.
  • There is speculation about whether the camera uses SSH internally, but the project itself only uses the official SDK, not a real shell.

Hacking, rooting, and prior projects

  • Commenters reference earlier Sony hacks (OpenMemories, PMCA-RE) and note that modern Sony firmware seems much more locked down.
  • Samsung NX cameras are cited as historically very hackable (Tizen-based, SSH access, persistent mods, extensive reverse engineering).
  • Some argue that even with a root shell on modern cameras, meaningful deep image‑pipeline modifications are extremely hard due to proprietary DSPs and complex real‑time systems.

Desired features & future directions

  • Requests include: safe PAL/NTSC region tweaks, ETTR‑oriented metering, focus stacking, advanced time‑lapse, and better wireless live review for clients during shoots.
  • Several people express hope that this project could evolve beyond Sony/mirrorless over time, similar to how other projects (e.g., media centers) outgrew their original hardware focus.