Search results

Okay, I've managed to work out what the 'Correct Key' is, it's the 'Verification Code' (Why HikVision make this difficult beyond me)! I've open my saved Mp4 video file and played it in VSPlayer, would someone explain how I remove the cameras line crossing markers from the video footage and also...

Hi Dan Thanks for your reply. I have just installed the VSPlayer but it is asking me for the 'Correct Key' to play the file, what does this mean? I can access previous film footage from my cameras using I.E. and the HikVision software does say that the chosen video clip was saved to the...

Hi, when viewing my cameras on HikVision IP via the laptop I can operate the 'Recording' or 'Capture' feature and in the bottom right corner it tells me that it was successful and also displays where the file was saved to, but I can only view the Jpeg still images, the Mp4 files error when I try...

UPDATE So, anyone following this thread I can update you 2 weeks on. The cameras are using the firmware as stated above, all is running smoothly apart from only one of my DS-2CD2742FWD-I, I have line crossing enabled and when I walk in front of it and activate this function the camera decides...

UPDATE I have changed the firmware as follows: Turrets DS-2CD2342WD-1 are running 5.5.5 Anti-Tamper domes DS-2CD2742FWD-1 are running 5.5.53 This set-up has cured the fault of the turrets from randomly dropping signal (rebooting). Conclusion - Turrets are unstable on...

When updating the firmware to the IP cameras directly through a browser there is a drop down box that gives you the option of 'firmware' or 'firmware directory'. What is the difference? I always use the 'firmware' option.

I can do this, but before I do, is there any on-screen data I should hide for security reasons? Out of the 4 cameras on my system the only ones which are affected are the turret DS-2CD2342WD-1 ones, the anti-vandal dome cameras are unaffected yet are running the same firmware 5.5.53 This...

Hi Phil Me again sorry, being as the 1st camera out of the 4 had received its firmware upgrade to 5.5.53 and was now operating correctly, I decided to upgrade the remaining 3 cameras firmware. As soon as I chose the 2nd camera to upgrade (successfully) my original 1st camera decided to reboot...

It was doing it via the browser and iVMS-4500, I say ‘was’ as it appears to have rectified itself. Very strange. Anyway thank you all for the valuable advice and help, I shall now upgrade all other cameras to 5.5.53.

All from the best UK supplier ‘USE-IP’

Yes, never had a problem with the text overlay whilst on 5.5.0 and the problem is only showing on the one camera that had the firmware upgrade, all other cameras are running on 5.5.0 and are bug free.

Should I keep the ‘primary’ & ‘alternative’ as above (Google’s public dns address), is it safe to leave it with these settings? Just checking

V3.4.98

Well there are no reports of the camera signal dropping which is good, the text overlay bug still exists so should I stick with the latest version 5.5.53 or revert back to the bug free 5.5.0 I wonder what the benifets are of the latest version????

That's fixed it! Thanks for your help Phil. :)

Hi Phil, Yes using I.E. NVR is DS-7608NI-K2 firmware v3.4.98 171121 In configuration, network, basic settings, DNS is ticked, preferred is my router address, alternative is blank.

Eventually opened it, had to browse in Internet Explorer to open, 'Edge' couldn't do it oddly.

Upgraded from 5.5.52 to 5.5.53 and the text overlay bug still exists. I am going to run with this firmware for a few hours to see if the picture drops (camera resets itself) as it did before, if it doesn't then I may leave it as it is and put up with the text overlay bug or revert back to good...

Spoke too soon, the bug is still there. Ive rebooted the NVR but it hasn't cured it. Shall try the upgrade to 5.5.53 to see if this cures it.

Thanks Phil, I've decided to just update the firmware on one camera only and have updated this from 5.5.0 to 5.5.52. I can report that the picture is stable now but the upgrade did alter the text OSD overlay settings. Oddly it created its own unique setting of blinking the text just once or...