RTSP to WEBRTC without h264 transcoding
marc.leeman at gmail.com
Fri Aug 7 14:26:56 UTC 2020
>From experience, you can create a pipeline that takes in whatever data (be
it RTSP or something else) and send it to a WebRTC element. You don't
really need to reply to I-Frame requests and such.
The only trick is that WebRTC has non-standard signalling; so you'll need
to handle that in some way or you'll need to hardcode about everything you
In general, the pipelines I used was something along the lines of
uridecodebin uri=..... caps="video/x-vp9; video/x-vp8; video/x-h264;
video/x-h265" ! parser ! payloader ! webrtcsink uri=....
Of course this was unidirectional.
By doing this, you could easily send feeds from standard cameras over
(IIRC) amazon cloud to some browser on a hand held device.
Unfortunately, management lost interest; and this code is now rotting in
some git repo :-(
On Fri, 7 Aug 2020 at 09:00, evaluat0r <volatileconst at gmail.com> wrote:
> pasifus wrote
> > and what gstreamer pipeline you used?
> > --
> > Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> > _______________________________________________
> > gstreamer-devel mailing list
> > gstreamer-devel at .freedesktop
> > https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
> I don't think you can do this because if a PLI or intra frame request is
> made, then you have to respond to that. But RTSP doesn't understand those
> requests so your webrtc sender would have to decode and encode the h264 or
> vp8 data.
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gstreamer-devel