Delay on EOS for rtspclientsink

[Zemelia]

Hello @repugraf!
Thanks for adding the EOS event to your library — it works great in most cases.
However, when using rtspclientsink, after the second (or subsequent) attempt to restream frames from the original source to another endpoint, I notice a long delay before EOS is triggered. Additionally, the frames themselves are delayed between the two pipelines (the source and the rtspclientsink output).
Code for example - https://jsfiddle.net/210cukp6/

Do you have any ideas what might be causing this?

Thanks!

[repugraf]

@Zemelia in example you've provided there are 2 pipleines:

1. Reads from rtsp
2. Writes to another rtsp

There are bus listeners for the writer pipeline but no bus listener for reader pipeline.

If the goal here to react to changes of reader (rtspsrc) stream you should add listener to reader stream. Something like this (in startPipeline function):

const interval = setInterval(async () => {
  const event = await pipeline.busPop(1000);

  if (event?.type === 'eos') {
    clearInterval(interval);
    process.exit(0);
  }
}, 10);

So if you want to send eos to rtspclientsink as soon es it's detected in rtspsrc pipeline you should add relative listener to rtspsrc and send eos to rtspclientsink. Problem is endOfStream is exposed only in AppSrcElement. So to be able to send eos to rtspclientsink new functionality needs to be added.

Just to confirm - is this the goal here? To re-transmit oes from rtspsrc to rtspclientsink?

[repugraf]

Since there has been no response for 6 months, I’m closing this issue for now.
If this is still relevant, don’t hesitate to comment and we can reopen it.

[repugraf]

EOS feature was added in this PR #21 if there is an interest for it