Re: [FFmpeg-devel] [PATCH v2 0/6] WebRTC sub-second live streaming support

["Tomas Härdin" <git@haerdin.se>]

tis 2023-11-14 klockan 13:59 +0100 skrev Michael Riedl:
> Another option is an external project for WebRTC testing, but the
> challenge is
> keeping it maintained and compatible with changes in implementations.

Perhaps there are funds to raise for such an effort? I can imagine
Google et al have an interest in this.

> External services might update their software, causing issues with
> tests. We
> would need a plan for dealing with that.

Just making sure various free software implementations interoperate
would be more than enough work, and provides some confidence. Surveying
what features are supported by each implementation would also be of
interest I imagine. For example a client of mine uses aiortc which is
lacking FEC and rate control.

A local company that sometimes contributes to FFmpeg is also involved
in various streaming stuff (though not WebRTC so far, I think).

> For paid services like Millicast, we need to figure out who pays for
> the tests.
> Understanding the costs is essential if we want to use paid services
> for
> testing.
> 
> I'd like to hear your thoughts on these points and how you would
> propose to
> proceed with adding tests for protocols like WebRTC.

The way I've been testing this stuff so far is by hand via Firefox and
Chromium. Both can be automated, though frontend isn't really my area.

As it stands at the moment, we let users be guinea pigs for our
protocols. While not great, this at least means we get bug reports. But
there's no way to ensure old bugs don't resurface.

/Tomas
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".