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
Proper beahviour for Triggering #83
Comments
Hello, I'm implementing those plugins with @MarcusZuber. I think one major design problem is that it is not really possible to say when or if a trigger is "valid". The naive idea is that you initiate a grab on thread A, then send a trigger on thread B and the grab in A will return. |
Sorry for the late reply, the message slipped through. One word in advance: the trigger semantics originate from the pco-family of cameras and other cameras were mapped as good as possible. But of course they all vary slightly in certain regards. Anyhow:
You will always have the problem especially when switching to hardware triggers where you never know when a trigger even happened. If you can provide a backwards-compatible PR, I am all open to review it Different behaviour with different pco cameras must come from hardware (but we could of course accomodate for that in software) because the plugin calls the lower-level command API the same way, regardless of the camera model. |
We are currently implementing multiple uca-plugins and are a little bit confused how the triggering/grabbing should work with the different
trigger_sources
"AUTO" and "SOFTWARE".@matze , @tfarago : Could you comment on this? I think the behavior is even inconsistent within the uca-pco-plugin depending which camera is attached.
The text was updated successfully, but these errors were encountered: