search

Jhanay / idoubs

Automatically exported from code.google.com/p/idoubs
0 stars 0 forks source link

Slow/sluggish video frame rates #72

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

Please use labels and text to provide additional information.

Original issue reported on code.google.com by boss...@yahoo.fr on 20 Aug 2011 at 11:28

GoogleCodeExporter commented 9 years ago 
Should be fixed by revision 181.
IMPORTANT: Please provide information about your device, iOS version, revision, 
remote party type... in your feedbacks.

Original comment by boss...@yahoo.fr on 8 Sep 2011 at 10:50

GoogleCodeExporter commented 9 years ago 
I've been testing today with the following:

iOS 4.3.5 iPhone
to
iOS 4.3.5 iPod Touch
Doubango r654
iDoubs r181

Codec: H264BL10

I've noticed frame rates are a fair bit slower then previous builds after this 
issue has been fixed.

Original comment by mattvanv...@gmail.com on 10 Sep 2011 at 12:00

GoogleCodeExporter commented 9 years ago 
On my test, endcoding frame rate is around 7 fps on iPhone4 with H.264 baseline 
profile 2.0/3.0 using QVGA resolution while decoding frame rate is around 15 
fps with iPad2, Galaxy S/S2/Tab, Nexus S.  

device : iPhone4
iOS version : 4.2.1
revision : doubango r654, idoubs r181
remote party : iPad2

NEON build option for x264 does not seems to work well on iOS but on Android.

Original comment by bj.park...@gmail.com on 10 Sep 2011 at 1:58

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 10 Sep 2011 at 11:23

GoogleCodeExporter commented 9 years ago 
We pushed new code for tests.
Please update both Doubango and iDoubs

Original comment by boss...@yahoo.fr on 20 Sep 2011 at 8:01

GoogleCodeExporter commented 9 years ago 
Since this issue, I've been hacking significant problems with crashing ant 
t_mutex. I'm reverting my codebase to 1 before this commit today, you can see 
my findings in issue #84

Original comment by m...@curiousminds.com on 28 Sep 2011 at 5:34

GoogleCodeExporter commented 9 years ago 
After reverting to the earlier version, I definitely notice the huge difference 
in framerates between r180 and the current release. However the current release 
is forcing mutex lock issues 1/2 calls, rendering a call useless as the app 
crashes when a mutex issue is confronted.

Is there any way we can fix this?

Original comment by m...@curiousminds.com on 29 Sep 2011 at 11:34

GoogleCodeExporter commented 9 years ago 
Mutex issue resolved as in other ticket.

Latency Issues:

VP8 is unusable, we get a very long delay at the start of the call with one 
side on a gray screen.

H.264BL1.0 seems to be the most reliable codec and bang for buck, we get great 
frame rates on this and will be what we use for the application.

Original comment by mattvanv...@gmail.com on 21 Oct 2011 at 12:06

GoogleCodeExporter commented 9 years ago 
All of my issues regarding to latency have been resolved. In my case I check 
for core count and use codec based on this. For example if cores are 2 i use 
h264base 3.0 and if 1 i use h264 base 1.0.

Original comment by mattvanv...@gmail.com on 13 Feb 2012 at 10:16

GoogleCodeExporter commented 9 years ago 
Fixed in (Doubango_r723 + iDoubs_r210)
For more information: 
http://groups.google.com/group/doubango/browse_frm/thread/cb6da3794242acc6

Original comment by boss...@yahoo.fr on 28 Jun 2012 at 3:54