You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that this library has several bug reports. But perhaps most of these bugs are directly related to the fact that the camera is not fully compliant with the ONVIF standard.
This library expects the camera response to be fully ONVIF compliant.
The camera has an internal server that responds to client requests. This library creates a client that requests responses from the camera.
I discovered this when trying to check the camera responses, and noticing that each camera returns a different response.
When trying to check (using https://jsonformatter.org/wsdl-formatter) if the response is at least standardized, it presented errors. But the references available on the ONVIF website do not show errors. If the responses from the cameras have header formatting errors, they must have ONVIF standardization errors.
Other libraries may have different ways of interpreting camera responses, due to having experienced standardization failures.
The Android App Onvier demonstrates that it can locate the RTSP address correctly, of the cameras mentioned above, which may perhaps be a hope of being able to evolve this library, so that it is more universal and less dependent on the rigid standard that the ONVIF website presents.
Despite this, camera manufacturers that claim to be compatible with the ONVIF standard should have their equipment 100% compatible with the standard. Or not advertise that they are compatible with ONVIF, so as not to cause inconvenience to users.
Hello,
I noticed that this library has several bug reports. But perhaps most of these bugs are directly related to the fact that the camera is not fully compliant with the ONVIF standard.
This library expects the camera response to be fully ONVIF compliant.
The camera has an internal server that responds to client requests. This library creates a client that requests responses from the camera.
I discovered this when trying to check the camera responses, and noticing that each camera returns a different response.
When trying to check (using https://jsonformatter.org/wsdl-formatter) if the response is at least standardized, it presented errors. But the references available on the ONVIF website do not show errors. If the responses from the cameras have header formatting errors, they must have ONVIF standardization errors.
Other libraries may have different ways of interpreting camera responses, due to having experienced standardization failures.
The Android App Onvier demonstrates that it can locate the RTSP address correctly, of the cameras mentioned above, which may perhaps be a hope of being able to evolve this library, so that it is more universal and less dependent on the rigid standard that the ONVIF website presents.
Despite this, camera manufacturers that claim to be compatible with the ONVIF standard should have their equipment 100% compatible with the standard. Or not advertise that they are compatible with ONVIF, so as not to cause inconvenience to users.
Ref.: https://superuser.com/questions/1253126/how-do-i-find-the-video-stream-url-of-onvif-cameras-manually/1880053
The text was updated successfully, but these errors were encountered: