Describe the Issue
When attempting to connect to a camera, multiple instances of the same device are generated in device_info_list, with the only difference being the 'parent' key's genicam interface existing at a different memory address. This makes it effectively impossible to create an acquirer from a key except by locating the genicam interface pointer.
To Reproduce
Steps to reproduce the behavior:
See code
Sample Code
from harvesters.core import Harvester
h = Harvester()
h.add_file('C:/Program Files/STEMMER IMAGING/Common Vision Blox/GenICam/bin/win64_x64/TLIs/GEVTL.cti')
h.update()
print(h.device_info_list)
Expected Behavior
I expect only one such interface to exist per camera.
Configuration
OS: Windows 10 22H2
Python: 3.10.14
Harvester: 1.4.3
GenTL Producer: Stemmer Imaging Common Vision Blox GEVTL.cti
Camera(s): Visible in code output, (Calibir GXM640, Goldeye G-008)
Reproducibility
I can run the code as much as I want, in both interactive and terminal, the output does not change.
Actions You Have Taken
I have done some ctl-f through harvesters documentation and searched existing closed and open issues with related terms. I have checked against the eBus player software and network pings, which only shows one camera instance each.
Additional context
Attempting to connect to both instances of a single camera still results in an already in-use error, as expected.
Describe the Issue When attempting to connect to a camera, multiple instances of the same device are generated in device_info_list, with the only difference being the 'parent' key's genicam interface existing at a different memory address. This makes it effectively impossible to create an acquirer from a key except by locating the genicam interface pointer.
To Reproduce Steps to reproduce the behavior:
Sample Code
OUTPUT MODIFIED FOR READABILITY
Expected Behavior I expect only one such interface to exist per camera.
Configuration
Reproducibility I can run the code as much as I want, in both interactive and terminal, the output does not change.
Actions You Have Taken I have done some ctl-f through harvesters documentation and searched existing closed and open issues with related terms. I have checked against the eBus player software and network pings, which only shows one camera instance each.
Additional context Attempting to connect to both instances of a single camera still results in an already in-use error, as expected.