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 673378 - error when parsing output of multipart demux
error when parsing output of multipart demux
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
0.10.19
Other Linux
: Normal minor
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-04-02 17:00 UTC by Jan Spurny
Modified: 2015-11-16 12:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jan Spurny 2012-04-02 17:00:40 UTC
I want to parse mjpeg stream because I want the JPEG images. I tried to use jpegparse and it works, however I'm getting a lot of warnings (I think there's one warning for every frame).

This demonstrates the behaviour (the IP address is public, so it should work everywhere):

--------------------------------
$ gst-launch -e souphttpsrc location='http://c-cam.uchicago.edu/mjpg/video.mjpg' ! multipartdemux  ! jpegparse ! fakesink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...

(gst-launch-0.10:21271): GStreamer-WARNING **: Trying to set string on taglist field 'comment', but string is not valid UTF-8. Please file a bug.
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock

(gst-launch-0.10:21271): GStreamer-WARNING **: Trying to set string on taglist field 'comment', but string is not valid UTF-8. Please file a bug.
...
--------------------------------

When I have used 'jpegparse' in a program and actually read the tags, I got just some binary nonsense.
Comment 1 Tim-Philipp Müller 2013-12-07 12:08:16 UTC
Sorry for not responding to this sooner.

I can't reproduce this any more, not with the latest 0.10 version, nor with current 1.x, so either it's been fixed or the stream contains other metadata now.

Can you still reproduce this with GStreamer 1.x. If yes, could you run it like this and submit a stack trace?

 $ G_DEBUG=fatal_warnings gdb --args gst-launch-0.10 -e ....
 (gdb) run
 ... wait for abort ...
 (gdb) thread apply all bt
 ... paste this ...
 (gdb) kill
  (gdb) quit
Comment 2 Jan Spurny 2015-11-16 12:45:37 UTC
Oh, I'm sorry too, when I didn't receive any comments, I forgot about it.

But as far as I can test, it works without any warnings in 0.10.36 and in 1.4.4.0

So it seems to me it's been fixed, probably a long time ago.