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 looked into GenICam's specification. If I understand correctly, looks like for a device than conform to the specification, it likely exposes GenICam's Transport Layer (TL) in a .so (named as .cti). This covers image capture part. The configuration of a camera is in GenICam
API, which may not be needed for image capture (need to confirm).
Since TL is C API and is well-defined, we very much could just use TL header file to directly operate and get the image capture. In fact it seems Harverster is access the TL's python binding which is pretty much the same method.
The only requirement is that camera need a TL Producer driver which typically bundled by vendors anyway.
It Is correct if we want to cover intially the capture part.
Also in V4L and OSX currently we are not covering camera settings control of these API if I remeber the PR correctly (could be useful later to have camera control settings).
Ref. #814 The majority of industrial and machine vision cameras need GeniCam support.
The text was updated successfully, but these errors were encountered: