Open PipGrylls opened 2 years ago
Using the following code I can connect and disconnect from two cameras without hitting the issue. This leads me to follow the logic that the event loop needs to be able to have cameras added to it or threads need to specifically carry their own cameras to work in parallel? See simple connect disconnect on a single event loop here https://gist.github.com/PipGrylls/79b3cc09a5f90e9fd3acba8cfa803100
Hello. While the SDK has been designed to allow control of multiple cameras simultaneously, this is currently largely untested. I do plan on getting around to this at some point but I can't say when that will be at this time.
Hi! I found the same problem, have you fixed up this issue?
I have not done any testing on this. It definitely needs some work.
This ticket is being used to track development / testing of simultaneous connections. The original bug request is shown below.
===================================================================
Connecting to cameras simultaneously seems to cause issues when disconnecting.
Hardware: 2x GoProHero10, Raspberry Pi 4b 2Gb
I am using an ExitStack to control the contexts but I can recreate the issue without using a context manager. Note: the wifi is not enabled as the Pi is controlled on the network over wifi and it will be disconnected if wifi is enabled.
I think there is an issue in releasing the async disconnect event. One camera will connect and disconnect fine.
Tomorrow I will edit the GoPro class to try to release whatever event is blocking and will update the issue/create a PR if I find anything.
Minimal reproduction:
And here is the traceback: