Several threads talk of increasing this setting to as high as 20MB per camera. I am unclear to the exact reasoning behind this suggestion, is it simply to avoid dropped packets / frames ?
I have tried several settings & once I increase above the default minimum of 0.5MB I get significant "lag time" between cameras when viewing live. With 4 cameras, 3x D2D with time being streamed from the cameras themselves & one camera just MPG4 encoding (XVID) with BI time overlay enabled, there is 30 second to 1 minute lag between cameras. I can go outside, wave & smile, trigger the camera, walk back in, wait 15 seconds & watch myself. Ideally I want to minimize dropped frames yet I still require accurate live stream. It is unclear if this setting is specific to systems suffering performance or packet loss issues or other tweaks with this setting that can assist in performance, but "not at any cost".
I've set it @ 1MB & that seemed reasonable yet still had 15 second lag at a minimum, so it appears it buffers all the time, not just when stressed, which to me seems counterproductive. I want it to buffer when required (stressed) but only at that time, not all the time. How are others working with this setting & when are they adjusting it, simply for stress & performance?
I regularly run "netstat -s -p tcp" (to detect any packet loss issues) on the PC running BI & am always within that 1-2% range of packet re-transmit values which suggests the network is running as optimally as expected.
I have tried several settings & once I increase above the default minimum of 0.5MB I get significant "lag time" between cameras when viewing live. With 4 cameras, 3x D2D with time being streamed from the cameras themselves & one camera just MPG4 encoding (XVID) with BI time overlay enabled, there is 30 second to 1 minute lag between cameras. I can go outside, wave & smile, trigger the camera, walk back in, wait 15 seconds & watch myself. Ideally I want to minimize dropped frames yet I still require accurate live stream. It is unclear if this setting is specific to systems suffering performance or packet loss issues or other tweaks with this setting that can assist in performance, but "not at any cost".
I've set it @ 1MB & that seemed reasonable yet still had 15 second lag at a minimum, so it appears it buffers all the time, not just when stressed, which to me seems counterproductive. I want it to buffer when required (stressed) but only at that time, not all the time. How are others working with this setting & when are they adjusting it, simply for stress & performance?
I regularly run "netstat -s -p tcp" (to detect any packet loss issues) on the PC running BI & am always within that 1-2% range of packet re-transmit values which suggests the network is running as optimally as expected.
Last edited: