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.
There are a few issues with the
Cameraprocess.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
vextdoes logging -- somehow just by havingvextinstalled, doingpython -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 usingvextdue to this annoying and surprising behavior.