Vivia Nikolaidou f3b539e0ff 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. https://bugzilla.gnome.org/show_bug.cgi?id=790334		2017-11-14 18:29:49 +02:00
..
gstavwait.c	avwait: Deserialised timecodes set after caps event now get correct framerate	2017-11-14 18:29:49 +02:00
gstavwait.h	avwait: Better handling of deserialised timecode framerates	2017-11-10 17:28:05 +02:00
gsttimecodestamper.c	Revert "timecodestamper: LTC from audio"	2017-11-07 21:12:32 +02:00
gsttimecodestamper.h	Revert "timecodestamper: LTC from audio"	2017-11-07 21:12:32 +02:00
Makefile.am	Remove plugin specific static build option	2017-05-16 14:05:52 -04:00
meson.build	meson: Added meson.build for audiomixmatrix and timecode	2017-02-24 10:10:07 +02:00
plugin.c	avwait: Rename timecodewait to avwait, add modes	2017-01-26 16:21:55 +02:00