Note 0013 min read
A click, a tile, and a device that answers
A tile, a controls diagram, an ESP32 board that relays a camera picture, and a feeder design that is not on a board yet.
A tile is one picture in a grid. Some tiles are cameras. A tile of color bars means no board answered. That picture is a test pattern. It is not a camera.
This note is the simple version of three pieces. They do not all do the same job yet.
Camera
HTTP
XIAO ESP32-S3
MoQ
Tile
#What MoQ is
MoQ is Media over QUIC. It is how these live pictures move. A track is one named stream. You subscribe to a track to watch it.
Watching does not send a command. The public bench says MoQ has no back channel. If you want to send input, you publish too.
#The grid
colorbars.dev is the public bench. The product name there is MoQ Studio. moqstudio.dev is the player SDK and tokens.
The controls page is colorbars.dev/controls. It is a diagram. Media comes down. Input goes up.
A related page can fill a mock grid from announcements. That mock grid is not the live events desk.
#What a press is
The controls diagram says this, step by step:
- A machine publishes video and audio. You subscribe to watch.
- To send input, you publish on your own path, with one controls track.
- A press writes JSON. A held button is true. A wheel can write numbers, such as steer, throttle, and brake. The shape of that JSON belongs to the application. This is the shape the bench describes, not a captured message:
{
"steer": 0,
"throttle": 0,
"brake": true
}- The machine chooses which controls tracks to read. It can read all of them, one of them, or none. The relay does not merge the JSON.
- The picture and the JSON share a timestamp. On a tight link, controls go out before audio, then notes about the stream, then video.
That is the control path on the page. It is not a live wire to a board.
#The board
On the bench, a XIAO ESP32-S3 is the relay. It asks a camera for a JPEG over HTTP, at /capture. It publishes that JPEG on a MoQ track, camera.hang. It accepts one subscriber.
A script on the desk can hold that one session and publish a copy. More than one viewer can then watch the copy.
The bench notes list two camera paths. The second camera path is not written yet. The same notes say launch is no. This is a bench, not a finished product.
One of the relays can also take motion samples over Bluetooth from a smaller board. The laptop does not open Bluetooth itself.
#The feeder
The feeder is a separate design. The current layout is a printable head, version 11. It is meant to sit on an existing hopper.
The controller firmware is source only. It has not been compiled for a board. It has not been flashed. It has not been connected to a device. The pin map is unconfirmed.
#Why the picture and the press share a clock
The controls note says the picture and the JSON share a timestamp. On a tight link, the press goes out first. You want the command and the picture to belong to the same moment.
The bench records ages and grades. I am not adding a target number here. The status line that matters is the one the bench already wrote: launch is no.
#Where to look
- moq.dev for the protocol
- colorbars.dev for the bench
- colorbars.dev/controls for the controls diagram
- moqstudio.dev for the player SDK and tokens
colorbars.dev and moqstudio.dev ask for a sign-in.
The hobby projects are on Projects. They are for fun and learning. They are not for sale.
Built on MoQ from moq.dev. This is independent hobby work, not affiliated with or endorsed by MoQ.