Changes between Version 22 and Version 23 of StreamingGuide


Ignore:
Timestamp:
Aug 29, 2012, 11:15:09 PM (4 years ago)
Author:
rogerdpack
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • StreamingGuide

    v22 v23  
    4949== Latency == 
    5050 
    51 You can decrease latency by specify that I-frames come "more frequently" (or basically always, in the case of [[x264EncodingGuide|x264]]'s zerolatency setting), though this can increase frame size and decrease quality, see [http://mewiki.project357.com/wiki/X264_Encoding_Suggestions here] for some background. 
     51You may be able to decrease latency by specifing that I-frames come "more frequently" (or basically always, in the case of [[x264EncodingGuide|x264]]'s zerolatency setting), though this can increase frame size and decrease quality, see [http://mewiki.project357.com/wiki/X264_Encoding_Suggestions here] for some more background.  Basically for typical x264 streams, it inserts an I-frame every 250 frames.  This means that new clients that connect to the stream may have to wait up to 250 frames before they can start receiving the stream (or start with old data).  So increasing I-frame frequency (makes the stream larger, but might decrease latency).  For real time captures you can also decrease latency of audio in windows dshow by using the dshow audio_buffer_size [http://ffmpeg.org/ffmpeg.html#Options setting].  You can also decrease latency by tuning any broadcast server you are using to minimize latency, and finally by tuning the client that receives the stream to not "cache" any incoming data, which, if it does, increases latency. 
    5252 
    5353== Cpu usage/File size ==