From f31fb447f41c5e3556dafffad0d2e7bae71027cb Mon Sep 17 00:00:00 2001 From: Juan Cobo Betancourt Date: Sun, 13 Sep 2026 18:35:15 -0500 Subject: [PATCH] docs: say plainly that nothing falls back from streaming capture The known-limitations note claimed the library falls back to SD card capture when streaming fails on the A2500. It does not: shoot(stream=True) goes to _shoot_streaming and raises, and nothing calls _shoot_standard after it. A caller reading that line would plan for a fallback that was never written. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 056376e..bace027 100644 --- a/README.md +++ b/README.md @@ -156,7 +156,7 @@ tools/ ## Known limitations -- **Remote capture on A2500**: The A2500 CHDK port is alpha-level. Streaming remote capture (`shoot(stream=True)`) may fail with PTP error `0x2002`. The library falls back to SD card capture (`shoot()`) which triggers the shutter but stores images on the card rather than streaming them back. +- **Remote capture on A2500**: The A2500 CHDK port is alpha-level. Streaming remote capture (`shoot(stream=True)`) may fail with PTP error `0x2002`, and nothing here falls back on its own: `shoot(stream=True)` raises, and a caller that wants the picture anyway has to call `shoot()` itself, which trips the shutter but leaves the image on the card rather than streaming it back. Whether the A2500 fails this way in practice has not been established against hardware. - **macOS only** for `tools/flash_chdk.py`. The library itself works on macOS and Linux. - **Canon cameras only** — CHDK is Canon-specific. Device discovery defaults to Canon's USB vendor ID (`0x04A9`).