-
Notifications
You must be signed in to change notification settings - Fork 313
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
Can use only one ONVIFCamera instance at a time #11
Comments
Sorry for my late response. I'm in vacation... Thanks for your report :) I haven't run more than one instance in single process, but I think there is something wrong with suds cache. you can set the mycam = onvif.ONVIFCamera(ip, 80, user, passwd, on_cache=True) |
did you find a permanent solution ?
Then I tried using 2 instances of ONVIFCamera class, |
I also meet 2 cameras problem when creating pullpoint. The code is like below:
When ran 2 camera instances, it would show error
There is no problem to run one camera. Is there some fix for the code? |
…class don't pollute each other. quatanium#11
Hi,
Thanks for the nice module. It works like charm ..
.. except when one is trying to connect to several (2+) cameras simultaneously.
The included python code demonstrates the problem.. just change the ip addresses in the main method's cams list.
When there is only one camera in the list it works ok (tried with both cameras individually), however, when there are two cameras in the list, it gives
(400, u'Bad Request')
while trying to get the media profiles for the second camera in the list.
The only way I can make two cameras work with this onvif module simultaneously, is to start them as individual processes (i.e. using python's multiprocessing module).
I'd please like to know why such behaviour and if it could be easily fixed.
Kind Regards,
Sampsa
The text was updated successfully, but these errors were encountered: