• February 23, 2025, 03:54:29 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Dview 2.04 and some issues  (Read 4415 times)

aiman

  • Level 1 Member
  • *
  • Posts: 5
Dview 2.04 and some issues
« on: November 12, 2009, 11:49:58 AM »

Hi,
I installed Dview 2.04 to use with my cameras and I got some issues/questions that I would like your help with.

1- As of now, I have 7 cameras added and more to come. For some reason, every now and then I lose the connectivity to one or more cameras for several seconds. I get an event at the bottom saying "Video Lost" and on the monitoring window it says "Connecting".
Why is that happening?
And I configured it to send me an email whenever Video is lost. It is not sending me anything

2- I configured the recording to be on "Scheduled Recording", 24/7 and I selected "Economic Recording".
I want it to record whenever motion is detected. However I come today and I saw a lot of recorded video while no body and no movement was there. Why is that happening and how to work around it? I checked the Motion detection settings and sensitivity, they're okay and not detecting motion yet Dview is recording.

3- When I check some Scheduled recordings, I get the message "File size is zero, can not be playbacked". Why is that?

4- When I am playingback some recordings, I noticed that monitoring pauses, does that mean it stops recording?


I appreciate your earliest response guys.
Logged

Mackerel

  • Level 3 Member
  • ***
  • Posts: 348
Re: Dview 2.04 and some issues
« Reply #1 on: March 16, 2010, 08:24:47 AM »

1. Somehow the signal lost event is never triggered in the DviewCam. Even on the new V3.0 version. And on all versions once in a while the signal is lost for a few seconds... It just happens.
2. The Economic Recording option was never implemented 100%, so...
3. This means that a number of files were cleaned up/deleted from outside of the program. Dunno why...
4. Playback costs CPU and that is subtracted from the Monitoring need. What you can do is increase the process-priority of the monitoring part, which will help a bit. Your machine must be powerful enough to handle that.

Try the new version 3.0 to see if that one helps you out, but the economic recording option is no longer there.
Logged