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 695483 - h264parse does not parse correctly
h264parse does not parse correctly
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal major
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-09 08:14 UTC by Wilhelm Westermark
Modified: 2015-07-29 14:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Debug level 4 of the pipeline (152.57 KB, application/octet-stream)
2013-03-09 08:14 UTC, Wilhelm Westermark 		Details

Description Wilhelm Westermark 2013-03-09 08:14:40 UTC 
Created attachment 238448 [details]
Debug level 4 of the pipeline

I tried using h264parse from bd8963f on my Raspberry Pi and I keep recieving:

0:00:02.736097382 20392   0xfdb030 WARN                 default gstsegment.c:478:gst_segment_to_running_time: invalid position (-1)

My pipeline is:

gst-launch-1.0 filesrc location=/opt/vc/src/hello_pi/hello_video/test.h264 ! h264parse ! fakesink

A change of sink does not change anything.

I also tried building it on my x64 laptop and received the same errors, though not as frequently.

I built the packages on the pi with: 

./autogen.sh --disable-docbook --disable-gtk-doc --enable-introspection=no --disable-nls --disable-examples --with-plugins=videoparsers --with-egl-window-system=rpi --enable-eglgles
Comment 1 Edward Hervey 2013-07-24 08:10:51 UTC 
Wilhelm, Is this still an issue with more recent gst versions ? What versions are you using ?
Comment 2 Alexandre Franke 2015-07-29 14:47:23 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!