a8614a61dc
By having a pair of buffers, the capture hardware can fill one buffer while
Python code (including displayio, etc) operates on the other buffer. This
increases the responsiveness of camera-using code.
On the Kaluga it makes the following improvements:
* 320x240 viewfinder at 30fps instead of 15fps using directio
* 240x240 animated gif capture at 10fps instead of 7.5fps
As discussed at length on Discord, the "usual end user" code will look like
this:
camera = ...
with camera.continuous_capture(buffer1, buffer2) as capture:
for frame in capture:
# Do something with frame
However, rather than presenting a context manager, the core code consists of
three new functions to start & stop continuous capture, and to get the next
frame. The reason is twofold. First, it's simply easier to implement the
context manager object in pure Python. Second, for more advanced usage, the
context manager may be too limiting, and it's easier to iterate on the right
design in Python code. In particular, I noticed that adapting the
JPEG-capturing programs to use continuous capture mode needed a change in
program structure.
The camera app was structured as
```python
while True:
if shutter button was just pressed:
capture a jpeg frame
else:
update the viewfinder
```
However, "capture a jpeg frame" needs to (A) switch the camera settings and (B)
capture into a different, larger buffer then (C) return to the earlier
settings. This can't be done during continuous capture mode. So just
restructuring it as follows isn't going to work:
```python
with camera.continuous_capture(buffer1, buffer2) as capture:
for frame in capture:
if shutter button was just pressed:
capture a jpeg frame, without disturbing continuous capture mode
else:
update the viewfinder
```
The continuous mode is only implemented in the espressif port; others
will throw an exception if the associated methods are invoked. It's not
impossible to implement there, just not a priority, since these micros don't
have enough RAM for two framebuffer copies at any resonable sizes.
The capture code, including single-shot capture, now take mp_obj_t in the
common-hal layer, instead of a buffer & length. This was done for the
continuous capture mode because it has to identify & return to the user the
proper Python object representing the original buffer. In the Espressif port,
it was convenient to implement single capture in terms of a multi-capture,
which is why I changed the singleshot routine's signature too.
|
||
|---|---|---|
| .. | ||
| asf4@84f56af132 | ||
| asf4_conf | ||
| bindings/samd | ||
| boards | ||
| common-hal | ||
| freetouch@b6859a349e | ||
| modules | ||
| peripherals@d3b20192cf | ||
| sd_mmc | ||
| supervisor | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| Makefile | ||
| README.rst | ||
| audio_dma.c | ||
| audio_dma.h | ||
| background.c | ||
| background.h | ||
| eic_handler.c | ||
| eic_handler.h | ||
| fatfs_port.c | ||
| ld_defines.c | ||
| mpconfigport.h | ||
| mpconfigport.mk | ||
| mphalport.c | ||
| mphalport.h | ||
| qstrdefsport.h | ||
| reset.c | ||
| reset.h | ||
| samd_peripherals_config.h | ||
| shared_timers.c | ||
| shared_timers.h | ||
| timer_handler.c | ||
| timer_handler.h | ||
README.rst
SAMD21 and SAMD51
==================
This port supports many development boards that utilize SAMD21 and SAMD51 chips. See
https://circuitpython.org/downloads for all supported boards.
Building
--------
For build instructions see this guide: https://learn.adafruit.com/building-circuitpython/
Debugging
---------
For debugging instructions see this guide: https://learn.adafruit.com/debugging-the-samd21-with-gdb
Port Specific modules
---------------------
.. toctree::
../../shared-bindings/samd/index