hdrprobe v0.7.0

[matthane]

New

• Stdin input. hdrprobe - probes a stream piped to stdin: the container is sniffed from the first bytes, a bounded format-aware head is read (currently 24 MiB for MPEG-TS/M2TS, whose metadata rides about one GOP in, and 16 MiB for everything else), and the ordinary probe pipeline runs over that buffer. This is built for callers whose media has no filesystem path an external process could open, such as Kodi addons, media-server plugins, and ranged HTTP fetches. A stream that ends within the budget reports identically to probing the same bytes as a file; a longer stream is flagged input_truncated in JSON, and the facts a prefix cannot support (a transport stream's duration, most bitrate figures) are withheld rather than reported wrong. hdrprobe stops consuming stdin once it has its budget, so the upstream writer seeing a broken pipe is the success signal and piping an entire remux costs only the head. - may appear at most once per invocation, --full is rejected on stdin (a pipe cannot be seeked or fully scanned), and metadata sidecars (raw RPU .bin, DV CM XML, HDR10+ JSON) are recognized by file extension so they still need paths. A consumer integration guide ships as docs/INTEGRATION-STDIN.md and is included in every release archive.

Schema

• 2.2 to 2.3 (additive). New top-level input_truncated boolean, serialized only when true; a complete stdin read and every file probe stay unflagged. "-" joins the file value space for stdin probes, and on a truncated probe size_bytes counts the bytes probed while the prefix-derived facts above are withheld. No existing field changed shape, type, unit, or presence, so consumers following the docs/SCHEMA.md conventions are unaffected.

---

This discussion was created from the release hdrprobe v0.7.0.