-
Notifications
You must be signed in to change notification settings - Fork 50
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
pylonsrc: duplicate feature names #48
Comments
Some of the features I've found
|
Some more features. And with the previous comment it is (almost) a complete list of features with duplicates already implemented in
|
At first I thought that feature name strings could be extended to an array of aliases. this would introduce a generic way to handle duplicates. But it also has a big overhead on features with no aliases. So I think that we should simply add required checks for proper names. As for features like During my research I've also noticed that |
Thanks for gathering these, unfortunate that Pylon doesn't transparently handle changed names. |
The difference on feature naming is encoded in SFNC version supported ( Check the Basler pylon c++ documentation regarding ( MigrationMode and "Migrating Existing Code for Using SFNC 2.x-Based Camera Devices" ) |
Different models of Basler cameras have different names for similar features. For example
AcquisitionFrameRateAbs
andAcquisitionFrameRate
. Plugin can be modified to try all possible aliases is those cases. Care must be taken though as some features are related but not equivalent. For exampleGain
andGainRaw
, whereGain = f (GainRaw)
andf()
depends on a camera model.Basler features documentation
I'll try to list all features with duplicate names. At least those already implemented in plugin. And then I'll develop a way to handle them. Any help is welcome
The text was updated successfully, but these errors were encountered: