Optional camera module: phone as shot camera#33
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second half of the Discord video request. MATEBOT_CAMERA=1 starts an aiohttp server (no new deps) serving a self-contained phone page: getUserMedia rear camera, screen wake-lock, live preview, armed/recording states, auto-reconnecting WebSocket. The bot detects shot start/end on the live status stream and commands the page to record; MediaRecorder chunks stream up the socket, get a 5s tail, and land in the video pipeline from #32 (ffmpeg transcode, sidecar offset, prune, journal sync playback). Clip/shot-id arrival order is racy, so a rendezvous attaches whichever side completes second. Best-effort: no page connected means no recording and no errors. HTTPS requirement (getUserMedia) documented with reverse-proxy and tailscale-serve recipes.