[Bug 790334] avwait: Deserialised timecodes set after caps event now get correct framerate

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=790334

Vivia Nikolaidou <vivia at ahiru.eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #363614|0                           |1
        is obsolete|                            |

--- Comment #6 from Vivia Nikolaidou <vivia at ahiru.eu> ---
Created attachment 363615
  --> https://bugzilla.gnome.org/attachment.cgi?id=363615&action=edit
avwait: Deserialised timecodes set after caps event now get correct framerate

A deserialised timecode has a framerate of 0/1 by default. That breaks
it when comparing the frames field with another timecode (incoming from
the frame). We were setting the framerate when receiving the caps event,
but not when setting the timecode in set_property, so it was broken for
timecodes set after the caps event.

Also checking if the fps_n we got from the caps event is != 0 before
setting it - also at the caps event.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.