The VideoSegmentGenerator appliance was using the old timestamp field
and needed to be updated to use origin. This also helped highlight
some of the difficult-to-parse variable and method names.
Instead of using origin in the segment appliance, it is startingAt
which has more intuitive meaning. Some of the internal methods have
been reworded as well with the goal of legibility.
Issue #103
Description
This PR updates the VideoSegmentGeneratorAppliance to use the new origin Payload.
This also involved renaming some internal variables and methods so the term origin wouldn't be overloaded.
Note that it's hard to name variables that exist to resolve two separate time frames that are moving forward in parallel... but I do think these names are an improvement.
The VideoSegmentGenerator appliance was using the old
timestampfield and needed to be updated to useorigin. This also helped highlight some of the difficult-to-parse variable and method names.Instead of using
originin the segment appliance, it isstartingAtwhich has more intuitive meaning. Some of the internal methods have been reworded as well with the goal of legibility.Issue #103
Description
This PR updates the
VideoSegmentGeneratorApplianceto use the neworiginPayload.This also involved renaming some internal variables and methods so the term
originwouldn't be overloaded.Note that it's hard to name variables that exist to resolve two separate time frames that are moving forward in parallel... but I do think these names are an improvement.
Related Issues
Related to #103