image

Pixel-array image data. Reserved dtype — the default timeline views map has no entry for image yet. Images are typically served outside the m3u transport (direct S3 links, CDN) rather than embedded per-sample.

Chunk format

• Format: typically jsonl with base64-encoded pixels, or a sidecar reference pattern
• Decoder: user-supplied

Recommended shape

If embedding pixels directly (slow, high bandwidth):

{
  ts: number
  shape: [H: number, W: number, C: number]  // e.g. [480, 640, 3]
  data: number[]                            // flattened row-major
}

For production use we strongly recommend storing image frames as HLS video (use dtype: 'video') or as a companion object-store reference:

{
  ts: number
  url: string   // "s3://bucket/frames/0001.jpg"
}

Compatible timeline lanes

No stock lane. Provide one in views:

const views = {
  ...defaultTimelineViews,
  image: { lane: MyImageFilmStripLane, icon: 'video', defaultHeight: 72 },
}

Compatible standalone views

— (not shipped)

Default props

None.

Why it's reserved

Embedding full-resolution pixel arrays in JSONL is rarely a good idea — a 640×480×3 frame is ~900 KB as base64, and a 10-minute recording at 30 fps is 18 GB. Prefer video for serial frames or an object-store reference pattern for sparse / high-value frames.