[Bug 655804] Play position advancing but frames not rendered

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=655804
  GStreamer | gstreamer (core) | 0.10.34

--- Comment #17 from Tvrtko Ursulin <tvrtko.ursulin at onelan.co.uk> 2011-09-01 07:55:26 UTC ---
Unfortunately this did not fix the original problem.

I left the test running overnight streaming BBC ONE from DVB-T and saw several
instances of the bug - the one ongoing as we speak is longer than observed
before.

First I had a couple of shorter instances, exactly like in the initial report.

2011-09-01 03:50:21.786 DEBUG QOS[xvimagesink0] @ 27934.877578s
rendered/dropped=1394780/123; jitter=87ms
2011-09-01 03:50:28.874 DEBUG playPosition 27940535676389L
2011-09-01 03:50:38.874 DEBUG playPosition 27948599676389L

This goes on for some time, during which I am pretty sure nothing was rendered
because it ends with:

2011-09-01 03:55:48.875 DEBUG playPosition 28196567676389L
2011-09-01 03:55:58.874 DEBUG playPosition 28204535676389L
2011-09-01 03:56:05.462 DEBUG QOS[xvimagesink0] @ 27936.537578s
rendered/dropped=1394843/124; jitter=342103ms

A QOS message reporting jitter of roughly the period since last QOS message.

Second instance happened early morning, at 5:35 - which is 100% because I have
a clock showing that time on a frozen frame on screen right now. And again
GStreamer is reporting that play position is advancing and there are no QOS
messages.

Log looks like this:

2011-09-01 05:35:01.821 DEBUG QOS[xvimagesink0] @ 5935.305789s
rendered/dropped=295874/44; jitter=84ms
2011-09-01 05:35:08.874 DEBUG playPosition 5942442919718L
2011-09-01 05:35:18.874 DEBUG playPosition 5952443305672L
2011-09-01 05:35:28.874 DEBUG playPosition 5962443057111L
...
2011-09-01 08:53:28.874 DEBUG playPosition 16541955894445L
2011-09-01 08:53:38.874 DEBUG playPosition 16550019894445L
2011-09-01 08:53:48.874 DEBUG playPosition 16557987894445L

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.