gstreamer-devel Digest, Vol 130, Issue 19

keith Thornton keith.thornton at
Mon Nov 15 07:08:52 UTC 2021


I have used min-threshold (buffers, time, bytes) together with the
max-size parameters, for the purpose of keeping the last 5 minutes of
video. I used them together with the  leaky parameter. This maintained
the last five minutes in the buffer. If I wanted to save them to disk I
then set the threshold parameters down to a minimum.


Am 15.11.2021 um 08:01 schrieb Marianna Smidth Buschle via gstreamer-devel:
> This isn't something I have ever tried.
> But what about the min-threshold-buffers and similar properties of the
> queue?
> Can't they be used to require that this amount of data is inside the
> queue?
> On 14.11.2021 13.00, gstreamer-devel-request at wrote:
>> Hi,
>> In the spirit of joining your discussion,
>>     - What makes you think that these queues will always have the
>> amount of
>>     buffers that you require at some point? Aren't you just setting
>> their
>>     maximum limit?
>> On the other hand, I would like to know if your method would work
>> because I
>> have tackled this problem via a totally different approach.
>> The idea is to have 2 pipelines. One acting as the trigger, with just
>> the
>> inference plugin, and whenever it finds something interesting it signals
>> the other application, via a method of your choice, controlling the
>> second
>> pipeline. This second pipeline is running concurrently with the first
>> and
>> using an appsink as its sink, you will be able to retain some of the
>> frames
>> in a data structure queue of a size of your choice. Once signalled, the
>> second pipeline would trigger a new on-demand pipeline with an appsrc
>> just
>> to write/record the event.
>> Here's my post on stackoverflow to get the full idea:
>> Hope that helps!
>> Best Regards,
>> Eslam Ahmed

More information about the gstreamer-devel mailing list