splitmuxsink: Do not hardcode frames_of_daily_jam
authorVivia Nikolaidou <vivia@ahiru.eu>
Tue, 16 Oct 2018 12:42:12 +0000 (15:42 +0300)
committerVivia Nikolaidou <vivia@ahiru.eu>
Tue, 16 Oct 2018 13:06:47 +0000 (16:06 +0300)
commitaf0e30d5452d87117dd6371fd15e213af5524ac4
tree44240361954963516812abc35be527c4c8d97237
parent09904e59df1223da8e028ea1e5b4a135ddd82a98
splitmuxsink: Do not hardcode frames_of_daily_jam

Apart from the obvious drawbacks of hardcoding, the drawback here was
that, if we subtracted 2 frames (instead of 2.6) from the target running
time, we'd request the next keyframe a bit too far into the future,
which would make our files split at the wrong position.

https://bugzilla.gnome.org/show_bug.cgi?id=797293
gst/multifile/gstsplitmuxsink.c