Question about correct usage of Livesync

Application Development
1

I have a custom Gstreamer Pipeline thats split into two seperate parts, producer and consumer, linked together via Appsrc/Sink

The consumer eventually outputs its result via RTMP and needs to stay up even if the producer dies, for this reason I’ve put a livesync element in it after the appsrc’s

Now my issue is that the Producer pipeline is replaceable. This will obviously reset the PTS of the data that makes it to the livesync which will then complain about too late buffers. I’ve “hacked” this by manually adjusting the PTS but I hate that solution.

Effectively what I need is a way to “reset” the livesync / tell it that it should work off a new stream without affecting the rest of the pipeline (e.g., keeping its output timestamp). Is that something possible?

Thanks

2

livesync should handle this automatically if you forward the Segment event from the Producer.

You could use the intersink / intersrc elements which will take care of this for you (along with other things such as setting latency on the consumer’s pipeline and so forth).

3

I have some logic in between my pipelines which is why I use AppSrc / AppSink directly. That being said, I was indeed not forwarding events other than setting the Caps on the target.

I have added that now, probing events that reach my appsink and send them to the appsrc in the target pipeline (w/ gst_element_send_event). That did not fix my cause, livesync still expects buffers at the running time from before I had restarted the producer

It does receive the Segment apparently, just doesnt seem to do anything with it:

livesync utils/livesync/src/livesync/imp.rs:1178:gstlivesync::livesync::imp::LiveSync::src_loop_inner:<livesync0> pending Segment { format: Time, start: 0:00:00.000000000, offset: 0:00:00.000000000, stop: --:--:--.---------, rate: 1.0, applied_rate: 1.0, flags: SegmentFlags(0x0), time: 0:00:00.000000000, base: 0:00:00.000000000, position: 0:00:00.000000000, duration: --:--:--.--------- }

livesync utils/livesync/src/livesync/imp.rs:1357:gstlivesync::livesync::imp::LiveSync::buffer_is_backwards:<livesync0> Timestamp regresses: buffer ends at 0:00:00.277841317, expected 0:00:24.331248241

livesync utils/livesync/src/livesync/imp.rs:1016:gstlivesync::livesync::imp::LiveSync::sink_chain:<livesync0> Discarding late Buffer { ptr: 0x7fff9c007fd0, pts: 1000:00:00.254621362, dts: --:--:--.---------, duration: 0:00:00.023219955, size: 4096, offset: 18446744073709551615, offset_end: 18446744073709551615, flags: BufferFlags(0x0), metas: [] }
4

One important thing I probably should re-iterate: The Pipeline containing the Livesync is never EOS, it does / should stay playing the entire time as mentioned before and the producer inputting into it is a live source.

5

the same problem for me

Livesync is buggy