[Bug 692875] Different timebases in GStreamer debug output

[GStreamer (bugzilla.gnome.org)]

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

--- Comment #3 from Alexey Chernov <4ernov at gmail.com> 2013-01-30 13:03:57 UTC ---
Wim, Tim-Philipp, thank you for clarification.

It's very often use case for me to compare several events using some time
values in debug messages.

Example 1: I've got a pipeline stalled after flush event now and I want to
detect the exact moment and reason it got stucked. It could be useful to be
able to compare time values from such debug messages with the pipeline time.
But now they're not going to be compared as pipeline time of the messages is
unknown.

Example 2: I found a slight playback problems in xvimagesink and would like to
detect whether basesink schedules everything correctly and it's videodriver
problem or there're some other problems. Again, I need to know, when "possibly
waiting for clock to reach 0:00:06.360000000", is it right, is it late and what
happened to the pipeline on 0:00:06.360000000. And again, now I can't.

Perhaps, system time is also important to count, but I think pipeline time
should definitely be printed somehow as it's sometimes extremely valuable for
debugging.

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