Binary uplink takes audio chunks beside image frames (openpanel VS4)
This commit is contained in:
+6
-4
@@ -279,10 +279,12 @@ fresh snapshot.
|
||||
|
||||
With a `binary` uplink the device sends a camera frame as a binary message in
|
||||
the same layout, with the header `{"type": "frame", "name": "<message>",
|
||||
"media_type": "image/jpeg", "ts": <device ms>}`. The message has to be one of
|
||||
its `in` ports wired as `image`, and the whole message at most
|
||||
`MAX_FRAME_BYTES`. The frame is held in memory and published in one step,
|
||||
named after the message and credited to its device node. A frame that does not
|
||||
"media_type": "image/jpeg", "ts": <device ms>}`. A microphone's chunk travels
|
||||
the same way with a media type such as `audio/L16;rate=16000`. The message has
|
||||
to be one of its `in` ports wired as `image` or `audio`, the media type of
|
||||
that family, and the whole message at most `MAX_FRAME_BYTES`. The frame is
|
||||
held in memory and published in one step, named after the message and credited
|
||||
to its device node. A frame that does not
|
||||
qualify is dropped, the reason logged once per socket, and the socket stays
|
||||
open. With `http` it uploads with `PUT /artifacts?volatile=true&name=<message>`
|
||||
and publishes with `POST /messages/<message>`. A device that is unpaired or
|
||||
|
||||
Reference in New Issue
Block a user