EricssonResearch / EricssonResearch/openwebrtc
Best settings for stable, lagfree video?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 531
- PR merge metrics
- No merged PRs in 30d
Description
Hi guys,
working with OWR for a while now (part of my bachelor thesis so expect more questions 😄) and build somethings similar to NativeDemo (one-way video from iOS to chrome using the back-camera, two-way audio). I have it at a pretty stable point now, audio works good and just the video sometimes has freezes for around 3 seconds, which is a bit annoying...
Seems to be independent of the resolution and bitrate (using VGA or CIF with 768 and 512 kbit/s mainly) and occurs every now and then. Did you experience this behavior already, looks like a full buffer or sth?! There is definitely enough bandwidth in my network, testing inside my local WiFi for now, demo.openwebrtc.io has the same behavior with NativeDemo btw.
Any advice how to make the video more stable and get rid of these freezes would be appreciated, planning to use it in a mobile network some day!
PS. How can I tell if my iOS-device uses hardware-accelerated H.264, tests on iPad 3 and iPad Air (A7) didn't show a clear difference for me, does it only profit when decoding video?
Cheers,
Tobias
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
Reproduce the intermittent freezes with NativeDemo or the described iOS-to-Chrome setup, including the listed VGA/CIF resolutions and bitrates. Compare behavior on the mentioned iPad 3 and iPad Air, then document whether the cause and relevant hardware-accelerated H.264 behavior can be identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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
- 25/100