I have camera freeze-ups within D-ViewCam if I use H.264 (instead of MJPEG). Anyone else see this too?
My setup:
D-ViewCam 3.5
2 DCS-5020L FW 1.03_B8
6 DCS-5010L FW 1.03_B8
5 DCS-2332L FW 1.01.04
PC is dedicated Win7_64 Home Premium, Intel Core2Duo E8400@3.0GHz, Motion detections write to second harddrive
The freeze-ups problem is just with the 5010/5020 cameras (no issues with the 2332s). By freeze-ups, I means the time and image stop changing within DViewCam. The camera does not Disconnect. There is nothing in the camera log to give me a clue that there was a problem. I can use IE to log into the "frozen" cameras and view the Live Image, so it appears to be more a problem with DCamView than the camera itself.
Scenario1: Using DViewCam's "Camera Settings" set all 5010 and 5020 cameras to use MJPEG.
Scenario2: Using DViewCam's "Camera Settings" set all 5010 and 5020 cameras to use H264.
In scenario1 the cameras go for days without freezeups. Unfortunately bandwidth utilization is quite high and I suspect (but don't know) that FPS may suffer. DViewCam shows total utilization at 80-90Mbps.
In scenario2 the cameras randomly freeze after a few hours or days. I say randomly because I don't see a pattern (I kept a spreadsheet log for a few days capturing which camera froze, how it was connected, and the time of day when it froze). The freeze happens on 5010s and 5020s. It happens whether the camera connects via WiFi or wired. The time of day is random. Over the course of three days, two or three cameras may freeze. I suspect if I left the system alone, then in the course of a week, all the 5010s and 5020s would be frozen in DViewCam.
The plus side of scenario2 is that total camera network bandwidth utilization falls to about 25Mbps per DViewcam.
I don't think it's a hardware or network issue. Those don't change when I switch scenarios. And the scenario which uses less resources (in H264 mode) is the one which has the freeze ups.
Any suggestions would be appreciated.
