RELEASE: GstValidate 1.3.90

[Thibault Saunier]

Hello Thornton,

>    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


That issue probably means that there is a timestamping bug somewhere.

> [snip]
> Repeats for each frame

Really you get that message for each frame? I doubt it, the test is
(at least should be) executed only for the first frame.

> 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.

I do not see QOS underflow message in the logs you sent.

> 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

It is just a GST_FIXME in the code, not  really an issue.

Regards,

Thibault Saunier