w3c / w3c/webcodecs

Per-plane VideoFrame copyTo()

Open
#431 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

extension
Dominant language
HTML
Stars
1.3k
Forks
194
Avg merge
1d 13h
Merged PRs (30d)
3

Description

(No urgent requests for this feature. Just relocating an idea from Chrome's bug tracker. Yell if you're interested!)

There may be cases where apps would be more efficient if they copied only the Y plane, only the non-alpha planes, or only the alpha plane.

Potential strategies:

  • Add a per-plane discard flag to copyTo().
  • Allow the copyTo() layout to be shorter than the number of planes, implying discard (doesn't solve alpha-only).
  • Provide a plane-subset configuration flag to copyTo() eg. {planes: "Y"} or a more generic conversion API eg.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked Chromium bug and the existing VideoFrame copyTo() API specification. The issue presents several possible designs but names no implementation files or tests. Done would require choosing and specifying a per-plane copying strategy before implementation can be scoped.

Written by the indexing model from the issue text.

Assessment

Domain
api, audio-video-rtc
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.