- Mar 9, 2014
- 36,891
- 21,407
- The camera properties Motion/Trigger tab has become the Trigger tab, and motion sensor settings are now available from there in a separate window. This allows more room for additional motion sensor settings, the newest being the algorithm selection of either "simple" or Gaussian. Gaussian was initially used from version 4.2.1 until 4.3.0 when it was replaced with a simpler method. At the time, there were unexplained false positives associated with Gaussian. Although Gaussian uses more CPU time, it should be a superior algorithm now that its initial instability has been ironed out. The "simple" method remains the default for now.
- The Intel hardware decoding produced distorted video with widths not a multiple of 32 (such as 720) this has been repaired.
- Several people have said that the new video components introduced in 4.3.3.1 have caused increased CPU utilization. Although a small number of users, the components have been rolled back to those used in 4.3.3.0 until more can be determined of possible causes.
- Many customers have written in about ReoLink's RTSP issues. While we hope ReoLink will eventually release a repaired firmware for RTSP support, in the meantime, many have reported that setting the H.264 encoding to "baseline" in the camera as well as limiting bitrates have made the stream usable. We now have a ReoLink camera here and are researching support for its native format as used by its web interface.