-
Notifications
You must be signed in to change notification settings - Fork 148
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
jetson TX2 camera #12
Comments
are you using the onboard camera of the jetson? |
Hi! for my experience: video_input : nvcamerasrc ! video/x-raw(memory:NVMM), width=(int)600, height=(int)600,format=(string)I420, framerate=(fraction)5/1 ! nvvidconv flip-method=0 ! video/x-raw, format=(string)BGRx ! videoconvert ! video/x-raw, format=(string)BGR ! appsink |
@AlexanderRobles21 @gustavz
I have installed applicable gstreamer dev packages.
Any help would be appreciated. Thanks. |
I make a guess: The problem is that Nvidia/JetPack Build OpenCV without Gstreamer support. Long story short: |
Hi Gustav, Thanks for your quick reply. I actually reinstalled OpenCV from source following this tutorial: https://jkjung-avt.github.io/opencv3-on-tx2/ I am using TF1.6 with JetPack 3.1 (and have also tried TF1.5 and gotten same error). From prying around the other issues in this repo, TF1.4 is recommended for this repo; however the error I have posted seems to be Gstreamer related. I will try reinstalling OpenCV from source and switch to JetPack3.1 to use TF1.4 and try that and post an update. Any input from your side is also appreciated. Thanks a lot. |
I use and always have used JetPack 3.2, maybe you should switch to that? |
Hi @imxboards, I recently tested object_detection.py for Jetpack 3.1 and TF 1.3 without any problems using onboard cam and webcam ( video_input = /dev/video1) achieved 20fps. But when I used TF 1.6 rc1 there is a problem: 2018-04-27 11:06:05.483867: E tensorflow/stream_executor/event.cc:33] error destroying CUDA event in context 0x337fbf0: CUDA_ERROR_LAUNCH_FAILED I recommend to use TF 1.3, I think this version works for CUDA 8. For Jetpack 3.2 (CUDA 9) I didn't tested yet. |
I successfully tested it on 1.4, 1.5, 1.6 but with varying performance results. If you want to achieve highest results use the versions that I recommend in the readme. Also I strongly recommend you all to use JetPack 3.2 because of CUDA 9 / cuDNN 7 among other improvements |
@warisz could you solve the problem? I am experiencing the same problem trying to install with tensorflow 1.6 and opencv 3.4.0 that i built by myself... cheers! |
I am experiencing the same problem, I have Jetpack 3.3 and TF 1.9 I installed open CV using this tutorial : VIDEOIO ERROR: V4L: device nvcamerasrc ! video/x-raw(memory:NVMM), width=(int)1280, height=(int)720,format=(string)I420, framerate=(fraction)30/1 ! nvvidconv flip-method=0 ! video/x-raw, format=(string)BGRx ! videoconvert ! video/x-raw, format=(string)BGR ! appsink: Unable to query number of channels Available Sensor modes : NvCameraSrc: Trying To Set Default Camera Resolution. Selected sensorModeIndex = 1 WxH = 2592x1458 FrameRate = 30.000000 ... Available Sensor modes : NvCameraSrc: Trying To Set Default Camera Resolution. Selected sensorModeIndex = 1 WxH = 2592x1458 FrameRate = 30.000000 ... Socket read error. Camera Daemon stopped functioning..... |
Hi @scbean have similar problem to the one you are describing Merwan |
Hi @Merwanski and @scbean You can check my repository: https://github.com/Alro10/realtime_object_detection Use this file: object_detectionjetson.py Please write back if that solves your problem! |
Thank you @Alro10 ... the camera is working but I am still getting this error message |
hi ,
I install tx2 with
Ubuntu 16.04
Python 2.7
Tensorflow 1.7
OpenCV 3.3.1
But when I ruan object_detection.py issue is coming
vidia@tegra-ubuntu:~/tf/realtime_object_detection$ python object_detection.py
/home/nvidia/opencv/modules/videoio/src/cap_gstreamer.cpp:887: error: (-2) GStreamer: unable to start pipeline
in function cvCaptureFromCAM_GStreamer
can you help me ? should i change config.yml parm?
The text was updated successfully, but these errors were encountered: