Skip navigation
Currently Being Moderated

how to reduce the Stream.publish latency

Nov 25, 2013 1:51 AM

I 'm now working on a video charting project,  one side is in a BW limited network, the other is in a BW unlimited network, when the limit reduce to 450Kbit/s, the side under limited network result to 2KB/s on publish netstream, but play stream is OK,I calculate the BW for update and download, both 40KB-50KB ,what's wrong with that??

 

 

What can I do to increase the speed of publishing!

 
Replies
  • Currently Being Moderated
    Nov 25, 2013 9:38 AM   in reply to July Chen

    Obviously, the larger your packet frame over RTMP to FMS will take longer to initially package and cache the video, thus when clients play a live stream the delay will be dictated by how quick the FMS server packages the initial 4 second, 8 second, 12 second, 16 second. Usualy by 16 seconds, the live stream is playable.   I have not found a way, such as like with 'ffmpeg -re'  realtime encoding, to enable this feature on FMS, or if it can be manipulated through service side action script main.asc.

     

    Let me know if you do figure a way after packaging, that FMS can close the gap on the cache, to reduce the latency from publish to live client.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 25, 2013 9:40 AM   in reply to ospn2012

    Also keep in mind, if there is any connection downtime or fluctuations in virtualization on the socket that is establishst, that the closer to real time encoding, may create undesirable live playback conditions. Whereas with a larger buffer cache server side, will serve up a smoother live video stream.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points