• v0.7.7 d1a2b7ed10

    v0.7.7 Stable

    builduser released this 2026-09-07 06:22:40 +02:00 | 6 commits to main since this release

    Fixes a source failing to publish with:

    stream map '' matches no streams
    failed to set value '0:v' for option map
    

    What was wrong

    ffmpeg's stream probing was limited to 32 bytes and no analysis time, in the
    belief that it kept latency down. It does not: probing stops as soon as the
    streams are known, so those limits only matter when something goes wrong. What
    they did instead was make ffmpeg give up before it had seen a single video
    tag, leaving no video stream for -map 0:v to match.

    Whether it failed depended on how the stream happened to arrive. Fed a whole
    file at once, 32 bytes can be enough by luck; fed at the rate a live source
    actually arrives, it is not. One source worked and the next did not, which
    made it look like a problem with the second machine rather than with the
    setting.

    The limits are now a megabyte and half a second, still upper bounds rather
    than waits, so there is no cost in the normal case. The decoder behind the
    program view had the same setting.

    The test feeds a stream at roughly live pace rather than all at once, since
    delivering it in one go is exactly the case where too small a probe happens to
    work anyway.

    Downloads

    File For
    streamsink-0.7.7-linux-amd64.tar.gz Linux server, client and agent
    streamsink-0.7.7-windows-agent-amd64.zip Windows agent, headless
    streamsink-0.7.7-windows-server-amd64.zip Windows server and client, with the GTK4 runtime
    streamsink-0.7.7-windows-decoder-amd64.zip Windows decoder, for the program view
    SHA256SUMS checksums, used by the updater
    Downloads