[Bug 766010] jifmux fails to find EOI if it's not within the last 5 bytes

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=766010

--- Comment #8 from Thiago Sousa Santos <thiagossantos at gmail.com> ---
(In reply to Mohammed Sameer from comment #7)
> Do we know what kind of data is present if we scan backwards? It is in
> theory more efficient but I have no idea what kind of byte values I should
> be watching for.

What do you mean? jifmux was made to deal with jpeg buffers, one jpeg frame per
buffer. What other type of data could be present?

Let's take a look at this bug from another angle, did you consider using
jpegparse before the jifmux? It should be able to strip that extra padding data
and seems like a more appropriate element to do it instead of having it in
jifmux.

> 
> Another idea would be to scan the last 5 bytes as we currently do but if we
> fail to find EOI then we scan all the encoded image data. What do you think?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.