Fix: flt.utils.muxer: make sure message's default clock class exists
authorPhilippe Proulx <eeppeliteloop@gmail.com>
Tue, 19 Feb 2019 19:51:02 +0000 (14:51 -0500)
committerFrancis Deslauriers <francis.deslauriers@efficios.com>
Thu, 2 May 2019 20:50:15 +0000 (20:50 +0000)
Without the checks added by this patch, the iterator can borrow the
default clock snapshot of a message related to a stream class without
any default clock class. This is a precondition break.

If there's no default clock class, then we fall back to assuming this
message has the same time as the latest returned message's time.

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>

No differences found
This page took 0.024319 seconds and 4 git commands to generate.