jpegparse flush behavior

[Graham Leggett]

On 10 Jan 2017, at 1:46 AM, Matt Staples <staples255 at gmail.com> wrote:

> 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?

Looks like a bug - I have run into something very similar in the OMX drivers, which was subsequently fixed.

Regards,
Graham
—

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3240 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20170110/75b0f706/attachment.bin>