[gst-devel] gst_event_new_flush_(start|stop) messing up the pipeline...

[Tim-Philipp Müller]

On Wed, 2010-02-10 at 12:17 -0800, S Boucher wrote:

> Is there some non-official documentation discussing the DOs and DONTs
>   with flush events, and segments?
> 
> From a pad task, I push a flush_start/flush_stop/segment, but any new
>   audio data pushed after that doesn't get played.  The events are
>   successfully pushed, and the timestamps of the new audio buffer are
>   within the range defined by the segment.
> 
> I must be doing something wrong, but nothing that appears to contradict
>  the official documentation.

If audio is not played any longer, then either buffers are dropped
somewhere before the sink, or buffers are modified to silence data, or
the sink drops/clips them.

The GST_DEBUG log should tell you what's happening. Start with
GST_DEBUG=*sink:5 to see if the sink gets buffers and what it does with
them.

It's hard to give general 'DO and DON'T' advice, esp. without even
having seen the code or knowing more about what you are doing.

Do you have the problematic code somewhere for people to look at?

Have you maybe even made a minimal test case that demonstrates the
problem?

Is there a GST_DEBUG log for people to look at somewhere?

Cheers
 -Tim