Supports configure lossless encoding
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js, rust
- Domain
- audio-video-rtc
Research direction
Start with the linked W3C WebCodecs issue and the referenced Chrome implementation to understand the proposed lossless-encoding configuration. Then inspect the repository's WebCodecs encoding surface; the work is complete when the Node.js implementation can configure lossless quality for the relevant encoding use cases and its behavior is verified.
Written by the indexing model from the issue text.
Description
Some sampling of use cases:
- Recording local artifacts at the highest quality for subsequent processing by more advanced creation pipelines.
- Working with screen-shares where 4:2:0 sampling causes blurriness. 4:4:4 is required for crisp text at small font sizes.
- Remote processing of audio signals via ML can be affected by audio encoding (hence why WebSpeech encodes to FLAC today).
Spec issue
https://github.com/w3c/webcodecs/issues/258
CQ (Constant Quality) or CRF (Constant Rate Factor in FFmpeg) or QP (Quantization Parameter each codec spec defined) are more fit than target bitrate for some content to keep certain quality includes lossless quality through presentation.
Chrome implementation
A preliminary implementation has been completed in Chrome.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 2
- Avg merge
- 14h 15m
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Brooooooklyn/webcodecs-node
-
Dependency Dashboard Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
All issues in Brooooooklyn/webcodecs-node
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100