<div dir="ltr"><div dir="ltr">
<br></div><div dir="ltr">On Fri, Aug 2, 2019 at 10:38 AM pisymbol . <<a href="mailto:pisymbol@gmail.com">pisymbol@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 2, 2019 at 9:00 AM pisymbol . <<a href="mailto:pisymbol@gmail.com" target="_blank">pisymbol@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
No, I'd say use appsink and implement your own, it's really trivial<br>
thing to do, and then you can fully customized for your needs without<br>
any race.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Via new-sample?</div><br></div></blockquote><div><br></div><div>Sorry, to be more specific. Are you saying do something like this:</div><div><br></div><div>... ! h264parse ! tee name=t0 ! queue ! muxer.video_0 t0. ! queue ! appsink name=appsink0</div><div><br></div><div>And then when I receive a max-file-duration roll over event, flush the appsink queue out via pull_samples? That won't work since I need to timestamp packets as they come in.<br></div><div><br></div><div>Or do you mean do something synchronous using appsrc and appsink? But I don't understand how that would work. Unless I need separate plugins, one to write a timestamp and attach it to a buffer as meta data and then one to drain the appsink later down in the pipeline to write out my side capture file.</div><div><br></div><div>Can you show me a quick pipeline example (just pipeline syntax) of where I could catch the roll-over event from the demuxer which would in turn cause my application to write out all the packets that were written out to a location?<br></div></div></div></blockquote><div><br></div><div>Or do you mean re-work my own multifilesink plugin using appsink and it's callbacks?<br></div><div><br></div><div>-aps<br></div></div></div>