Skip to content

Take the first frame at the moment of motion, not after asking the cloud - #5

Merged
keyldev merged 1 commit into
masterfrom
feat/frame-at-motion
Oct 14, 2026
Merged

keyldev merged 1 commit into
masterfrom
feat/frame-at-motion

Conversation

@keyldev

@keyldev keyldev commented Oct 14, 2026

Copy link
Copy Markdown
Collaborator
  • The frame used to be taken only once the cloud had answered started: a TLS handshake or two, seconds on a camera, and a person walking past was out of the picture by then
  • Now majestic is asked for it as soon as the hook fires, and it goes out as frame 0 if the cloud wants frames; skipped once the cloud has said it wants none

- The frame used to be taken only once the cloud had answered `started`: a TLS
  handshake or two, seconds on a camera, and a person walking past was out of
  the picture by then
- Now majestic is asked for it as soon as the hook fires, and it goes out as
  frame 0 if the cloud wants frames; skipped once the cloud has said it wants none
@keyldev
keyldev merged commit 3e10154 into master Oct 14, 2026
7 checks passed
@keyldev
keyldev deleted the feat/frame-at-motion branch October 14, 2026 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant