Skip to content

locate --render reports "matches the file" for internal consistency, which reads as "the span holds what you asked for" and does not #62

Description

@Railly

From the 0.23.0 validation run.

The agent placed a cut whose span did not contain the content it was targeting. locate --render <file> reported that the EDL matches the file, so the agent proceeded. The defect survived into the next round's render and was only caught by re-transcribing that render directly.

locate --render verifies that the EDL's master-time map agrees with the render's measured duration. That is internal consistency. It is not a claim that a given master position holds the content the caller was looking for, and nothing in the output distinguishes the two. "Consistent" and "correct" are different guarantees, and the wording invites reading the weaker one as the stronger.

Cost in that run: one wrong cut, one wasted round, and the defect reached a render that had already passed audit and joins.

Direction: say what was actually checked. Something closer to "the EDL's timing map agrees with this render's duration" rather than "matches the file", and when the caller supplied a position or a phrase, either verify that position holds it or say plainly that this verb does not.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions