We upgraded from .46 to .48 having seen a reference to long SRT stream framing issues.

Yesterday we had 3 Inbound streams going and 7 outbound.

2 of the Inbound were via SRT - one from an Atomos Connect, and the other was from our Main VMIX OB PC. We've moved to SRT as the commentary for the most part seems to be it is more stable, more resiliant to network drops, Jitter, etc.

The atomos connection dropped right toward the end of the stream - but had been going for around 5.5hrs - so all told not bad.

The VMIX Broadcast, per another question I have asked about having SRT Stream options - is instead just working with the SRT output - using 10Mbps, the usual 2 second keyframes, and pushing to a specific Path on our SRT server. Then that SRT server pushes to the RTMP Server that has the Youtube and Facebook RTMP details.

That stream had been going for around 3.5 hrs at the time, and AI has mostly identified "timing drift / pacing instability"


2026-06-07 09_19_51-vMix Pro - 29.0.0.48 x64 - VLogStreaming.vmix.png (3,092kb) downloaded 5 time(s).

Should we still use this method to push our Streams? or go back to relying on RTMP Custom pushes... Which for the most I even think seem to have better Quality if I'm honest, but seems to be that when they Drop...they drop more savagely and take longer to get back online to the RTMP server, as we need to reset NGINX...

Or even - is there some means to add into a hidden config to be able to make sure the SRT data itself is definitely these settings:

enable strict CFR
fixed GOP
keyframe exactly every 100 frames (50fps = 2s)
no adaptive GOP
no dynamic bitrate.

Cheers in advance