Live mode
Run it on a live stream
Point a camera at a street, or share a browser tab that plays a live traffic stream. The detector and the tracker run on this device, up to 5 frames a second, and nothing is uploaded. Our event rules and the risk model are drawn for one junction in Tashkent, so they switch on only when the view matches our camera's.
Choose a source
For a live stream, open it in another tab and start it playing, then share that tab here. Keep this tab in front: browsers slow down pages in the background.
Checking what this browser can run
Risk, last 60 s
Events found
| Class | Start | End | Length |
|---|
How the live mode works
- The page asks for the camera, or for the tab or window to share, only when you press a button. Stop turns it off. Frames are read on this device and never sent anywhere.
- The pipeline is the one on the demo page: the YOLO26s detector at 960 px wide, on WebGPU where the browser offers it and on the CPU through WebAssembly elsewhere, then ByteTrack.
- It sends the next frame only when the last one is done, and at most 5 a second. A slower device runs at a lower rate instead of falling behind. The rate on the right is what this device manages.
- The tracker and the risk model are set for 5 frames a second, the demo's rate. At a lower rate, road users move further between frames and a lost track is kept for longer. So tracks, events and risk are closest to the demo's when the rate stays at 5.
- The first frame is lined up with our reference views of the junction. If it fits, the page also reads the signal lamps and runs the risk model, and at Stop it applies the event rules to the whole run. The rules need whole tracks, so events come at the end.
- On any other view the rules and the risk model would look in the wrong places, so the page only detects and tracks there.
- A run stops by itself after 10 minutes.