Marianna Smidth Buschle

From what I can see the problem is that in the pipeline without the `interpipe` the `mpegtsmux` only receives 1 segment event, which comes from the encoder: ``` Inspect Event:...

I don't know if the problem is in the interpipesrc or the mpegtsmux, so I have also created this: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1637

Reply from gstreamer community: > Pretty clearly that's a bug in the interpipe source element, if it outputs data with a different segment than when it arrived at the interpipe...

> PR #97 is a potential fix for this report. I have found out late Friday that event though PR #97 improves this problem it is unfortunately not a completely...

From what I could find it seems like the segment gets created by the `basesrc` because there seems to be a default seek in the initialization? https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/master/libs/gst/base/gstbasesrc.c#L1823 ``` 0:00:00.146469458 29690...

My best guess at the moment is that you are missing calling the `appsrc->create()` function (are only calling `basesrc->create()`), which seems to handle the segment: https://github.com/RidgeRun/gst-interpipe/blob/master/gst/interpipe/gstinterpipesrc.c#L463 https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/-/blob/master/gst-libs/gst/app/gstappsrc.c#L1676 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/master/libs/gst/base/gstbasesrc.c#L1570 So I...

So https://github.com/RidgeRun/gst-interpipe/pull/98 makes this work: ``` pipelines.append("v4l2src ! videoconvert ! " "x264enc key-int-max=30 speed-preset=1 tune=zerolatency name=enc_out ! video/x-h264,profile=high ! h264parse ! " "interpipesink name=video_out sync=false async=false " "interpipesrc name=mux_V listen-to=video_out...