From 617264432e19f5530d5856a7919033164fe45ac0 Mon Sep 17 00:00:00 2001 From: Isaac Connor Date: Fri, 26 Mar 2021 17:02:03 -0400 Subject: [PATCH] Add help for ImageBUfferCount and MaxImageBUfferCount --- web/lang/en_gb.php | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/web/lang/en_gb.php b/web/lang/en_gb.php index a2a004199..dcc41c249 100644 --- a/web/lang/en_gb.php +++ b/web/lang/en_gb.php @@ -441,6 +441,7 @@ $SLANG = array( 'Idle' => 'Idle', 'Ignore' => 'Ignore', 'ImageBufferSize' => 'Image Buffer Size (frames)', + 'MaxImageBufferCount' => 'Maximum Image Buffer Size (frames)', 'Image' => 'Image', 'Images' => 'Images', 'Include' => 'Include', @@ -1137,6 +1138,19 @@ $OLANG = array( optionally choose to not decode the H264/H265 packets. This will drastically reduce cpu use but will make live view unavailable for this monitor.' ), + 'ImageBufferCount' => array( + 'Help' => ' + Number of raw images available in /dev/shm. Currently should be set in the 3-5 range. Used for live viewing.' + ), + 'MaxImageBufferCount' => array( + 'Help' => ' + Maximum number of video packets that will be held in the packet queue. + The packetqueue will normally manage itself, keeping Pre Event Count frames or all since last keyframe if using + passthrough mode. You can set a maximum to prevent the monitor from consuming too much ram, but your events might + not have all the frames they should if your keyframe interval is larger than this value. + You will get errors in your logs about this. So make sure your keyframe interval is low or you have enough ram. + ' + ), // 'LANG_DEFAULT' => array( // 'Prompt' => "This is a new prompt for this option",