BUG with queue element ?

[Stefan Sauer]

On 09/17/2014 04:32 PM, Prabhakar Lad wrote:
> Hi Stefan,
>
> Thanks for the response!
>
> On Wed, Sep 17, 2014 at 12:38 PM, Stefan Sauer <ensonic at hora-obscura.de> wrote:
>> On 09/15/2014 08:56 PM, Prabhakar Lad wrote:
>>
>> Hi Tim,
>>
>> Thanks for your response!
>>
>> On Mon, Sep 15, 2014 at 6:01 PM, Tim Müller <tim at centricular.com> wrote:
>>
>> On Mon, 2014-09-15 at 17:03 +0100, Prabhakar Lad wrote:
>>
>> Hi,
>>
>> What GStreamer version are you using?
>>
>> I am using GStreamer-1.0
>>
>> Perhaps you could distill this into a minimal test case that
>> demonstrates the issue?
>>
>> I attaching the c file test-case and also pasting the code, so
>> that its easier to review.
>>
>>
>> How do you stop the program? With Ctrl-C? You should send an EOS to the
>> pipeline before stopping to ensure the queue is flushed.
>> Stefan
>>
> I am not sure if I have put my words rite,  as per my understanding of the valve
> element, when the drop property is set back 'TRUE' it should resume
> the data flow
> between the elements but there isnt I have tested with adding a probe
> callback at the source
> pad of the valve. the callback never hits. hope that clears!
When you set the valve.drop=FALSE it continues, but everything that it
received while drop was TRUE is gone. Alsi in your example you drop from
the beginning, this way you might miss initial events.

Stefan

> Agreed at the end, The pipeline should be flushed with EOS!
>
> Thanks,
> --Prabhakar