Specify endianess of pcm samples
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
In the wild, PCM can be in little endian or big endian. Because most of the time they come from RIFF files and RIFF files are little endian, implementations (certainly Firefox, probably Chrome?) have assumed little endian. RIFX files exist but are somewhat rare, that would be big endian RIFF files.
I propose that we standardize Web Codecs facilities to be little endian. We can always register new pcm types if a big endian ends up being needed.
Contributor guide
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.
Research direction
Start by reviewing the Web Codecs PCM facilities and the RIFF/RIFX endian distinction described in the issue. Determine whether the specification should define little-endian samples and how that affects existing PCM types; done means the endian behavior is standardized or a new PCM type is clearly required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100