Recent changes to video-rtc.js introduced ~1 second delay to MSE stream

[AndrewEyesman]

Hello, I've been integrating the MSE stream example from the go2rtc demo into my project. While the stream loads successfully, I noticed a ~1s delay compared to the demo example.

After some investigation, I traced the issue to the video-rtc.js file, which I borrowed from the demo. Specifically, the delay appears to be introduced by the recent “Improve delay for MSE player” commit.

To confirm this, I tested an older version of video-rtc.js (before this commit), and the delay disappeared.

Unfortunately, I haven't pinpointed the exact cause, but it seems the recent changes introduced unintended latency. Hopefully, someone can reproduce the issue and identify the fix.

Additional context

By “MSE stream example,” I’m specifically referring to this one:

Environment

Go2rtc host: Docker
Browser: [Chrome]
Operating System: [Windows]
Frontend Framework: [React/Vite]

I'm happy to provide any additional information if needed.

[AlexxIT]

I don't know what you mean about demo. Go2rtc doesn't have any demo.

1 sec delay for MSE added for a reason. It could work worse for perfect connection. But it works better for other connections. Because it added controllable buffer before player.

[AndrewEyesman]

When I say demo I'm referring to the web UI. Sorry for not being clear.

Thank you for confirming this is not a bug. However, the 1 sec delay is not ideal for some cases. For example I'm integrating PTZ commands to my application but it feels much worse because of the delay.

[AlexxIT]

You can use old JS version. It's hard to write best logic for all cases.
Old version works fine only in local network. Or on very good channels. And with streams with low quality.

[AndrewEyesman]

Ok thank you. I will consider this moving forward.