EricssonResearch / EricssonResearch/openwebrtc
Checking H264 Capability on Firefox
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 531
- PR merge metrics
- No merged PRs in 30d
Description
Hello everyone,
Have you tried the H264 capability of Firefox? I connected the NativeDemo app for iOS with the Firefox browser. I checked the SDP data and it seems that it is still using VP8
a=rtpmap:120 VP8/90000
Based on the NativeDemo code, handleOfferReceived/handleAnswerReceived checks the encoding name and I always get "VP8"
I have tried using two iOS devices, both with A7 processor (since it supports the H264 hardware encoding) and I get H264 in the SDP data and on the code. However I expect that on Firefox the same behavior will happen. Any thoughts on this guys?
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 with the NativeDemo handleOfferReceived/handleAnswerReceived checks and compare their encoding-name result with the Firefox SDP, then trace the negotiation inputs. Done means identifying why Firefox advertises VP8 here and recording the supported behavior or a reproducible correction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ios
- Domain
- audio-video-rtc, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100