shady/sketchy incoming media on browser - not on Android

Ask questions about the Android SDK here

shady/sketchy incoming media on browser - not on Android

Postby modim1425 » Thu Feb 21, 2013 7:24 pm

Hello,

I've got my project up and running with 2 way video/audio functioning between Firefox and my Nexus S. I'm having some extreme issues with video quality which I instinctively attributed to Android but after some inspection have realized that the worst part of it is at the incoming end on the browser. Video freezes, unfreezes, glitches and generally acts unruly. It seems (not positive on this but I think...) to get worse over time with the video/audio looking fine at the start (with the exception of some extreme latency) and glitching all the way out to the far reaches of non-usability within a few seconds. I'm getting some interesting logcat stuffs ("FEAR THE COMPACTOR!") coming from the opentok audio video codec parser as well qos reports that I'm assuming are "quality of stream" reports that I'm wondering if you could take a quick look at. Any other advice on how to clean up the video would be really, truly appreciated:

02-21 20:39:28.182: V/opentok-avc-parser(3883): FEAR THE COMPACTOR! readBuffer.remaining=1325
02-21 20:39:28.249: D/dalvikvm(3883): GC_CONCURRENT freed 384K, 6% free 9524K/10119K, paused 12ms+2ms, total 42ms
02-21 20:39:29.799: D/dalvikvm(3883): GC_CONCURRENT freed 419K, 6% free 9523K/10119K, paused 3ms+5ms, total 64ms
02-21 20:39:30.132: V/opentok-subscriber(3883): subscriber qos report: {guid=9082f627-29f0-4b19-a693-f74fcd5e0676, partner_id=22121412, widget_type=Subscriber, duration=120001, media_server_name=fms404-oak.tokbox.com, session_id=1_MX4yMjEyMTQxMn5-V2VkIERlYyAxOSAxNTo1MjozNiBQU1QgMjAxMn4wLjgwMzM1ODE0fg, widget_id=4d61a60d-31ea-48f9-9a67-bc5844a77cea, stream_type=basic, stream_id=1701519971, version=20121019130650-android, connection_id=ed1a05bf-beea-4669-90cb-30e8fb81d8e5}
02-21 20:39:30.428: V/opentok-clientlogging(3883): sent client qos {guid=9082f627-29f0-4b19-a693-f74fcd5e0676, partner_id=22121412, widget_type=Subscriber, duration=120001, media_server_name=fms404-oak.tokbox.com, session_id=1_MX4yMjEyMTQxMn5-V2VkIERlYyAxOSAxNTo1MjozNiBQU1QgMjAxMn4wLjgwMzM1ODE0fg, widget_id=4d61a60d-31ea-48f9-9a67-bc5844a77cea, stream_type=basic, stream_id=1701519971, version=20121019130650-android, connection_id=ed1a05bf-beea-4669-90cb-30e8fb81d8e5}
02-21 20:39:30.885: V/opentok-rtsp(3883): subscriber sent rtcp RR
02-21 20:39:31.190: V/opentok-avc-parser(3883): FEAR THE COMPACTOR! readBuffer.remaining=3819
02-21 20:39:31.424: D/dalvikvm(3883): GC_CONCURRENT freed 419K, 7% free 9507K/10119K, paused 2ms+3ms, total 37ms
Was this post helpful? (0)
modim1425
 
Posts: 19
Joined: Tue Nov 20, 2012 5:18 pm
Thumbs Up: 1

Re: shady/sketchy incoming media on browser - not on Android

Postby charley » Fri Feb 22, 2013 1:06 pm

The compactor notice is mostly harmless, just an internally used garbage collection mechanism.

Do you mind posting a screenshot of the video artifacts that you're seeing? It'll be helpful for me to diagnose. I'm not sure if we have ever certified the Nexus S to be functional with this SDK; we have run into a lot of device-specific encoding issues in the past.
Was this post helpful? (0)
charley
 
Posts: 418
Joined: Fri May 06, 2011 7:41 pm
Thumbs Up: 33


Return to Android (Native)



Who is online

Users browsing this forum: No registered users and 1 guest

cron