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

Camera process issues #82

Open
tbekolay opened this issue Jul 12, 2018 · 0 comments
Open

Camera process issues #82

tbekolay opened this issue Jul 12, 2018 · 0 comments

Comments

@tbekolay
Copy link
Member

There are a few issues with the Camera process.

  • I was unable to get it running properly, but I figured it was an environment thing. A forum poster had the same issue. Dan suggested using OpenCV to get frames from the camera, and I suspect that OpenCV will be better supported than vext.

  • I just spent a day figuring out why I was getting extra logging messages printed to my console. Turns out it's some oddness with how vext does logging -- somehow just by having vext installed, doing python -c "import logging; print(logging.root.handlers)" shows a stream handler installed, so the only way around it is to detect it and remove the handler later. It would be nice if we could do camera input without using vext due to this annoying and surprising behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant