Nx video request issues

Answered

Albert Climent Bigas

October 27, 2022 11:17

Hi,

We have found some issues when retrieving video streams from the archive, when using the endpoint `/media/{cameradId}.{format}?pos=xx&endPos=yy&accurate_seek=true`

- The video itself is retrieved in only one http request, making it impossible to seek timestamps unless the video has been completely downloaded.
- Once the video has finished playing, the html native video player "breaks" and it's no longer possible to seek any time in the video. The linked video shows this behaviour:

https://drive.google.com/file/d/1Z7H2TDBxNEYr8s34LswiSzj7wyEbhQ4M/view?usp=sharing

We have seen that the http response for endpoint `/media/{cameradId}.{format}` is like this (200 OK status code):

and when comparing to other videos, we can see that the differences (such as the status code 206 Partial Content):

Headers such as Content-Length and Content-Range are also important so the video player knows the length of the video and allows seeking using the time bar

 

Regards,

Albert

0

• 

  Andrey Terentyev

  • Network Optix team

  October 28, 2022 11:41

  Hello Albert Climent Bigas,

  - The video itself is retrieved in only one http request, making it impossible to seek timestamps unless the video has been completely downloaded.
  - Once the video has finished playing, the html native video player "breaks" and it's no longer possible to seek any time in the video. The linked video shows this behaviour:

  It's expected behavior. The media interface you're using (i.e. webm) provides an on-the-fly transcoded video STREAM, not a finite video file, which is in the case of your second screenshot. That means there is no seek option in a stream. The BigBuckBunny.mp4 is a video file, not an interface to the video stream, that's why can be sought to a certain position.

  You could try the HLS media interface if you need a seek option.

   

  1

Please sign in to leave a comment.