AW: RELEASE: GstValidate 1.3.90

[Thornton, Keith]

Hi,
I tried out gst-validate from the current git master. I used the following pipeline 
gst-validate-1.0.exe filesrc location="f:/data/blah.mp4" ! qtdemux name=demux ! h264parse ! avdec_h264 ! video/x-raw,width=1920,height=1080,format=I420 ! queue ! d3dvideosink sync=true
and got the following results

0:00:00.098269350  5608 0000000002C08600 WARN                validate gst-validate-reporter.c:143:gst_validate_report_valist: <demux:video_0> 131076 (warning) : buffer(2): first buffer's runn
er running time is not 0, it is: 0:00:00.016683333
0:00:00.099157592  5608 0000000002C08600 WARN                validate gst-validate-reporter.c:143:gst_validate_report_valist: <h264parse0:sink> 131076 (warning) : buffer(2): first buffer's ru
ffer running time is not 0, it is: 0:00:00.016683333
0:00:00.100001847  5608 0000000002C08600 WARN                validate gst-validate-reporter.c:143:gst_validate_report_valist: <h264parse0:src> 131076 (warning) : buffer(2): first buffer's run
fer running time is not 0, it is: 0:00:00.016683333
0:00:00.100805341  5608 0000000002C08600 WARN                validate gst-validate-reporter.c:143:gst_validate_report_valist: <avdec_h264-0:sink> 131076 (warning) : buffer(2): first buffer's
buffer running time is not 0, it is: 0:00:00.016683333
0:00:00.149313790  5608 0000000002C08600 WARN                validate gst-validate-reporter.c:143:gst_validate_report_valist: <avdec_h264-0:src> 131076 (warning) : buffer(2): first buffer's r
uffer running time is not 0, it is: 0:00:00.016683333
0:00:00.154283428  5608 0000000002C08600 WARN                validate gst-validate-reporter.c:143:gst_validate_report_valist: <capsfilter0:sink> 131076 (warning) : buffer(2): first buffer's r
uffer running time is not 0, it is: 0:00:00.016683333
0:00:00.156926454  5608 0000000002C08600 WARN                validate gst-validate-reporter.c:143:gst_validate_report_valist: <capsfilter0:src> 131076 (warning) : buffer(2): first buffer's ru
ffer running time is not 0, it is: 0:00:00.016683333
0:00:00.158494733  5608 0000000002C08600 WARN                validate gst-validate-reporter.c:143:gst_validate_report_valist: <queue0:sink> 131076 (warning) : buffer(2): first buffer's runnin
 running time is not 0, it is: 0:00:00.016683333
0:00:00.159762435  5608 0000000002C08680 WARN                validate gst-validate-reporter.c:143:gst_validate_report_valist: <queue0:src> 131076 (warning) : buffer(2): first buffer's running
running time is not 0, it is: 0:00:00.016683333
0:00:00.161259163  5608 0000000002C08680 WARN                validate gst-validate-reporter.c:143:gst_validate_report_valist: <d3dvideosink0:sink> 131076 (warning) : buffer(2): first buffer's
 buffer running time is not 0, it is: 0:00:00.016683333
0:00:00.300667398  5608 00000000034A5450 FIXME                    bin gstbin.c:4023:gst_bin_query: implement duration caching in GstBin again


[snip]
Repeats for each frame



...
0:00:29.685554734  5608 00000000034A5450 FIXME                    bin gstbin.c:4023:gst_bin_query: implement duration caching in GstBin again
   warning : first buffer's running time isn't 062866666 speed: 1.000000 />
             Detected on <d3dvideosink0:sink> at 0:00:00.118093949
             Details : First buffer running time is not 0, it is: 0:00:00.016683333
             Description : the first buffer's received running time is expected to be 0

   warning : first buffer's running time isn't 0
             Detected on <queue0:src> at 0:00:00.116596342
             Details : First buffer running time is not 0, it is: 0:00:00.016683333
             Description : the first buffer's received running time is expected to be 0

   warning : first buffer's running time isn't 0
             Detected on <queue0:sink> at 0:00:00.115327467
             Details : First buffer running time is not 0, it is: 0:00:00.016683333
             Description : the first buffer's received running time is expected to be 0

   warning : first buffer's running time isn't 0
             Detected on <capsfilter0:src> at 0:00:00.113759774
             Details : First buffer running time is not 0, it is: 0:00:00.016683333
             Description : the first buffer's received running time is expected to be 0

   warning : first buffer's running time isn't 0
             Detected on <capsfilter0:sink> at 0:00:00.111110590
             Details : First buffer running time is not 0, it is: 0:00:00.016683333
             Description : the first buffer's received running time is expected to be 0

   warning : first buffer's running time isn't 0
             Detected on <avdec_h264-0:src> at 0:00:00.106146230
             Details : First buffer running time is not 0, it is: 0:00:00.016683333
             Description : the first buffer's received running time is expected to be 0

   warning : first buffer's running time isn't 0
             Detected on <avdec_h264-0:sink> at 0:00:00.057641300
             Details : First buffer running time is not 0, it is: 0:00:00.016683333
             Description : the first buffer's received running time is expected to be 0

   warning : first buffer's running time isn't 0
             Detected on <h264parse0:src> at 0:00:00.056838100
             Details : First buffer running time is not 0, it is: 0:00:00.016683333
             Description : the first buffer's received running time is expected to be 0

   warning : first buffer's running time isn't 0
             Detected on <h264parse0:sink> at 0:00:00.055993845
             Details : First buffer running time is not 0, it is: 0:00:00.016683333
             Description : the first buffer's received running time is expected to be 0

   warning : first buffer's running time isn't 0
             Detected on <demux:video_0> at 0:00:00.055104430
             Details : First buffer running time is not 0, it is: 0:00:00.016683333
             Description : the first buffer's received running time is expected to be 0

Pipeline finished, issues found: 10

=======> Test PASSED (Return value: 0)


The question is, how are these results to be interpreted? Is it a bad mp4 file, could it be the reason why I get a QOS Underflow message for every frame? (although all frames are output to the display.
What does the line in the middle mean
0:00:00.300667398  5608 00000000034A5450 FIXME                    bin gstbin.c:4023:gst_bin_query: implement duration caching in GstBin again



-----Ursprüngliche Nachricht-----
Von: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] Im Auftrag von Thibault Saunier
Gesendet: Montag, 29. September 2014 17:51
An: gstreamer-devel at lists.freedesktop.org
Cc: gstreamer-announce at lists.freedesktop.org
Betreff: RELEASE: GstValidate 1.3.90

The GStreamer team is pleased to announce the first release candidate of the stable 1.4 release series of GstValidate. This is the first release ever of our new testing infrastructure for the GStreamer Framework!

This release candidate will hopefully shortly be followed by the stable 1.4.0 release if no bigger issues are detected, and enough testing of the release candidate happened.

The only part of GstValidate concidered as stable 'API' are the CLI interfaces, and the APIs present in the documentation.

The documentation for GstValidate can be found at:
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-validate/html/index.html

Release tarballs can be downloaded directly from:

http://gstreamer.freedesktop.org/src/gst-validate/gst-validate-1.3.90.tar.xz
be8245ccfb0907205568a923ac3aa0b2d548dd5ada7707b42398712a9a06243c
gst-validate-1.3.90.tar.xz

As always, please let us know of any issues you run into by filing a bug in Bugzilla: https://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer

Best Regards,

Thibault Saunier

_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel