vidoe fps is low
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (wireshark) or Android log (DDMS output)
if you want quick response
What steps will reproduce the problem?
1.I use Doubango and imsdroid on android device.And I found this phenomenon
when an video call between two android devices: no matter what fps i set (by
MediaSessionMgr.defaultsSetVideoFps(fps)),the actual fps was no more than
15,average was about 10 in the send end.That is to say,the fps is less than 15
in the real situation, and can't be biger?
2.For this low fps, the video to the receiver is not very fluent, if 1080p
makes it worse.
3.So in order to get a high fps, how to do?
I have try two solution: one is to use the work thread to deal frame callback
in android level,and it works well for the local video is very fluent.But the
remote video is not such better when 1080p.
Another is can I use multi-thread to encode video frame by ffmpeg in doubango?
and how should I do?
What is the expected output? What do you see instead?
Thanks .
What version of the product are you using? On what operating system?
Please provide any additional information below.
```
Original issue reported on code.google.com by `gle2135...@gmail.com` on 15 Oct 2014 at 3:21
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Android video-call path around MediaSessionMgr.defaultsSetVideoFps(fps), comparing the configured rate with the observed send-end FPS. Review the reported work-thread approach and 1080p behavior, then reproduce with Android logs or a network capture; done requires identifying the FPS limit and documenting or validating a change that improves remote video fluency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- audio-video-rtc, mobile, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100