Skip to content
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

Implement quirk files #2

Closed
EmmanuelP opened this issue Aug 4, 2016 · 1 comment
Closed

Implement quirk files #2

EmmanuelP opened this issue Aug 4, 2016 · 1 comment
Labels
1. Enhancement Issues that propose improvements to existing features 5. Camera Issue in ArvCamera API

Comments

@EmmanuelP
Copy link
Contributor

Cameras don't always use the standard names for the most common features, like exposure, image rate, etc...

Currently, ArvCamera checks for vendor and model, and behave differently when needed. The drawback of this method is when we want to add a new behaviour for a new camera, it has to be included in the code, and it will not be easily available to users until the next release.

It could be improved by instead using quirk files, in the form of genicam xml patches. This quirk files would be bundled in the aravis distribution, but could also be read in a defined user directory.

The search path would be:

$XDG_DATA_DIRS/aravis
$prefix/share/aravis

The patch file will be named using the camera genicam filename with a .patch extension added.

Not everything will be possible with these quirk files, but it could be possible to make new camera work without additional code.

@EmmanuelP
Copy link
Contributor Author

I'm closing this issue in favor of #733

@EmmanuelP EmmanuelP closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. Enhancement Issues that propose improvements to existing features 5. Camera Issue in ArvCamera API
Projects
None yet
Development

No branches or pull requests

1 participant