Skip to main content
Participant
March 27, 2012
Question

Why a 5 second RTMP h264 buffer on my Transformer Prime?

  • March 27, 2012
  • 3 replies
  • 2269 views

I've got a 'live' streaming service that is working very well using Flash or Air on Desktops. I'm able to set netStream.bufferTime to 1.0 seconds and that's what I get in flash player.

When I package the same app for android and deploy it to my Transformer Prime (running Honeycomb since h264 appears to be broken in ICS), I always get a 5 second buffer. This is a show stopper for me since I am receiving commands from the user and updating the video feed. One second latency is ok, 5 is a no go. No matter what I do, I cannot get the Prime even to try and play with a lower buffer setting. I've tried setting netStream.bufferTimeMax = 1.0, but that has no effect. Is there some sort of a hard lower limit on buffer time in Air for Android?

This topic has been closed for replies.

3 replies

flashdictionary
Inspiring
October 1, 2013

No you are not the only developer using netstream.bufferTime on the Android with rtmp. I just wanted to make a note that over a year later this is still a bug on the Android platform with Adobe AIR 3.9.0.960.

We are testing with Galaxy Tab 3, Android version 4.2.2

flashdictionary
Inspiring
October 9, 2013

I have added a bug to the bugbase requesting that Adobe upgrade the Netstream for Androids to support the bufferTime property.

https://bugbase.adobe.com/index.cfm?event=bug&id=3648268

Please add your vote if you are having the same issue.

April 13, 2012

I coming with the same problem in android, when the message "NetStream.Buffer.Empty" come it will change the bufferTime to 5. hope someone can solv it.

Participant
April 2, 2012

Can it be that I am the ONLY developer trying to do live h264 streaming to Android using AIR? Not only is h264 fundamentally broken under ICS, but this 5+ second lag is a show stopper. Can anyone from Adobe comment on this?

April 12, 2012

I am seeing the same problem under Motorola Xoom. Setting bufferTime to 0 causes the video to hang after displaying one frame. Setting bufferTime to a positive value results in a 5 second lag.