Issue with Motion+Low Res recording on a camera that doesn't connect with a secondary RTSP stream
Answered
Ahoy all,
I noted an issue that might be nice to avoid.
Customer installed a system with about 50 existing IP cameras.
Most of the cameras appeared via auto discovery and the primary and secondary RTSP paths were part of the handshake and put into place with the recording software.
There were 5 cameras that never provided the secondary rtsp path to the system as part of the auto discovery/handshake with the recording software.
On these 5 cameras The software allowed a recording schedule to be set up as Motion+Low Res recording even though there was no secondary stream.
The result was that no video was recorded, but the camera had an indicator showing that it was recording.
This was discovered recently on playback, and the issue was overlooked by the tech who did the installation.
Bottom line, I would love to see some logic in the software that would warn you that there is no secondary stream on the camera if you are setting a recording schedule for that camera that requires a secondary stream to function.
I tested, and forcing the primary stream for motion detection in the expert section of the camera would have resolved the problem as well.
It appears one could feasibly set up a High+Low recording schedule on a camera that has both primary and secondary rtsp streams available and would work.. The system would then allow you to copy this schedule to a camera where it will not work..(if the camera being copied to doesn't have a 2nd stream available).... and if you don't see that there is no 2nd rtsp path for the camera, you could make the mistake of thinking all is working as it should.
Due diligence on setup would have found the issue on the front end... but it would be nice to have a flag thrown if you try to apply a setting that won't work to a camera for recording.
I hope this isn't tool long winded.. and it's not a complaint, just an observation that would be nice to avoid the potential to repeat inadvertently.
-
Hi Matt,
We appreciate your feedback on this issue.
Under the recording tab of the camera settings, if motion is not possible due to secondary stream, the following warning should be displayed: "Dual-Streaming and Motion Detection is not available for this camera."
It could be possible that the auto-discovered cameras were added with a secondary stream but subsequently, the VMS somehow lost the secondary stream after being added.
What version/build of Nx is being used and what cameras are being used?
0 -
I wasn't able to check in the recording tab of the particular cameras that had the issue to see if the notification you referenced was there... but ideally some kind of notification that would better clarify the fact that the recording schedule as selected or attempted to copy from another camera would not function. And the idea that a recording icon shows in the tree next to the camera when in actuality nothing is recording is something that could be confusing.
On a system with 100 cameras, it is unlikely that a technician is going to go through each camera and check for 2ndary streams.
Time is money to most of our installers.. quick, simple, and easy to use is an absolute requirement for them. We love this platform and choose it as our go-to for most projects.
I'm dealing with less than highly technical people doing the installs on some of these projects. Otherwise I wouldn't have noted the issue as something that would be nice to have.
Any simplification to avoid issues like this would be great to have in the software.
We are running the latest version of Digital Watchdog
v4.1.0.31401 I only came to this forum on this because DW support refused to share my concerns with engineering or share with development.
Thanks for your feedback. If this issue is not something you want to consider, or outside boundaries, by all means feel free to delete.
1 -
Hi Matt Barber,
Although we do not consider this as faulty or a bug, we value your feedback and therefore I moved this topic to the 'New Feature Ideas' section, so our product team will be aware of this concern, and they might be able to clarify this notification in a future release to avoid confusion.
But I have to be honest, I do not expect a change on a short notice, unless it is an easy solution we can add.
0 -
Matt, Norman, Derek,
This issue is already fixed and likely will be released in 4.3 version.
The behavior should be the following:
If camera doesn't have the secondary stream, motion detection will be off by default, and "Motion" and "Motion + Low-res" options in the schedule will be disabled.
If you enable motion detection, it will be enabled for the primary stream. "Motion" mode in this case will be enabled, but "Motion + Low-res" will remain inactive.1 -
Very cool and very fast reply. I'm impressed. Thank you for your time and tolerance.
Matt
0
Please sign in to leave a comment.
Comments
5 comments