-
Notifications
You must be signed in to change notification settings - Fork 614
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow selection of onvif url provided from camera #4157
Comments
Thank you for the issue @gmonk , I'm moving to the backlog to schedule it. |
Are there any work arounds to force the onvif url ? do these configs get stored in a config file or database ? I am trying to demo this with the hopes of being able to purchase the enterprise version but if it does not work with our CCTV cameras I do not have much to go on. Thanks |
Hi @gmonk , These configs are stores in database. After server gets the RTSP url, it saves to the DB and you can change the RTSP URL in the db. It's a little tricky. I think the support team can help you if you go to Enterprise edition. You can reach to support via support@antmedia.io Please let me know if I can help with anything |
This issue is still prevalent in the latest release. I believe the interpretation of what I was talking about was way off. This is not an issue with simply being able to query the profiles to a camera that has been already added via REST. The issue is when trying to add any current CCTV camera capable of multiple encoders which is the majority of enterprise CCTV cameras out there. When trying to add any one of these cameras Antmedia simply adds the first profile it finds assuming thats the right profile when in fact several cameras will use different codecs for different profiles such as mjpeg or mpeg4 which is the case for the cameras we use the encoders 1&2 are both mpeg4 which ant media does not seem to decode and 3&4 are H.264 But Antmedia simply chooses ProfileToken_1_1 every single time. This can easily be fixed by either probing the ONVIF media params in the camera and returning an option for the user to select from before adding or simply honor the url given by the user when manually adding. I have tried to add the correct profile or edit an existing profile and change it to ProfileToken_1_3 but no matter what Antmedia simply rewrites it backto ProfileToken_1_1 or re-probes the camera picking the first profile and does not accept the changes. The camera stream works just fine if I do add it in as a Stream Source using the following |
Hi @gmonk , Thank you for your comment. You point out different angle and it makes sense. Anyway, just let me tell what the current solution works and then discuss a solution for your case. We thought that user can choose any profile to change resolution and bitrate so that we created a REST method to let the user get the profiles. Here is the basic workflow
In this way, you can use any RTSP Stream URL on the device. Please let me know if it's a solution for you. Secondly, I agree that Ant Media Server should pull the first compatible Stream profile(H264) by default and let the user choose the other profiles. The solution above provide the ability to let the user choose the other profiles programmatically. I guess you want this ability to be available on the web panel? Lastly, I really would love to see what you've developed and understand how we can help you each other. Is it possible to schedule a meeting and discuss further about our collaboration? |
Is your feature request related to a problem? Please describe.
Siqura PTZ Camera HSD626 provides 4 different encoders 1-4 first two only encoders 3-4 support H.264
antmedia does not properly detect all encoders and give option to select it will only detect Profile_1 I have tried to override by providing ONVIF URL with Profile_3 but antmedia does not honor the entry and once saved still seems overwrite and url changes back to Profile_1
Describe the solution you'd likeo
Using other VMS type software on the same camera the ONVIF probe will return list of rtsp urls from the camera and give you the option to select proper url. This would be a nice option.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: