Unexpected video codec format streaming has been received with video API
Completed
Unexpected video codec format streaming has been received with video API
Extracting transmitted video streaming from the camera, which is set H.264 through RTSP streaming from the Nx server, the received video format changed to H.265 unexpectedly. This could happen?
What we did
We set the following video streaming flow for our original AI processing.
Out system overview
[ Camera ] >—(1)—> [ Nx Server ] >—(2)— >[ Our custom AI server ]
(1) video streaming set to H.264 with ONVIF
(2) video streaming format was not designated specifically
Used Web API without video codec as follwoing.
rtsp://User:Pswd@XXX.XXX.XXX.XXX:YYYY)/b68f6dd3-cad9-adaa-498e-2b7dc2a58844
Result
Our server stopped due to an unexpected video codec H.265 received.
Fail rate
This issue happens not always happen. Only once we faced the issue.
We are not sure about the trigger.
Expected Result
The expected video codec is H.264, and even video codec is not set over API, the video format should follow the original camera video codec always, we expect.
Observation
Assuming we would not encounter the issue if video codec is set with API. However, this could imply that Nx internally changed the stored video codec to H.265 after receiving H.264 video streaming. On top of that, we worry about CPU/GPU resources changing video format unexpectedly. What is the Nx internal behavior? If this could happen, how to avoid this behavior?
Question
1. Why such an unexpected video format has been transmitted?
2. Nx could generate another video format to store video?
3. If The answer to Q2 is yes, could you please share the workaround to fix the video to fix a designated CODEC and share possible side effects? if this workaround is not usual.
-
Hello,
Result
Our server stopped due to an unexpected video codec H.265 received.Could you elaborate on this, please? How technically have you detected the codec was H.265? Any evidence is welcome: error message, log message, RTSP session traffic capture.
1. Why such an unexpected video format has been transmitted?
The URL of the API request indicate you are opening LIVE stream from a camera.
At the moment, I can suppose two reasons.
1. Someone has changed primary stream codes on a camera.
2. The Server has switched to the secondary stream of the camera with H.265 codec configured.Could you please share a screenshot of the "Advanced" tab of camera settings in the GUI application?
2. Nx could generate another video format to store video?
By the API you are using (rtsp://User:Pswd@XXX.XXX.XXX.XXX:YYYY)/b68f6dd3-cad9-adaa-498e-2b7dc2a58844), the Server does not change codecs nor transcodes video and sends video as it comes from a camera.
-
Andrey Terentyev
Thank you very much for the comment.
About "Our server stopped due to an unexpected video codec H.265 received."
We developed it, and the original Ai processing is running on our server. The process uses video from Nx output over the API as below.
[ Camera ] >> [ Nx Server ] >> [ Our custom AI server ]Last week our server stopped due to the phenomenon. Because the unexpected video format RTSP data has been received. Our Ai process can handle H.265, but to enable this, before starting processing, we need to designate a video codec. In this case, we set H.264. Thus, our process stops if H.265 is transmitted.
Truth, the following internal log, has remained. this log has been extracted from our AI server.
-
Sorry, I forgot to attach the log.
Here is the log from our system.
[rtsp @ 000001bfa5a6fec0] Multi-layer HEVC coding is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature that has not been implemented.New Update
After checking connected cameras, we found one camera has H.265 video stream setting.The camera has 3 streams, 2 out of 3 are set with H.254 but the 3rd stream is set with H.265. we are assuming this could be affected.
But the question here is, Primary and secondary streams are set with H.264, so even if the camear has H.265, the 3rd stream should be never used by Nx in our understanding. This could happen?
-
Hello,
But the question here is, Primary and secondary streams are set with H.264, so even if the camear has H.265, the 3rd stream should be never used by Nx in our understanding. This could happen?
At the moment, with the description you've provided, the most probable version is that someone has changed stream settings on a camera.
Another one is that the camera sends occasionally "wrong", i.e. look to be H.265, frames while the H.264 stream has been declared.
Anyway, to answer more precisely, we need a reproduction scenario.
Please, refer this article to provide structured information for further investigation.
https://support.networkoptix.com/hc/en-us/community/posts/7430083630615-Support-Request-Template
Please sign in to leave a comment.
Comments
7 comments