← All news

Robotweax SRT 0.3.3: Hybrid Multicast and Transport Updates

Robotweax SRT 0.3.3, published on 14 November 2026, expands multicast distribution with a fixed source socket, coordinated sending and an experimental hybrid mode that can switch receivers to unicast and back. The release also improves encrypted packet handling, connection shutdown and Windows timing.

Robotweax SRT is an independent, MIT-licensed C++20 implementation of Secure Reliable Transport. Version 0.3.3 retains shared-library ABI 0.3 and the public SRT API target 1.5.7.

More control over multicast distribution

SRT MultiCast sends each original payload once over IPv4 multicast, while individual unicast connections handle receiver-specific control and recovery. Version 0.3.3 adds two optional profiles to this experimental Robotweax-to-Robotweax transport.

Independent-source multicast separates the fixed multicast source socket from the per-receiver unicast control sockets. Both peers explicitly select the profile, keeping multicast source addressing independent of individual control connections.

Coordinated sending gives the group ownership of original transmission, recovery history and a shared wire budget. It requires a positive SRTO_MAXBW and supports up to 64 receivers. Detached receivers are reported through group data so applications can handle membership changes.

Ordinary multicast groups also gain a shared limit for unicast retransmissions when a positive group SRTO_MAXBW is set: all members together are capped at four times that rate. The coordinated profile uses its own budget. Multicast profiles

Hybrid multicast with unicast fallback

The experimental hybrid profile adds authenticated startup with separate receiver credentials, recovery of group membership, unicast fallback and return to multicast. This lets an application evaluate path changes while keeping the media source running.

The robotweax_srt_multicast sample supports --hybrid in a static build with both experimental ACP1 and HYBRID_CONTROL enabled. These features remain off by default and do not add a public C API.

Fallback follows a live catch-up policy: it can discard unread buffered media and reports skipped sequence positions. Applications must account for those discontinuities. The hybrid profile is for Robotweax peers and remains outside the supported security and Haivision interoperability scope. Hybrid media guide

Encryption and runtime improvements

Delayed packets are matched to receive-key generations using accepted sequence positions. Failed authenticated decryptions preserve their encrypted input and do not expose unauthenticated output, including when buffers overlap.

Connection shutdown also receives attention: overdue timers can no longer indefinitely postpone Listener closure. Multicast socket profiles are checked again when listening starts, and Linux epoll handling avoids misaligned field access. Release notes

On Windows, the runtime scheduler now holds a one-millisecond timer period during its lifetime. Applications that manage timer resolution themselves can build with ROBOTWEAX_SRT_WINDOWS_TIMER_PERIOD=OFF. The setting affects pacing and power use; it does not guarantee sub-millisecond scheduling.

Upgrading to 0.3.3

The release preserves all 85 C exports and existing public C layouts from 0.3.2. The three new multicast socket options require matching headers and library. Applications moving from ABI 0.2, and applications using source-tree C++ interfaces, must rebuild.

The release includes signed Windows SDK installers for OpenSSL and the experimental BCrypt backend, checksums and tag provenance. The feature comparison describes the supported profiles and integration differences.

Download Robotweax SRT 0.3.3