Signal view

Checking whether the camera, network or recorder is damaging the DataBorder.

The signal view is a protocol analyzer for the DataBorder. Switch to it with the signal toggle in the timeline header.

The decoder analyzes the selected clips on demand and shows a progress line with a stop button.

Lanes

The signal view over ten seconds of a clip: the frames, updates, records per update, payload, corrections, margin and worst-codeword lanes.The signal view over ten seconds of a clip: the frames, updates, records per update, payload, corrections, margin and worst-codeword lanes.
The signal view over ten seconds of a clean clip.
LaneMeaning
framesOne mark per frame: decoded, unrecoverable, or dropped in transport. Keyframes carry a tick. A healthy stream is one unbroken bar of decoded frames.
updatesOne stripe per DataBorder update. A stripe is wider when the camera held the update for longer than usual. Sequence gaps are red.
records per updateHow many records each update carried. The tall bars are full snapshots, which arrive every few seconds. The low bars in between are deltas.
payloadThe update's bytes, top to bottom, colored by layer, so you can watch the carousel cycle. Hover over a layer in the legend to isolate it.
corrections and failuresThe symbols that the error correction fixed, by position around the ring: top edge, sides, and bottom edge. Blank means clean. A failed codeword is a red column.
marginThe contrast between light and dark blocks. Above 60 is clean. Below 40, the decoder falls back to a slower threshold method.
worst codewordThe number of symbols corrected in the worst codeword of each update. Six is the limit. At seven, the codeword fails.

The help button next to the toggle explains each lane in place, with a sketch.

Patterns

The findings list under the chart adds up the totals and points to the likely cause. The common patterns:

  • Falling margin with rising corrections means that a recorder or a stream profile is compressing too hard. Raise the bitrate on the profile the recorder uses, or record a different profile. See Recording.
  • Corrections concentrated in one stretch of the ring, a hot spot in the findings, usually mean that something is drawn over the ring there. Common causes are the camera's clock, a text overlay, or a fixed element in a screen recording. Move it off the border.
  • Dropped frames, and sequence gaps the findings attribute to transport, point to the network path rather than the picture.
  • Updates held longer than usual, and sequence gaps attributed to the camera, mean the camera skipped a DataBorder refresh. This is load on the camera rather than a fault in the stream. See Performance.
  • A clean signal with values that look wrong is not a signal problem. Check the tag configuration on the camera.

The frame inspector

Click on the signal view to place the cursor. The at cursor panel then becomes a frame inspector for that frame. It shows whether the DataBorder decoded and by which method, the margin, the corrections per codeword, the update's flags and fragments, the payload as a grid of bits, and a hex dump colored by layer. A frame whose codeword failed shows no bytes at all, because the decoder never displays data it could not validate.