Dynamic pipeline for GstRTSPMediaFactory launch line

[Eslam Ahmed]

Hello,

Just keeping this thread active.
Thanks in advance for any assistance you can provide.

Best Regards,
Eslam Ahmed


On Sun, Jan 15, 2023 at 5:45 PM Eslam Ahmed <eslam.ahmed at avidbeam.com>
wrote:

> Hi Tim,
>
> Thanks for pointing that out. I checked the this
> <https://gitlab.freedesktop.org/gstreamer/gst-rtsp-server/-/blob/discontinued-for-monorepo/examples/test-uri.c>
> example. it does the demuxing and the payloading automatically yet I wanna
> be in a position where I can inject more elements into the pipeline as to
> alter the stream before relaying/payloading it again.
>
> Best Regards,
> Eslam Ahmed
>
>
> On Sun, Jan 15, 2023 at 4:46 PM Tim-Philipp Müller via gstreamer-devel <
> gstreamer-devel at lists.freedesktop.org> wrote:
>
>> Hi Eslam,
>>
>> Is it possible to make use of dynamic pipelines when passing the launch
>> line via gst_rtsp_media_factory_set_launch?
>>
>> For starters, I found out that it must have at least one payloader named
>> pay%d. This is quite problematic if you don't know the codec before
>> spinning the pipeline as you must use the correct payloader. Luckily, I am
>> using rtpgstpay as my payloader so it's fixed.
>>
>> But what about the rest of the pipeline? For example, if the codec is
>> h264 then I need to add an h264parse element in the pipeline same for h265
>> or other codecs. This can be done when using uridecodebin and connect the
>> pad-added callback. Is this the right way to go about this? and if my
>> payloader is not fixed, how would one add it dynamically at runtime?
>>
>>
>> Are you aware of GstRTSPMediaFactoryURI
>> <https://gstreamer.freedesktop.org/documentation/gst-rtsp-server/rtsp-media-factory-uri.html#GstRTSPMediaFactoryURI> in
>> gst-rtsp-server?
>>
>> It does exactly that based on uridecodebin.
>>
>> Cheers
>>  Tim
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20230119/395f5fd9/attachment-0001.htm>