Skip to content

Potential typo in VideoFrame.copyTo method algorithm #918

Open

Description

@Vanilagy

Step 10.4.7. reads:

Let layout be a new PlaneLayout, with offset set to destinationOffset and stride set to rowBytes.

Logically, this would make more sense if it were:

Let layout be a new PlaneLayout, with offset set to destinationOffset and stride set to computedLayout’s destinationStride.

Because the layout, which will ultimately be returned by the method, refers to the layout of the destination, not the source.

This is further supported by step 10.4.9.3.:

Increment destinationOffset by computedLayout’s destinationStride.

Obviously, we're moving along the destination using the destination's stride, so the returned layout should reflect that.

Activity

  1. changed the title [-]Potential typo in VideoFrame.copyTo algorithm[/-] [+]Potential typo in VideoFrame.copyTo method algorithm[/+] on Dec 3, 2025
  2. added
    CR BlockingNeeds to resolved for Candidate Recommendation
    on Aug 11, 2026
  3. Djuffin commented on Oct 7, 2026

    @Djuffin
    Contributor

    should be addressed by #958

  4. self-assigned this
    on Oct 7, 2026
  5. added
    PR existsA PR has been submitted that addresses this issue
    TPAC2026Agenda topic for TPAC 2026
    on Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

CR BlockingNeeds to resolved for Candidate RecommendationPR existsA PR has been submitted that addresses this issueTPAC2026Agenda topic for TPAC 2026

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions