After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 678469 - jpegdec eats the interlaced flag in the caps
jpegdec eats the interlaced flag in the caps
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.36
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-06-20 11:16 UTC by Xavi Artigas
Modified: 2015-07-27 22:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
playbin2 for a MJPEG file (224.23 KB, image/png)
2012-06-20 11:16 UTC, Xavi Artigas 		Details

Description Xavi Artigas 2012-06-20 11:16:13 UTC 
Created attachment 216818 [details]
playbin2 for a MJPEG file

I have an interlaced MJPEG file which playbin2 cannot deinterlace, because jpegdec is removing the interlaced flag from the caps.
See attached pipeline plot.
Comment 1 Tim-Philipp Müller 2012-06-20 11:21:24 UTC 
Does the file play normally at all, or only at half height?

Could you make the file available?

There is a known issue with interlaced MJPEG - jpegdec will only decode the first field basically.
Comment 2 Xavi Artigas 2012-06-20 11:31:07 UTC 
The file plays correctly, just interlaced.

You can test this pipeline:
gst-launch -v videotestsrc ! interlace ! jpegenc ! "image/jpeg,interlaced=(boolean)true" ! jpegdec ! fakesink silent=1

I had to add the capsfilter because jpegenc ALSO removes the interlaced flag.
Comment 3 Tim-Philipp Müller 2013-01-01 13:55:29 UTC 
Could you please make the file available to me? (how was it created?)

I'm asking because I have never seen interlaced jpeg like that, only with two jpeg images, one for each field.
Comment 4 Alexandre Franke 2015-07-27 22:47:53 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!