Skip to main content
Known Participant
March 23, 2011
Question

InsufficientBandwidth warning behaves differently in 4.0.1

  • March 23, 2011
  • 3 replies
  • 1707 views

Help!

I have an application that connects people face-to-face for a live stream, and then later combines the two recorded streams from their live interaction. I utilize the InsufficentBandwidth warning to help ensure that each end of my recorded stream is the same length.

I've started a test server and installed 4.0.1, but when I simulate low bandwidth conditions in 4.0.1, I do not recieve the same warning with any accuracy, and I usually do not see it at all. Are there new settings that I need to tweak, or is this a bug in the latest release? The issue will prohibit me from upgrading, and apparently there are critical security fixes in 4.0.1

Thanks!

    This topic has been closed for replies.

    3 replies

    Nikhil_Kalyan
    Participating Frequently
    April 19, 2011

    Hi,

    I tried to see the different that you mentioned between the behavior on FMS 4.0 and FMS 4.0.1 builds specifically for the InsufficientBW warning event. I started a simple live stream (800 kbps) with Netlimiter on the client to simulate lower bandwidth conditions (limiting BW to 100 kbps), and within the testing that I did, i had the same frequency in the occurances of the warning for NetStream.Play.InsufficientBW on both the FMS builds, and hence coudn't find what you are observing. I used Flash Player 10.2 for the playback for two minutes and i got the InsufficientBW warning around four times within this playback time within my bandwidth conditions.


    Do you want me to try some specific steps ?

    Thank you !

    Nikhil_Kalyan
    Participating Frequently
    April 19, 2011

    You can directly get in touch with me for quicker turn around for the issue as i am actively working on this one.

    my mail : npkalyan@adobe.com

    Thank you !

    Known Participant
    April 4, 2011

    Any information here? The issue is inhibiting us from updating to 4.0.1, which seems pretty crucial given the security issues listed for 4.0.0.

    Too often on this forum I see responses from people labeled as "employee" asking questions to posts, but not following up with any clear direction or useful information. I'm happy to provide any data points necessary to troubleshoot or diagnose this issue. I'd love to understand if my assumptions about this feature were incorrect, or if something has recently changed in the expected functionality. Thanks.

    Participating Frequently
    April 8, 2011

    First of all sorry for no response. I somehow missed your query in all the threads i have been answering off late - they were many of them and my apologies of missing on it.

    Let me look at changes which went in 4.0.1 and see any of those changes has realy implication on status messages.

    Till i figure out changes between 4.0 and 4.0.1 - is it possible for you to use bandwidth check mechasim and keeping some threshhold value and disconnect client if its bandwidth falls below threshhold value - does it make any sense for you.

    Check this link related to bandwidth checking: http://help.adobe.com/en_US/FlashMediaServer/3.5_Deving/WS5b3ccc516d4fbf351e63e3d11a0773d56e-7ffa.html#WS5b3ccc516d4fbf351e63e3d11a0773d117-7ffb

    Participating Frequently
    April 11, 2011

    Hi,

    I'm replying on behalf of SE_0208. I cross checked the changes that have gone into 4.0.1 from 4.0. And there seems to be no changes that are related to your issue.

    I have mailed the concerned people to get more information. I'll get back to you once I have more information on your issue.

    And also, after upgrading to 4.0.1 have you done any configuration changes apart from whatever you had in 4.0 or have you missed any configuration changes?

    Have you changed your flash player?

    Thnaks,

    Manish.

    Participating Frequently
    March 25, 2011

    I am trying to understand how and why are using the InsufficientBandwidth warning to achieve something which are trying to acheive

    Known Participant
    March 28, 2011

    I connect two people to a live chat, and record the results. Later, I process the results into a single video of one person, and both people

    s audio. If, during the course of the chat, someone is disconnected, I disconnect the other person as well and then reconnect them, appending new video to the existing recorded video of their chat before disconnect.

    When someone has trouble pushing video/audio because of bandwidth issues, often the stream will appear to freeze for the other participant. In this case, sometimes people refresh the browser window in attempts to 'fix' the issue, which causes both streams to disconnect.

    When this happens, because one end has been streaming video/audio to the server at a normal rate, and another has not, the resulting vidoes are out of sync - one side has more data in it than the other. Once they reconnect, more data will be recorded, but the videos are no longer the same length - and the result is out of sync video/audio when I later combine the two into one.

    I use the low bandwidth warning to pre-emptively disconnect people and keep the audio/video in sync.

    I also use it as a test to see if a machine is capable of streaming at the quality our product requires. If we do a test chat and get an insufficient bandwidth warning, we can assume that the person's setup may not be optimal for a longer chat.

    I'm not sure I understand why it matters how I use it? It's a documented feature, there's nothing in the changelog that suggests that the functionality has changed, and it seems to work differently between 4.0 and 4.01 (where it rarely seems to work at all). Has something about it changed?