We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
greetings
if I work with jupyter notebook I can use the camera, but if I try to run it from terminal as file.py I get the error:
[ WARN:0] global /home/nvidia/host/build_opencv/nv_opencv/modules/videoio/src/cap_gstreamer.cpp (933) open OpenCV | GStreamer warning: Cannot query video position: status=0, value=-1, duration=-1
right after: camera = USBCamera( capture_device=0 )
I tried:
gst-launch-1.0 v4l2src device=/dev/video0 ! videoconvert ! xvimagesink
and works OK
I use nanocamera example and get the same error:
but it open a video stream anyway and works OK
I am working with a logitech webcam 920
The text was updated successfully, but these errors were encountered:
Were you able to fix it? Did the NanoCamera work for you?
Sorry, something went wrong.
No branches or pull requests
greetings
if I work with jupyter notebook I can use the camera, but if I try to run it from terminal as file.py I get the error:
[ WARN:0] global /home/nvidia/host/build_opencv/nv_opencv/modules/videoio/src/cap_gstreamer.cpp (933) open OpenCV | GStreamer warning: Cannot query video position: status=0, value=-1, duration=-1
right after: camera = USBCamera( capture_device=0 )
I tried:
gst-launch-1.0 v4l2src device=/dev/video0 ! videoconvert ! xvimagesink
and works OK
I use nanocamera example and get the same error:
[ WARN:0] global /home/nvidia/host/build_opencv/nv_opencv/modules/videoio/src/cap_gstreamer.cpp (933) open OpenCV | GStreamer warning: Cannot query video position: status=0, value=-1, duration=-1
but it open a video stream anyway and works OK
I am working with a logitech webcam 920
The text was updated successfully, but these errors were encountered: