hikvision have stopped responding to me on Skype for over a month, not sure what state of 5.4.4 is sort could not help, I'm waiting for it too.
New Hik firmware 5.4.3
- Thread starter redfive
- Start date
alastairstevenson
Staff member
Maybe they are in a group huddle about their response to the new bugged 'Eagle Eye mode' in the NVR firmware.
Spinning round fast and complaining like it does probably doesn't help device stability.
glfp, Image size (resolution), Image quality/properties and frame rate are what determines the bit rate. Adjusting the bit rate is not a quality setting in its own right, more a means of control over network throughput. So looking at the HikVision table, with a 2MP camera at a resolution of 1080P running at the highest quality setting at 15 fps then if you allow for more than 5120 (for example 8192) then you will achieve the optimum recorded image. However, if you set it to limit at 4096 then the camera will adjust resolution and quality in order to meet this limit. So the bit rate adjustment is more like a throttle, you can leave it wide open for best performance or close it off for best economy. If you are worried about recorded file size then FPS probably has the biggest impact. H264+ compression can have an advantage as it is a smart codec that applies different levels of compression to the image. As I understand it static areas of the image are compressed more than dynamic areas, so the walls of a corridor might be highly compressed whilst people moving down the centre of the corridor are less so (I am not big on algorithms so there is probably a better way to explain this).
As an experiment, maybe you could run the camera in VBR mode and try different image quality and FPS settings and see what that affect that has on your camera output. Based on that, set a Maximum bit rate value that you are happy with and that meets your storage requirements. I am still learning myself (and enjoying it) but I hope that I have helped you in some way. There is also plenty of good help on the web if you dig around.
As an experiment, maybe you could run the camera in VBR mode and try different image quality and FPS settings and see what that affect that has on your camera output. Based on that, set a Maximum bit rate value that you are happy with and that meets your storage requirements. I am still learning myself (and enjoying it) but I hope that I have helped you in some way. There is also plenty of good help on the web if you dig around.
Happy New Year to all.
I just posted this in the thread started by andyblac on 'Firmware 5.4.x working with HikVision on bugs'. It seems that v5.4.4 was set to live on December 26th. The link is here: HIKVISION EUROPE.
I haven't tried it yet but will post any feedback I have when I get the chance.
I just posted this in the thread started by andyblac on 'Firmware 5.4.x working with HikVision on bugs'. It seems that v5.4.4 was set to live on December 26th. The link is here: HIKVISION EUROPE.
I haven't tried it yet but will post any feedback I have when I get the chance.
I purchased a DS-2DE4220IW-D from an official UK distributor and it came pre-installed with V5.4.3 build 160810.
Unfortunately it shuts down all services every couple of days and the only open port on it is ssh.
Ssh'ing in and running dmesg reveals:
Code:
[237806.067154] [ pid ] uid tgid total_vm rss cpu oom_adj oom_score_adj name
[237806.067206] [ 730] 0 730 240 82 0 0 -17 udevd
[237806.067227] [ 1051] 0 1051 351 80 0 0 0 dropbear
[237806.067249] [ 1059] 0 1059 216 77 0 0 0 network_deamon
[237806.067272] [ 1261] 0 1261 958 103 0 0 0 execSystemCmd
[237806.067294] [ 1266] 0 1266 1777 208 0 0 0 daemon_fsp_app
[237806.067318] [ 1272] 0 1272 3590 1045 0 0 0 database_proces
[237806.067341] [ 1273] 0 1273 4814 762 0 0 0 net_process
[237806.067363] [ 1289] 0 1289 373 79 0 0 0 psh
[237806.067383] [ 1291] 0 1291 209446 7777 0 0 0 davinci
[237806.067405] [ 1495] 0 1495 29390 4556 0 0 0 hikdsp
[237806.067422] Out of memory: Kill process 1291 (davinci) score 293 or sacrifice child
[237806.067501] Killed process 1291 (davinci) total-vm:837784kB, anon-rss:5948kB, file-rss:25160kBI have no idea what series (Rn) the DS-2DE4220IW-D is.
Hey SynAckFin,
Have you had any further feedback on this matter ? I noticed you also posted in 'cctvforum.com' too. I am not big on code but looking at your screen dump it seems that DaVinci was the process causing the problem. I think that is the main video processing/rendering application. I have not been able to replicate this symptom as you described, what settings are you using that might be forcing this result ? Also, if you can offer some instructions on how to "ssh" into these newer firmware cameras I would be happy to check what is happening on mine as a comparison. I have installed PuTTY but haven't been able to communicate with the camera so far.
Have you had any further feedback on this matter ? I noticed you also posted in 'cctvforum.com' too. I am not big on code but looking at your screen dump it seems that DaVinci was the process causing the problem. I think that is the main video processing/rendering application. I have not been able to replicate this symptom as you described, what settings are you using that might be forcing this result ? Also, if you can offer some instructions on how to "ssh" into these newer firmware cameras I would be happy to check what is happening on mine as a comparison. I have installed PuTTY but haven't been able to communicate with the camera so far.