Best protocol to send ad playback video to browse and change runtime playback settings

Nirbheek Chauhan nirbheek.chauhan at
Thu Nov 11 05:56:52 UTC 2021

The RTC in WebRTC stands for "real time communication". The protocol and
browser APIs are not designed for VOD playback. You can use it as a
transport protocol, but then you'll need to use custom signalling for
playback controls and do them on the server.

If you want to do what youtube does, you should use the HTML5 APIs:

There's nothing gstreamer-related here except maybe while generating the
media files.


On Thu, 11 Nov, 2021, 11:20 marc lievens, <mark.lievens at> wrote:

> Hi,
> I still have to take a deeper look at webrtc,
> But is this protocol not more  used for live steaming?
> I want user interaction like jumping around and rate changes and stepping
> through and offcouse transcoding on the VOD.
> cheers marc
> Op zo 7 nov. 2021 om 14:49 schreef Nirbheek Chauhan <
> nirbheek.chauhan at>:
>> On Sun, Nov 7, 2021 at 2:15 PM marc lievens via gstreamer-devel
>> <gstreamer-devel at> wrote:
>> > What is the best video and communication protocol that I can use to
>> playback and send video to a  browser
>> >
>> Since this is VOD, i.e., the video is already stored on a server
>> somewhere, the best way is likely to use standard <video> tags. The
>> browser's media controls support playback at varying rates, seeking,
>> pause, play, etc.
>> If the video is not statically available (as a single mp4 or webm
>> file, or split chunks), then you will need to do all media control
>> server-side and send a continuous stream to the browser over webrtc
>> (sounds like you are already doing this for playback). This is a lot
>> more expensive w.r.t. hardware requirements since you need to
>> transcode the stream.
>> Cheers,
>> Nirbheek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gstreamer-devel mailing list