Kicking off the discussion - Berry with Webcam

[btsimonh]

thankyou @Jason2866 for enabling discussions :).

Off the wall question:
The webcam features are available through 'Scripting' (here and here)

Scripting is the only mention of the motion detetion - it's not even a command.

What is the appetite for adding webcam to Berry? Is there some nepherious way to achive calling any tas native function? Can we get native buffers in berry through commands (e.g. does berry know about real addresses - can we pass such things between commands and berry, in order to pass a buffer?). i.e. Can we add webcan stuff to berry without writing berry native addons?

(i have ideas about things like looking at the SIZE of the jpeg for motion detect - which comes for free if we are encoding to jpeg - did this years ago for shotchange detect, and it worked really well. Whether it would detect a pidgeon landing near my pond is another matter....).

All thoughts appreciated :).

br,
Simon

[btsimonh]

following up on this, I've now tested providing address and length in a TAS command return, and using that in Berry to create a bytes object which references the native buffer. Berry can then use the buffer in normal 'bytes' ways - e.g. open a file and write the buffer to it, or probably HTTP POST it somewhere, all without re-allocation of memory (in this case 6-60 kbytes of PSRAM allocated buffer containing a jpeg image). Also pushing the fact a motion sense calculation has been done, and optionally that a frame has been received, into Berry.
Because the webcam driver is now heavily modified, I'll be following @Jason2866 's advice and creating a new driver, so people can choose between them. It will be a couple of weeks before I'm ready for public tests...