Integrating our application with Milestone, is there a simple way if we can play the VOD stream of RTSP in the form of a URL?
If I am just pulling a maximum of 3 recorded streams at a time, (out of hundred streams) is there going to be a large incremental resource utilization for transcoding at the Milestone backend?
Tried using command like in the document: "vlc.exe --rate=-1.0 --start-time=3600 “rtsp://basic:basic@bgws-pvv-04:554/vod/943ffaad-42be-4584-bc2c-c8238ed96373” but could not get the video recording
A: Yes it works fine for Live views. We are able query the available cameras based on the camera names and retrieve the corresponding live views of the CCTVs via the ONVIF bridge set up in the Milestone server
• are you sure your camera has recordings?
A: The camera recordings are being recorded in a Milestone recording server, and we were shown that the time/date that we are trying to retrieve for the particular group of cameras has recordings and is able to playback from Milestone system
• have you double-checked the address (hostname, port, camera ID)?
A: We assume that would be the same information for the live view?
• what exactly happens when you attempt to play the video in VLC?
A: At the moment there is no feed to play on VLC. We tested on a few cameras which we were able to retrieve live feed. For example, we sent a request token to Milestone for a recording for a particular camera with a particular timestamp and we got a response token which allows us to GetRecordingSearchResults. However, the search could not render any results.
You can find answers to similar questions here and here.
Please bear in mind that VLC supports only relative times. The RTSP protocol itself supports also and absolute times.
In your example this parameter “–start-time=3600” will offset the playback in 1 hour (3600 seconds) after the beginning of the recordings in the RS DB. And I’m pretty sure GetRecordingSerachResult returns absolute times. So if you want to use VLC, you have to convert absolute times to relative to the DB start.
Milestone Development cannot reproduce the issue the problem is no longer related to creating new code or integrating our existing code.
The only advice Milestone Development can give is to try troubleshoots with different users, or try different cameras - but again, this is not related SDK anymore. As this is not related to software development with the MIP SDK, which is the focus of this forum, please ask again in the support community, you should get better help from the partners using the support community.
Noted. We managed to get a response (same rtsp stream can play live), meaning there should be a recording, but was not able to playback. Any idea what could be a possible cause of this?
Something you said is bothering me so I want to make it clear: live feed does not mean your stream is recorded. Can you make sure that your camera is properly set-up to actually record (using for examle Smart client or Web client)?
We have asked the same question to the technology provider that owns and manage this milestone server instance multiple times. They have replied that recordings have been ongoing and showed screenshots of camera view recording from the client software,
The only advice I can give is to try troubleshoots with different users, or try different cameras - but this is not related SDK anymore. As this is not related to software development, which is the focus of this forum, please ask again in the support community, you should get better help from the partners using the support community.
For some reason we are able to pull the VOD streams now, probably a restart of the server or certain services?
We are now trying to retrieve accurately the event that happened. From a given timestamp of an event given by milestone, we are trying to pull the VOD stream.
We understand that the way the VOD stream is being pulled, if we wanted a to play a specific timing of recording, we have to account the number of seconds that has elapsed from the beginning of the recording.
From the ONVIF API we used getRecordingInformation but the time that is being reflected seems erroneous as the event happened, for example at 22-10-06 18:02, but the pulled recording information is: