Skip to main content
Participant
January 18, 2010
Question

How to configure dual buffering on FMS?

  • January 18, 2010
  • 1 reply
  • 964 views

Hello,

Our customer wants to implement dual buffering with FMS solution, with 3 seconds of initial buffer and 20 seconds of extended buffer.

According to the information we have this implementation is done at the Flash player, but our customer insists that we have to perform some configurations at server side.

We need some help with urgency, do someone know if there is any configurations of dual buffering at server side or if it is all done at player side.

Thanks in advance!!!!!

Regards,

Lewis

    This topic has been closed for replies.

    1 reply

    January 18, 2010

    Client side buffering happens on the client side, the server doesn't care how much data the client buffers (nor should it). The buffer is merely an accumulation of data. All the server should care about is sending that data to the client as fast as it can.

    Perhaps I've missed something, but I know of no server side configs that have anything to do with client side buffer.

    Participant
    January 18, 2010

    But our customer says that with Wowza Media Server it works, and that they have some c

    onfigurations on server side.

    So can somebody confirm if in FMS we also have these configurations at server side?

    Best regards,

    Lewis

    January 18, 2010

    I just went through the config and API docs to make sure I wasn't missing anything, and found nothing about configuration of client side buffer, let alone dynamic buffer. I ran through the Wowza docs as well... didn't find anything there.

    Are you sure your customer isn't confusing dynamic streaming with dynamic buffering? The two are very different. Dynamic buffering has to do with adjusting the buffer, where dynamic streaming has to do with connecting to videos of different bitrates based on QoS variables. In either case, most of the logic resides on the client side (in the case of dynamic streaming, there is some logic on the server side, but the request to change streams needs to be made by the client).

    Did your customer give you any indication of where their info is coming from?