Troubles playback recorded video SM5000 NSN5200
It is very unsustainable that the camera has to be turned on when starting a video playback in the latest sdk/api. I can see it is because the playback has to get the camera information data before starting. Is this fixed in the comming release of SDK/API ?. Our 100 cameras is recording our patients in the night, and it can't be turned on 24/7. The people in day shift has to turn cameras on for viewing nightly recordings. Not practical.
Greetings from Denmark.
Thank you for your post.
I must apologise, but I'm not completely clear on your post. Some of the information is fragmented and I'm having difficulty following along. To help clarify things, I will ask you some questions to help me understand better:
What version of Pelco SDK are you using?
- I assume the use of Pelco SDK because of your notes about SM5000 and NSM5200. The SM5000 is older equipment, and therefore troubles me. The SDK can trigger manual recording if necessary. HOWEVER, the determining factor on if a camera is set to record constantly or not is NOT determined by the SDK but by the Endura environment setup itself (specifically with the recording NSM). Constant recording on the NSM is usually the default setup for Endura, though this can be changed I believe. This point is not an SDK issue or question but one about Endura and one for Pelco Product Support - you can reach them at +4543959871 or by email at ne-tech AT pelco.com (information taken from Pelco.com under "About Us" -> "Contact Us" and looking on the map for the office for Denmark & Norway in EMEA).
If you are using the Pelco SDK to retrieve recording from the NSM5200 for a given time, then recording must exist at that given time on the NSM for any playback to work. If the camera is not set to constantly record within the Endura and NSM setup, then there is a chance that the SDK's request for playback might fail (if no recording exists at the time specified).
I'm confused by your phrase "camera has to be turned on" -- I take this to mean actual power to the camera to physically have it active. That's why I'm confused because of course the camera would need to be turned on for any video to be generated, so I do not think that is your intention. Do you mean the camera must have an active streaming session? It must be streaming to the NSM to record for the NSM to store any video. From there, then the SDK can be used to query for and view that recorded video.
Again, I apologise for my confusion. From what I see, the points you've outlined do not indicate a behavior problem with the SDK or it's functionality that I can tell, but a setup issue or question with the way Endura works with recording on the NSM. If you still have questions, please help me to understand better so that I can help out.
Sorry for not explaining correct.
I will try to describe a typical working day here at the hospital, it possible makes a better understanding.
Our patients is going to sleep in the evening. The camera is powered on. SM5000 is now recording. Lets say the camera is powered on from 23:00 til 08:00 in the morning, at 08:00 o'clock in the morning the camera is powered off again. Now we have 9 hours of recorded video on our NSM5200.
The nurses starts browsing the recorded video at etc. 11:00, and they want to se what happend at 03:00 in the morning.
Here is what im am trying to explain.
It is not possible to view recorded video via the latest Pelco SDK 4.2.1 if the camera is not powered on, you can't initialize a playback session, You have to have a camera object defined, and it is impossible.By single step I can see that the camera data is taken from the camera in "live".
Huh, that is an interesting use case scenario ... certainly not one that has been considered in testing. Sadly our development team that worked on the older Pelco SDK is no longer with the company, so I can't ask if that was something that was considered with an Endura system. I'm not even certain if playback works within Endura using Workstation software if the camera is also offline and not registered as online with the System Manager -- do you know? Have you tested or tried that?
I can tell you that from a testing perspective the kind of setup that you describe was never considered when using Pelco SDK. Cameras were considered to be online all the time and streaming live video, even if they weren't actively being recorded by an NSM. Motion-based recording or recording based on schedules is one thing, but to have the camera completely powered off and offline I do not believe was considered.
As a theory only, it might be possible to investigate the NSM's recordings using the VideoOutput API service and perform a Query there ... though you'd need to know the camera's UUID in order to cross reference the UUID and determine which cameras had which recordings. I really don't think that a scenario like what you describe has been considered, certainly not when it comes to the Pelco SDK at least.
Pelco SDK is no longer under active development efforts. The last release was in January 2016, over a year ago. We have made some very minor changes only for specific instances of VideoXpert systems early last year, but those versions were not released because the plan is for developers to use the VideoXpert SDK when writing a solution with VideoXpert. Sadly, there are no plans to provide any changes for Pelco SDK at this time, and no development effort is being made.
With this behavior that you are describing and the knowledge that Pelco SDK is not being updated, we may need to explore a different route -- is it possible to leave the cameras online but not have them record? Or perhaps it's possible to leave the cameras online but only set them to record during certain times on a recording schedule (please reach out to Pelco Product Support for help if needed to do this)?
Privacy and Cookies Policy
Copyright © Pelco