Skip to content

Gating needs to do a proper job of handling timestamps associated with each frame #8

@jmtayloruk

Description

@jmtayloruk

The code is not doing a great job of precise timing. It determines a delay time before sending the trigger, but then executes a bunch more code.

Oh and, more importantly, that delay time is then treated relative to “current_time”, which is set after doing the phase-matching. That is going to reduce accuracy and precision, and also makes me even more uncomfortable in terms of future-proofing.

I think it would be much better to pass around absolute times, not deltas.

Chas writes:
There was a reason, three years ago, to use relative times... but it could just have been because that was of interest to me in my offline analyses?

Originally posted by @ChasNelson1990 in https://github.com/_render_node/MDE3OlB1bGxSZXF1ZXN0UmV2aWV3NDY4MjcxOTQw/pull_request_reviews/more_threads

Jonny writes: I suspect any emulation concern you might have will be resolved if we pass around proper timestamp metadata with each frame

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions