jpegparse flush behavior

[Matt Staples]

Hi all,

I have a pipeline that includes an instance of jpegparse.  If I do a
flushing seek on the source, or otherwise send a FLUSH_START event
followed by a FLUSH_STOP event, then jpegparse never parses any more
data.  Looking at the code, I see that gst_jpeg_parse_sink_event has a
handler for FLUSH_STOP, but no handler for FLUSH_START.  And I see
that the base class, gstbaseparse's FLUSH_START handler sets a
variable (priv->flushing) that doesn't get cleared by jpegparse's
overriding FLUSH_STOP handler. So I think that's causing gstbaseparse
to skip all subsequent parsing, which feels like a bug to me, except
I'd be surprised if I was the first one to run into that.  (Unless
maybe using jpegparse with seekable sources is an unusual use case?)

If that's not a bug, any guesses what I might be doing wrong?


Thanks,
-Matt